# NocoDB MCP Server

> Part of the NocoDB documentation (MCP Server). Index of all pages: https://nocodb.com/llms.txt. Any docs page is available as Markdown by adding `.md` to its URL.

URL: https://nocodb.com/docs/mcp
Last updated: 2026-10-22

The NocoDB MCP server lets Claude, ChatGPT, Claude Code, Cursor and other AI assistants work with your NocoDB data through 200 tools, with OAuth or a token.

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.

<McpEndpoints tryIt="List my NocoDB workspaces and projects.">
  <McpEdition name="NocoDB Cloud" hint="Sign in with OAuth. Nothing to install, no token to copy." url="https://app.nocodb.com/mcp">
    1. Copy the URL.
    2. Paste it into your AI client, where it adds an MCP server or connector.
    3. Sign in to NocoDB, choose the projects and tools, and click **Authorize**.
  </McpEdition>

  <McpEdition name="Self-hosted" hint="For licensed self-hosted NocoDB on a paid plan. Replace <your-nocodb-host> with your domain." url="https://<your-nocodb-host>/mcp">
    1. Set `NC_SITE_URL` to the public HTTPS address of your instance.
    2. Paste your URL into your AI client, where it adds an MCP server or connector.
    3. Sign in to NocoDB, choose the projects and tools, and click **Authorize**.
  </McpEdition>

  <McpEdition name="Community Edition" hint="The Community Edition has no OAuth. Connect with a connection URL and token instead." url="https://<your-nocodb-host>/mcp/<connection-id>">
    1. [Create an MCP connection](/docs/mcp/connections#server-configuration-nocodb) for a project.
    2. Copy its URL and token, or the ready-made config for your client.
    3. Paste it into your AI client. The client gets the record tools.
  </McpEdition>
</McpEndpoints>

## Pick your client

<McpClientGrid />

## 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](/docs/mcp/connections#connection-tools-and-access).

| Area                                           | What the assistant can do                                                                                                                                             | Tools |
| ---------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----- |
| [Records](/docs/mcp/records)                   | Query, count and aggregate records; create, update, upsert and delete them; link records, add attachments and comments; import and export CSV; restore from the trash | 36    |
| [Tables & fields](/docs/mcp/schema)            | Create and change tables, fields and select options, with a dry run before changes that can lose data; organize folders; duplicate projects, tables and fields        | 23    |
| [Views](/docs/mcp/views)                       | Create and configure views, filters, sorts, share links, form field conditions, view folders and row colors                                                           | 33    |
| [Workflows](/docs/mcp/automation)              | Build workflows step by step, test steps without running them, publish them and read their runs; manage webhooks and scripts                                          | 35    |
| [Apps & docs](/docs/mcp/apps-and-docs)         | Build classic apps and their pages, dashboards and widgets, and documents and their comments                                                                          | 46    |
| [Members & permissions](/docs/mcp/permissions) | Manage members and teams, table and field permissions and row-level security; read the audit log                                                                      | 24    |

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:

```text
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](/docs/mcp/connections#opt-in-tools). Get the web app URL for a table, view, workflow, classic app, dashboard, script, or document.

## Two ways to connect

|                | Sign in with OAuth                                      | MCP connection                                                                                          |
| -------------- | ------------------------------------------------------- | ------------------------------------------------------------------------------------------------------- |
| **How**        | Add the server URL to the client and sign in to NocoDB. | Create a connection in NocoDB and copy its configuration to the client.                                 |
| **Server URL** | `https://app.nocodb.com/mcp`                            | `https://<your-nocodb-host>/mcp/<connectionId>`, with a token                                           |
| **You choose** | Projects and tools, on the authorization screen         | Projects and tools, when you [create the connection](/docs/mcp/connections#server-configuration-nocodb) |
| **Editions**   | NocoDB Cloud, licensed self-hosted                      | All editions                                                                                            |
| **Best for**   | Claude, ChatGPT, Claude Code                            | Pinning a client to set projects, clients without OAuth, the Community Edition                          |

## Connect an MCP client

| Client                                                  | Easiest way                                                                      | Setup                                |
| ------------------------------------------------------- | -------------------------------------------------------------------------------- | ------------------------------------ |
| <ClientName logo="claude">Claude</ClientName>           | OAuth, from the Claude Connectors directory                                      | [Claude](/docs/mcp/claude)           |
| <ClientName logo="claude">Claude Code</ClientName>      | OAuth, with `claude mcp add`                                                     | [Claude Code](/docs/mcp/claude-code) |
| <ClientName logo="openai">ChatGPT</ClientName>          | OAuth, with a connector for `https://app.nocodb.com/mcp`                         | [ChatGPT](/docs/mcp/chatgpt)         |
| <ClientName logo="openai">Codex</ClientName>            | MCP connection, TOML block                                                       | [Codex](/docs/mcp/codex)             |
| <ClientName logo="cursor">Cursor</ClientName>           | MCP connection, JSON block                                                       | [Cursor](/docs/mcp/cursor)           |
| <ClientName logo="windsurf">Windsurf</ClientName>       | MCP connection, JSON block                                                       | [Windsurf](/docs/mcp/windsurf)       |
| <ClientName logo="antigravity">AntiGravity</ClientName> | MCP connection, JSON block                                                       | [AntiGravity](/docs/mcp/antigravity) |
| <ClientName>Other MCP clients</ClientName>              | OAuth if the client supports remote MCP servers with OAuth, or an MCP connection | [Other clients](#other-clients)      |

## 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:

| Section                       | What it covers                                                             |
| ----------------------------- | -------------------------------------------------------------------------- |
| Account & workspaces          | Who you are, your workspaces, the projects in them, and links into the app |
| Records & data                | Records, comments, import and export                                       |
| Schema                        | Tables, fields, duplicating, and how a project is organized                |
| Views                         | Views, filters, sorts, sharing, form fields, row colors                    |
| Automation                    | Workflows, webhooks and scripts                                            |
| Interfaces, dashboards & docs | Classic app pages, dashboards, widgets, and documents                      |
| Access & security             | Members, field and table permissions, row-level security                   |

| Level                    | What it allows                                           |
| ------------------------ | -------------------------------------------------------- |
| **Read**                 | The read tools of the section                            |
| **Read & write**         | The above, plus the tools that create and change         |
| **Read, write & delete** | The above, plus the tools that delete, remove or unshare |
| **None**                 | No tools of the section                                  |

<Callout type="warning">
  Every section starts at 

  **Read, write & delete**

  . To make sure that a client can never delete anything, set each section to 

  **Read & write**

   or lower. See 

  [Connections and access](/docs/mcp/connections#connection-tools-and-access)

  .
</Callout>

## 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](/docs/mcp/connections#server-configuration-nocodb) 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](/docs/mcp/connections#connection-tools-and-access), 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](/docs/mcp/connections#connection-tools-and-access), 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](/docs/apps) has its own API and MCP server, scoped to that app and its teams. See [App API and MCP server](/docs/apps/api-and-mcp).

## Related

* [Connections and access](/docs/mcp/connections)
* [NocoDB APIs](/docs/apis)

<LegacyAnchors
  map={{
"desktop-llm-clients": "/docs/mcp/connections#server-configuration-nocodb",
"server-configuration-nocodb": "/docs/mcp/connections#server-configuration-nocodb",
"client-configuration": "/docs/mcp#connect-an-mcp-client",
"claude-code": "/docs/mcp/claude-code",
"claude": "/docs/mcp/claude#claude-desktop-with-an-mcp-connection",
"cursor": "/docs/mcp/cursor",
"windsurf": "/docs/mcp/windsurf",
"antigravity": "/docs/mcp/antigravity",
"codex": "/docs/mcp/codex",
"json-example": "/docs/mcp#connect-an-mcp-client",
"web-based-llm-clients-oauth": "/docs/mcp/connections#web-based-llm-clients-oauth",
"claude-web": "/docs/mcp/claude",
"setup-steps": "/docs/mcp/claude#self-hosted-nocodb",
"configure-tool-permissions": "/docs/mcp/claude#tool-permissions-in-claude",
"using-nocodb-tools-in-claude-web": "/docs/mcp/claude",
"chatgpt": "/docs/mcp/chatgpt",
"prerequisites": "/docs/mcp/chatgpt",
"setup-steps-1": "/docs/mcp/chatgpt#connect-chatgpt",
"using-nocodb-tools-in-openai-web": "/docs/mcp/chatgpt#use-nocodb-in-a-chat",
"guided-setup-from-the-app": "/docs/mcp#connect-an-mcp-client",
"available-tools": "/docs/mcp#what-you-can-do",
"connection-tools-and-access": "/docs/mcp/connections#connection-tools-and-access",
"api-call-usage": "/docs/mcp/connections#api-call-usage",
}}
/>

---

## Related pages

- [MCP Connections and Access](https://nocodb.com/docs/mcp/connections.md): Create a NocoDB MCP connection, choose the projects it can reach and the tools it can call, and authorize web clients such as Claude and ChatGPT with OAuth.
- [Records and Data with NocoDB MCP](https://nocodb.com/docs/mcp/records.md): NocoDB MCP tools for records: query, aggregate, create, update and delete records, link them, add attachments and comments, import and export CSV.
- [Tables and Fields with NocoDB MCP](https://nocodb.com/docs/mcp/schema.md): NocoDB MCP tools for structure: create and change tables, fields and select options, folders and duplicates, with a dry run before risky field changes.
- [Views with NocoDB MCP](https://nocodb.com/docs/mcp/views.md): NocoDB MCP tools for views: create and configure views, filters and sorts, share links, form field conditions, view folders, row coloring and date dependencies.
- [Workflows and Automation with NocoDB MCP](https://nocodb.com/docs/mcp/automation.md): NocoDB MCP tools for automation: build workflows step by step, test steps without running them, publish, and manage webhooks, scripts and automation folders.
- [Classic Apps, Dashboards and Docs with NocoDB MCP](https://nocodb.com/docs/mcp/apps-and-docs.md): NocoDB MCP tools for classic apps (interfaces), dashboards and widgets, and documents: create, configure, publish and share them through an AI assistant.
- [Members and Permissions with NocoDB MCP](https://nocodb.com/docs/mcp/permissions.md): NocoDB MCP tools for access: project and workspace members and teams, table and field permissions, row-level security policies and the audit log.
- [NocoDB Skills](https://nocodb.com/docs/mcp/skills.md): Use the NocoDB skill for Claude to list, create, update and delete NocoDB tables, fields, views and records through natural language with an API token.