NocoDB

This connector uses the NocoDB v3 API and is read-only.

Setup:

1. In NocoDB, open Team & Settings > API Tokens and create a token. Use a token with read-only access where possible; this adapter never sends write requests.
2. Set NOCODB_API_TOKEN to that token.
3. Set NOCODB_URL to the root NocoDB host, with no trailing slash. For NocoDB Cloud use https://app.nocodb.com. For self-hosted NocoDB use your own host, for example https://nocodb.example.com.

Authentication: NocoDB API tokens use the xc-token header. This adapter sends the header correctly. API tokens apply to the entire NocoDB instance; to limit access, create a token from a user account that only has the needed permissions.

Discovery order: call nocodb_list_workspaces first, then nocodb_list_bases for the workspace you want, then nocodb_list_tables for the base. IDs follow a chain: workspace IDs start with w, base IDs start with p, table IDs start with m or use a longer alphanumeric string, and record IDs are numeric. Always discover IDs from the parent level before querying the child level.

Records and filtering: before filtering or sorting records, call nocodb_get_table to learn the exact field names and types. The where parameter uses the NocoDB filter syntax: (field,eq,value) for a single condition, joined with ~and or ~or for multiple conditions, for example (Status,eq,Open)~and(Priority,eq,High). The sort parameter is JSON: one object or an array of objects with field and direction (asc or desc), for example [{"field":"CreatedAt","direction":"desc"}]. Field names must exactly match what nocodb_get_table returns.

Pagination: pageSize is silently capped at 100 on NocoDB Cloud and 1000 on self-hosted instances. Use nocodb_count_records to learn the total before paging through large tables.

Rate limiting: NocoDB enforces approximately 5 requests per second per user, shared by all of the user's tokens. If the limit is hit, the API returns HTTP 429 with a Retry-After header (see https://nocodb.com/docs/apis/errors).

Self-hosted instances: if the 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. On AnythingMCP Cloud, only publicly reachable NocoDB instances work.

Community Edition note: unlicensed self-hosted NocoDB may have a single implicit workspace. In that case, nocodb_list_workspaces may return one entry or an empty list; proceed directly to nocodb_list_bases with the known workspace ID or skip to tables if the base ID is already known.

Out of scope: creating, updating, or deleting records, tables, bases, or workspaces; views APIs (plan-gated); attachments; webhooks; and the deprecated v1/v2 APIs.