NocoDB MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NOCODB_BASE_URL | Yes | The base URL of your NocoDB instance | |
| NOCODB_API_TOKEN | Yes | Your NocoDB API token (can be obtained from profile settings) | |
| NOCODB_DEFAULT_BASE | No | Optional default base ID to use |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_basesB | List all available NocoDB bases/projects |
| get_base_infoB | Get detailed information about a specific base/project |
| list_tablesC | List all tables in a base |
| get_table_infoC | Get detailed information about a table including its schema |
| create_tableC | Create a new table in a base with specified columns. Supports various column types including SingleSelect (with options), PhoneNumber, QrCode, and Barcode. |
| delete_tableC | Delete a table from the database |
| add_columnB | Add a new column to an existing table. For SingleSelect: provide options in meta. For QrCode/Barcode: provide reference column ID. PhoneNumber uses standard text storage. |
| delete_columnC | Delete a column from a table |
| insert_recordC | Insert a single record into a table |
| bulk_insertC | Insert multiple records into a table |
| get_recordC | Get a single record by ID |
| list_recordsC | List records from a table with optional filtering, sorting, and pagination |
| update_recordC | Update a single record |
| delete_recordC | Delete a single record |
| search_recordsC | Search for records containing a query string |
| list_viewsC | List all views for a table |
| create_viewC | Create a new view for a table |
| get_view_dataC | Get records from a specific view |
| queryC | Execute an advanced query with filtering, sorting, and field selection |
| aggregateC | Perform aggregation operations on a column |
| group_byC | Group records by a column and get counts |
| upload_attachmentC | Upload a file attachment to NocoDB storage |
| upload_attachment_by_urlC | Upload files to NocoDB storage from URLs |
| attach_file_to_recordC | Attach an uploaded file to a record |
| get_attachment_infoC | Get information about file attachments in a record |
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 25 tools
Most tools have distinct purposes, but there is some overlap between 'list_records', 'get_view_data', 'query', and 'search_records' which could cause confusion in selection. However, descriptions clarify their specific use cases, such as 'query' for advanced operations and 'search_records' for text-based searches, mitigating ambiguity.
Tool names follow a consistent verb_noun pattern (e.g., 'list_bases', 'create_table', 'delete_record'), with minor deviations like 'aggregate' and 'group_by' that are still clear. Overall, the naming is predictable and enhances readability, though not perfectly uniform.
With 25 tools, the count is borderline high for a database management server, potentially overwhelming. While it covers extensive operations, it might be slightly heavy for typical agent use, leaning towards the upper limit of reasonable scope.
The tool set provides comprehensive CRUD and lifecycle coverage for NocoDB operations, including base, table, column, record, view, and attachment management. No obvious gaps are present; it supports creation, retrieval, updating, deletion, and advanced querying across all relevant entities.