nocodb-mcp-connector
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_AUTH_TOKEN | No | Secret token used to authenticate HTTP requests to the MCP server (required for HTTP mode, optional for stdio) | |
| NOCODB_BASE_URL | Yes | The base URL of your NocoDB instance, e.g. https://app.nocodb.com | |
| NOCODB_API_TOKEN | Yes | Your NocoDB API token |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_workspacesA | List NocoDB workspaces visible to this API token. Only relevant on NocoDB Cloud; self-hosted OSS instances typically don't use workspaces — call list_bases directly instead. |
| list_basesA | List NocoDB bases (projects) visible to this API token. Pass workspace_id on NocoDB Cloud if you have multiple workspaces; omit it for self-hosted OSS instances. |
| list_tablesA | List tables within a NocoDB base, including each table's id, name, and type. |
| get_table_schemaA | Get full schema for a table: its fields/columns, types, options (e.g. select choices), and relational (Links) fields with their linkFieldId. Call this before creating/updating records so you know valid field names and link field ids. |
| list_recordsA | List records from a table, with optional filtering, sorting, field selection, and pagination. |
| get_recordB | Get a single record by its Id. |
| count_recordsB | Count records in a table, optionally matching a filter. |
| create_recordsB | Create one or more records in a table. |
| update_recordsB | Update one or more existing records. Each record object must include its Id plus the fields to change. |
| delete_recordsC | Delete one or more records by Id. |
| list_linked_recordsB | List the records currently linked to a given record through a relational (Links) field. |
| link_recordsA | Link one or more existing records to a given record through a relational (Links) field (e.g. attach child records to a parent). |
| unlink_recordsB | Remove a link between a record and one or more related records through a relational (Links) field. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 13 tools
Each tool targets a distinct resource and action. list_bases vs list_workspaces are clearly separated by workspace vs base, and descriptions clarify usage. list_records vs get_record differ in list vs single retrieval.
All tools use verb_noun snake_case (list_bases, create_records, link_records, etc.) with no mixed conventions or vague verbs. The pattern is immediately predictable.
13 tools is appropriate for a database connector covering base/table discovery, schema introspection, record CRUD, querying, and link management. Each tool earns its place.
Core workflows are well-covered: explore bases/tables/schema, then create/update/delete/query records and manage links. Minor gaps include no create/delete base or table, but these may be outside the connector's scope.