nocodb

This MCP server exposes a natural-language friendly interface to interact with your NocoDB databases. It translates prompts into CRUD operations against NocoDB tables, enabling you to create, read, update, and delete records, as well as manage columns and tables through simple commands. The server expects you to provide your NocoDB instance URL, base ID, and an API token for authentication, and then you can issue prompts to perform tasks like creating a new record, updating fields across rows, or deleting specific entries. The included example prompts demonstrate common operations such as getting records, creating records, updating records, and deleting records, as well as adding or removing columns. You can also upload data from JSON via the provided upload workflow, and you can run the MCP server directly from the CLI for quick experiments. When integrated with Claude Desktop or other tooling, you can point the configuration to the node-based server entry point and supply environment variables to keep credentials secure.

Prerequisites:

• Node.js (recommended LTS) and npm installed
• A NocoDB instance (cloud or self-hosted) with a base and API access

Installation steps:

1. Clone or download the MCP server repository.
2. Install dependencies: npm install
3. Build the project (TypeScript to JavaScript): npm run build
4. Create a .env file or use environment variables to configure NOCODB_URL, NOCODB_API_TOKEN, and NOCODB_BASE_ID.
5. Run the MCP server: node dist/start.js

Optional (npm package usage):

• If installed via npm, you can start with the provided CLI wrapper (nocodb-mcp-server) as documented in the repository.
• Ensure your environment variables are available to the process when starting.

Environment variables are required for authentication and specifying the NocoDB base. Common issues include incorrect NOCODB_BASE_ID, invalid API tokens, or missing permissions on the token. Ensure your NocoDB instance is reachable from the host running the MCP server. When deploying, consider using a .env file or secure secret management. The CLI and integration examples show how to invoke the server directly or through tooling like Claude Desktop; in both cases, the node entry point dist/start.js expects the environment to be set up with NOCODB_URL, NOCODB_API_TOKEN, and NOCODB_BASE_ID. The project follows a TypeScript workflow with a dist folder containing the compiled server. If you encounter build issues, verify TypeScript configuration and dependencies, and ensure npm run build completes successfully.