6sense
Ask an AI agent about 6sense account insights, buying signals and keyword trends.
Query and edit NocoDB records from an AI agent.
Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.
Paste it into any MCP client. Setup docs
The NocoDB MCP server connects a NocoDB base to Claude and any MCP-compatible agent. Its 11 listed tools read table schemas, query, count and aggregate records, read attachments, and create, update and delete records. On Cloud and licensed deployments the surface extends well past records.
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.
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
deleteRecords is a single call and NocoDB's own example is a bulk delete. No two-phase confirmation is published.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.
nocodb.com/docs/product, is a different page; the canonical MCP page is cited above. · retrieved 2026-09-13https://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 at https://app.nocodb.com/.well-known/oauth-protected-resource returns 200 naming https://app.nocodb.com as the authorization server with an empty scopes_supported array (2026-09-13) · retrieved 2026-09-13Connect NocoDB once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.