NocoDB logoMCP server · Databases and warehouses

NocoDB MCP server

NocoDB in any MCP client, through Memtro: NocoDB does not publish this server. Memtro's NocoDB connector reads NocoDB through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.

What the model can do

NocoDB bases on NocoDB Cloud or a self-hosted server: tables, fields and rows with filters and counts. Can add, upsert, link, change and delete rows, comment, create and change bases, tables and fields, and run button actions and workflows when asked.

Reads

  • nocodb_list_basesNocoDB workspaces and the bases in each: base id and title.
  • nocodb_list_tablesTables in a NocoDB base: id, title, description.
  • nocodb_get_tableA NocoDB table's fields: title (what rows and filters use), type, and the choices of select fields.
  • nocodb_list_recordsRows of a NocoDB table, filtered with NocoDB's where syntax, sorted and paged.
  • nocodb_count_recordsHow many rows of a NocoDB table match a where filter (or all rows).

Acts, when you ask

These change something in NocoDB. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

  • nocodb_create_recordsAdd new rows to a NocoDB table, only when the person asked.
  • nocodb_create_commentAdd a comment (markdown) to a NocoDB row, only when the person asked.
  • nocodb_update_recordsChange fields of existing NocoDB rows, only when the person asked.
  • nocodb_delete_recordsDelete rows from a NocoDB table, only when the person explicitly asked to delete them.
  • nocodb_upsert_recordsAdd or update NocoDB rows matched on 1 to 3 fields, only when the person asked.
  • nocodb_create_tableCreate a new table in a NocoDB base, only when the person asked, optionally with its first fields.
  • nocodb_update_tableRename a NocoDB table, change its description or its display field, only when the person asked.
  • nocodb_delete_tableDelete a NocoDB table and every row in it, only when the person explicitly asked to delete that table.
  • nocodb_create_fieldAdd a field (column) to a NocoDB table, only when the person asked.
  • nocodb_update_fieldRename a NocoDB field or change its description or default value, only when the person asked.
  • nocodb_delete_fieldDelete a field (column) from a NocoDB table and its value in every row, only when the person explicitly asked to delete that field.
  • nocodb_link_recordsLink rows of the related table to a NocoDB row through a Link field, only when the person asked.
  • nocodb_unlink_recordsRemove links between a NocoDB row and rows of the related table on a Link field, only when the person asked.
  • nocodb_update_commentReplace the text of a NocoDB row comment, only when the person asked.
  • nocodb_delete_commentDelete a NocoDB row comment, only when the person explicitly asked.
  • nocodb_resolve_commentToggle a NocoDB row comment between resolved and open, only when the person asked: a resolved comment is reopened.
  • nocodb_run_button_actionRun a Button field's action (for example AI generation) on named NocoDB rows, only when the person asked.
  • nocodb_run_workflowStart a NocoDB workflow whose trigger is manual, only when the person asked.
  • nocodb_create_baseCreate a new, empty NocoDB base in a workspace, only when the person asked.

Connect it

First connect NocoDB on Dashboard → Connections, then add Memtro to your client once. The NocoDB tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

Claude Code

The Memtro plugin registers the server and a skill for when to use it; the tools are then available in every session.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

Cursor

Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Claude Desktop

Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…

OpenCode

A remote server in opencode.json.

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Pi

One command: pi mcp add memtro --url https://platform.memtro.com/api/mcp --bearer-token-env-var MEMTRO_API_KEY. Tools arrive as mcp__memtro__*. The pi-memtro extension registers it for you, alongside Memtro as the model.

Any other client

Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared NocoDB connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

  • › How many support requests in NocoDB are still open?
  • › Which orders from Acme are marked unpaid?
  • › What fields does the Inventory table have?
  • › Mark the Northwind order as shipped
  • › Add a Priority field to the Tickets table

Questions

Is this an official NocoDB MCP server?
No. It is Memtro's MCP server with Memtro's NocoDB connector behind it: the connector reads NocoDB through its API with the credentials you connect on Dashboard → Connections, and NocoDB publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.
What does it cost?
Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.
Can it change anything in NocoDB?
Only when you ask, and only what it has been granted: add rows to a table; comment on a row; change fields of existing rows; delete rows from a table; add or update rows matched on up to three fields; create a table; rename a table or change its description or display field; delete a table and all its rows; add a field to a table; rename a field or change its description or default; delete a field and its data; link rows through a Link field; unlink rows on a Link field; edit a row comment; delete a row comment; resolve or reopen a row comment; run a button field's action on named rows; run a manual-trigger workflow; create a base in a workspace. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.
Which clients work?
Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · Databases and warehouses

Where agents remember your company

Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.

7-day free trial · card on file, nothing charged until it ends · cancel any time