NocoDB
by NocoDB
Query and edit NocoDB records from an AI agent. 11 record tools on every edition; Cloud adds table, view and permission management.
Connection verified
Connection checked by Agentman on .
Listed in Anthropic’s Connectors Directory at community tier — a listing, not a partner-level review.
Anthropic states this reflects the level of review a connector received, not a security audit.
Connect NocoDB via MCP
https://app.nocodb.com/mcpWorks in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.
Use in Agentman
Connect NocoDB once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.
Open in Agentman StudioNocoDB Tools & Capabilities (11)
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
Limits
deleteRecordsis a single call and NocoDB's own example is a bulk delete. No two-phase confirmation is published.- The real surface depends on your edition. Cloud and licensed self-hosted expose schema, workflow and permission tools that the portable 11 do not include.
- Permission tools can change visibility, including Record-Level Security policies — a larger grant than data editing.
- Your base role is the ceiling, which is also the main mitigation: viewers read, editors write, and audit behaves as it does through the REST API.
- The endpoint returns an application error to unauthenticated requests rather than a standard challenge, which can read as a dead URL.
- We did not read tool schemas. The endpoint requires OAuth, so names come from Anthropic's directory and behaviour from NocoDB's documentation. We exercised no tool.
Frequently asked questions
Yes. deleteRecords is one of the eleven tools every NocoDB edition exposes, alongside createRecords and updateRecords. NocoDB's own sample prompt for the delete action is removing all tasks assigned to a person, so bulk deletion is the documented intent. No two-phase confirmation is published for it.
Yes. Every edition exposes the record tools, but NocoDB documents that Cloud and licensed self-hosted deployments also expose tools for tables and fields, views, scripts, dashboards, webhooks, comments, interfaces, workflows, permissions, documents, import and export, duplication, row colouring, and folders and members.
On Cloud and licensed self-hosted deployments, yes. NocoDB lists setting table and field permissions and Record-Level Security policies among the workspace tools. That is a notable capability to grant an agent, because it can alter who sees what rather than only changing data within existing rules.
Yes. NocoDB documents that tools respect the token owner's base role — viewers can read and editors can write — and that each tool wraps the same service as the matching REST API, so validation, permissions and audit behave identically. The connector inherits your existing base role rather than bypassing it.
Because an unauthenticated request has no base context. Requesting the endpoint directly returns a NocoDB application error about a base not being found, rather than a protocol response. The server is running and OAuth-protected — it publishes RFC 9728 metadata at the same host — so that error is not a sign the endpoint is wrong.
Both desktop and web. NocoDB publishes configuration for Claude, Cursor, Windsurf, AntiGravity and Codex as desktop clients with a JSON example, and separate OAuth setup steps for web-based clients including Claude Web and ChatGPT, with a section on configuring tool permissions in Claude Web.
Sources
- NocoDB MCP Server documentation (retrieved 2026-09-13), source of the per-edition tool split, the sample prompts and the base-role behaviour. Note the URL Anthropic's directory publishes,
nocodb.com/docs/product, is a different page; the canonical MCP page is cited above. · retrieved 2026-09-13 - Live OAuth posture check against
https://app.nocodb.com/mcp— an unauthenticated POST returns a NocoDB application error (ERR_BASE_NOT_FOUND) rather than a Bearer challenge, while RFC 9728 metadata athttps://app.nocodb.com/.well-known/oauth-protected-resourcereturns 200 naminghttps://app.nocodb.comas the authorization server with an emptyscopes_supportedarray (2026-09-13) · retrieved 2026-09-13 - Anthropic Connectors Directory entry (retrieved 2026-09-13) · retrieved 2026-09-13
- NocoDB support — <support@nocodb.com> · Privacy
Server Info
- Category
- Productivity
- Developer
- NocoDB
- Tools
- 11
- Domain
- app.nocodb.com
Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.
Similar MCP Servers for Productivity
Related Resources
Ready to connect NocoDB?
Connect NocoDB once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.