Nocodb MCP Server

What edwinbernadus/nocodb-mcp-server MCP server does

The edwinbernadus/nocodb-mcp-server MCP server connects an MCP client to a NocoDB database. It supports CRUD operations on NocoDB tables, so an agent can retrieve rows, create records, update existing data, and delete records through natural-language instructions.

The examples show requests that target a named table, add multiple rows, update matching data, and remove records that meet a condition. The server also supports schema changes in the demonstrated workflows, including adding a column, setting values in that column, and deleting the column afterward.

A separate example loads records from a JSON file into a newly created NocoDB table. The repository includes an example JSON file for this workflow. Screenshots in the documentation also cover bulk record creation and bulk deletion.

How it works

The server uses the Model Context Protocol to make NocoDB operations available to a compatible client. It communicates with the configured NocoDB instance using three required values: the instance URL, an API token, and the target base ID.

For local use, the project is written in TypeScript and compiled output is placed in the dist directory. Claude Desktop can start the compiled dist/start.js file with Node.js and pass the NocoDB settings through the client configuration. The README also documents a direct command-line launch using the published nocodb-mcp-server package and positional connection parameters.

The base ID is taken from the NocoDB URL. In the documented URL structure, it appears between the workspace or username segment and the table ID. NocoDB Cloud users should use https://app.nocodb.com as the service URL.

Setup and configuration

Install Node.js and TypeScript, then install the project dependencies and build the TypeScript source:

npm install
npm run build

Create a .env file, or copy the repository's env.example template, and provide these settings:

• NOCODB_URL: the NocoDB instance URL
• NOCODB_API_TOKEN: the token used to access NocoDB
• NOCODB_BASE_ID: the base containing the tables to manage

Claude Desktop configuration starts the compiled server with node and points its arguments to the local dist/start.js path. The same three values are supplied in the configuration's environment section. The documented configuration uses placeholder paths and credentials that must be replaced for a real deployment.

Tools and capabilities

The edwinbernadus/nocodb-mcp-server MCP server supports the following demonstrated operations:

• Read records from a selected NocoDB table.
• Create one or more records.
• Update records, including changing values across matching rows.
• Delete records that match a requested condition.
• Add and remove table columns.
• Populate a newly created table from JSON data.
• Perform bulk record creation and deletion workflows.

The README refers to API_FUNCTION.md for the complete API function reference, but that document's contents are not included in the supplied material.

Limitations and notes

The server requires access to a NocoDB instance and a valid API token; it is not a standalone database. The supplied setup instructions describe a locally built Node.js deployment and a Claude Desktop integration. A hosted deployment is also linked through Fronteir AI, but its endpoint details and operating conditions are not provided here.

The examples demonstrate natural-language requests, but they do not define the full query syntax, filtering behavior, pagination support, error handling, or available function list. Review the repository's API function documentation before relying on operations beyond the examples. The project is a TypeScript fork of an earlier NocoDB MCP server and is distributed under the MIT license.