Summary
Read NocoDB workspaces, bases, tables, and records from NocoDB Cloud or a self-hosted instance. 7 read-only tools using xc-token API key authentication against the v3 REST API.
Guided setup
Connect NocoDB to Meta Muse in 2 minutes
Start a free trial on AnythingMCP Cloud, connect NocoDB in the guided setup, then add your MCP URL to Meta Muse. No code and no server to run.
No credit card · 7-day trial · Self-host alternative available
Try asking
Example prompts for NocoDB
Click any prompt to copy it. Paste into Claude, ChatGPT, Cursor, Gemini, Copilot or OpenClaw to run it against this connector.
Claude is AI and can make mistakes. Please double-check responses.
💡 No install? Use cloud.anythingmcp.com directly. Sign in, click Connectors → NocoDB, paste your credentials, mint an MCP API key — done. No Docker, no
git clone, no local server.
NocoDB + Meta Muse
Read NocoDB workspaces, bases, tables, and records from NocoDB Cloud or a self-hosted instance. 7 read-only tools using xc-token API key authentication against the v3 REST API.
Prerequisites
See the full setup instructions baked into the connector (visible in the in-app store when you select the connector). The required environment variables for this connector are:
NOCODB_URL, NOCODB_API_TOKEN
Step 1 — Get credentials
Setting up takes about 2 minutes. You need your NocoDB address and an API token.
- In NocoDB, open Team & Settings → API Tokens and create a token. Use a token with read-only access where possible. Copy it into
NOCODB_API_TOKEN. - Set
NOCODB_URLto the root NocoDB host, without a trailing slash:https://app.nocodb.comon NocoDB Cloud, or your own host, for examplehttps://nocodb.example.com. - Install the connector and run
nocodb_list_workspaces: it lists the workspaces your token can see.
Token scope: NocoDB API tokens apply to the whole NocoDB instance and are sent in the xc-token header. To limit what the AI can see, create the token from a user account that has only the permissions it needs.
Where NocoDB runs: AnythingMCP Cloud reaches only publicly reachable NocoDB instances. If your NocoDB host is private or resolves to private address space, self-host AnythingMCP on the same network and allow the host through SSRF_ALLOWED_HOSTS, otherwise the outbound guard blocks the request.
What it reads: through the NocoDB v3 API, your workspaces, bases and tables, a table's columns with names and types, records, one record by its numeric row ID, and record counts. IDs follow a chain: nocodb_list_workspaces gives workspace IDs (starting with w), nocodb_list_bases base IDs (starting with p) and nocodb_list_tables table IDs. Before filtering or sorting, the AI calls nocodb_get_table for the exact field names. Filters use NocoDB syntax, for example (Status,eq,Open)~and(Priority,eq,High), and sorting is JSON, for example [{"field":"CreatedAt","direction":"desc"}].
Community Edition: an unlicensed self-hosted NocoDB may have a single implicit workspace, so nocodb_list_workspaces can return one entry or an empty list. Then go straight to nocodb_list_bases with the known workspace ID, or to the tables if you already know the base ID.
Limits: pageSize is silently capped at 100 on NocoDB Cloud and 1000 on self-hosted instances; nocodb_count_records gives the total before paging through a large table. NocoDB allows about 5 requests per second per user, shared by all of that user's tokens. Over that it returns HTTP 429 with a Retry-After header.
The connector is read-only: it does not create, update or delete records, tables, bases or workspaces, and it does not use views (plan-gated), attachments, webhooks or the deprecated v1 and v2 APIs.
Step 2 — Install the adapter
curl -fsSL https://raw.githubusercontent.com/HelpCode-ai/anythingmcp/main/docker-compose.quickstart.yml -o docker-compose.yml
printf 'JWT_SECRET=%s\nENCRYPTION_KEY=%s\n' "$(openssl rand -hex 32)" "$(openssl rand -hex 32)" > .env
docker compose up -d
Step 3 — Add the connector in Muse
Your server URL: in AnythingMCP, open MCP Servers → the server this connector is on, and copy its URL (
https://cloud.anythingmcp.com/mcp/…). Use it wherever this guide showsYOUR_SERVER_ID.
Muse adds remote MCP servers as custom connectors and signs in to them with OAuth.
- In Muse, open Settings → Connectors and choose Add custom connector.
- Paste the MCP server URL
https://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID. - Muse opens the AnythingMCP sign-in page: sign in and approve access.
- In a chat, ask Muse for something that needs the
NocoDBtools.
You can also set it up from a chat, on the web, in the iOS and Android apps or in WhatsApp. Send Muse this message:
Create a Custom Connector for a new remote MCP server, then connect to it:
Name: AnythingMCP
Transport: remote streamable HTTP
URL: https://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID
Auth: OAuth
Self-hosting? Use your instance's public HTTPS address instead of https://cloud.anythingmcp.com. Muse connects from Meta's cloud, so localhost does not work.
Available tools
| Tool | What it does |
|---|---|
nocodb_list_workspaces | List all workspaces visible to the configured API token |
nocodb_list_bases | List bases (projects) in a NocoDB workspace |
nocodb_list_tables | List tables in a NocoDB base |
nocodb_get_table | Get the full schema of one NocoDB table: its columns with names, types, and options |
nocodb_list_records | List records from a NocoDB table |
nocodb_get_record | Get one record by its numeric row ID from a NocoDB table |
nocodb_count_records | Count records in a NocoDB table, optionally filtered by a where clause |
FAQ
Where is Muse available? Meta currently offers Muse in the US and Canada, on the web, in the iOS and Android apps and in WhatsApp.
Does Meta review this connector? No. Meta doesn't review custom connectors. Muse sees only the tools you switched on for this MCP server in AnythingMCP, and you can disconnect it anytime under Settings → Connectors.
Next steps
Was this guide helpful?