NocoDB MCP Server

The NocoDB Model Context Protocol (MCP) Server lets LLMs that support MCP, such as Claude, Cursor, Windsurf and Codex, work directly with your NocoDB project. On all editions, an LLM can query and edit records. On NocoDB Cloud and licensed self-hosted deployments, it can also manage tables, fields, views, workflows, interfaces, permissions and more.

Pick your client

What you can do

The NocoDB MCP server gives an MCP client a set of tools. The tools that a client sees depend on the edition, the plan and the connection.

Each tool works through the same service as the matching REST API, so validation, permissions and audit work the same way. In the Community Edition, the MCP server gives the record tools only.

How NocoDB is organized

Most tools ask for a project. These are the pieces that the tools work with:

Workspace
└── Project
    ├── Tables ──── fields, views, records
    ├── Workflows ─ steps, runs
    ├── Scripts and webhooks
    ├── Classic apps ── pages
    ├── Dashboards ──── widgets
    └── Documents

listWorkspaces and listBases turn "my Sales project" into the IDs that the other tools need, so they are often the first calls. whoami shows what the connection can reach.

List workspaces and projects. Create and read projects. Rename a project or change its icon color. Delete a project that the connection created, if you switch on deleteBase as an opt-in tool. Get the web app URL for a table, view, workflow, classic app, dashboard, script, or document.

Two ways to connect

Connect an MCP client

Permissions

You choose what a client can do, on the NocoDB authorization screen or when you create an MCP connection. Pick the projects it can reach, then set a level for each section:

Self-hosted and Community Edition

• Licensed self-hosted: connect with OAuth the same way, with https://<your-nocodb-host>/mcp. This URL must be the public HTTPS address of your instance. NocoDB builds its sign-in addresses from NC_SITE_URL (or NC_PUBLIC_URL), so set it to that address.
• Community Edition: there is no OAuth. Create an MCP connection for each project, and connect a client that accepts a token. The connection gives the record tools only.

Other clients

Any MCP client can connect:

• If the client supports remote MCP servers with OAuth, add https://app.nocodb.com/mcp (or your self-hosted URL) and sign in to NocoDB.
• If the client accepts only a token, create an MCP connection and use its URL and token.

Skill guide and feedback

Outside the Community Edition, the server also exposes Generate Skill Guide (generateSkillGuide). It returns Markdown files covering the tools this connection can actually reach, area by area, along with the workspaces and projects it can see, for a client that keeps skills on disk to write under .claude/skills/nocodb-mcp. The bundle includes a SKILL.md entry point, so the folder works as a skill once the files are written. Ask for it once at the start of a session. Passing sections: ["scope"] returns only the reachable workspaces and projects, which is the part that changes most often. It sits outside the tool allowlist, so it is always offered, and it reports only what the connection itself can reach.

On NocoDB Cloud and licensed self-hosted deployments, the server also gives Submit Feedback (submitFeedback). With this tool, an MCP client reports a NocoDB bug, a call that reported success but did the wrong thing, a missing capability, a confusing behavior, or a docs gap to the NocoDB team. The report changes nothing in your workspace, and the call answers with a feedback id. You cannot read a report back.

NocoDB also tells the client to report a problem that it meets during a task, and to tell you what it reported. A report carries the client's own description of the problem, not your records.

Submit Feedback sits outside the tool allowlist, so every connection has it. It is available only where the deployment can deliver reports: NocoDB Cloud, and self-hosted deployments whose license carries feedback credentials.

Example prompts

• "List my NocoDB workspaces and projects."
• "Show me all projects with deadlines this week."
• "Create a task named 'Review Documentation'."
• "Mark the status of Project X as completed and reassign to John."
• "Link the onboarding tasks to the Acme project."
• "Summarize total revenue by month from the Sales project."
• "Add a Priority field to Tasks with options Low, Medium and High."
• "Create a kanban view of Tasks stacked by Status."
• "Build a workflow that sends me an email when a new order comes in."
• "Give the Sales team read-only access to the Invoices table."

Building an AI app?

This page is about connecting an AI assistant to your workspace. An AI app has its own API and MCP server, scoped to that app and its teams. See App API and MCP server.

Related

• Connections and access
• NocoDB APIs