NocoDB MCP

NocoDB's MCP server exposes a base to AI clients as a set of record operations, so a team can run a spreadsheet style database conversationally. An agent can create records, read and filter them, update existing rows, and delete them, which covers requests such as adding a task with a due date, listing projects with deadlines this week, changing a status and reassigning an owner, or clearing records that match a condition. A base information tool returns the workspace and base metadata the connector can see, which is how the agent discovers the tables and fields available before acting. The scope is deliberately limited to records. Schema operations such as creating tables, adding fields or changing other metadata are not exposed, so an agent can fill and maintain a base but cannot restructure it. For a tool whose main risk is an assistant reorganizing a team's data unprompted, that boundary is the right one. Two connection styles are documented. Desktop clients such as Claude Desktop, Cursor and Windsurf use a JSON configuration with the server endpoint and a token header. Web clients including Claude and ChatGPT use an OAuth flow where the user authorizes specific workspaces and bases, and permissions can be set per tool so a given action either always asks for confirmation or runs unsupervised. It suits small teams running operations, content calendars or project tracking in NocoDB who want an assistant that maintains the base rather than dictating updates to a human.