AITable MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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_spacesB | Fetches all workspaces that the currently authenticated user has permission to access. |
| search_nodesC | Retrieve nodes based on specific types, permissions, and queries. Nodes in AITable can be of several types: datasheets (also known as sheets, or spreadsheets), form, dashboard, and folders. |
| list_recordsC | Read the records from a specified datasheet with support for pagination, field filtering, and sorting options. |
| get_fields_schemaB | Returns the JSON schema of all fields within the specified database, This schema will be sent to LLM to help the AI understand the expected structure of the data. |
| create_recordC | Create a new record in the datasheet. Extract key information from user-provided text based on a predefined Fields JSON Schema and create a new record in the datasheet as a JSON object. |
| upload_attachment_via_urlA | Upload an attachment to the AITable server using its web URL. Returns storage information that can be passed to create_record or update_record tools to associate with a specific records. |
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 6 tools
Each tool has a clearly distinct purpose with no overlap: create_record (create), get_fields_schema (metadata), list_records (read), list_spaces (workspace access), search_nodes (search), and upload_attachment_via_url (attachment handling). The descriptions reinforce unique functions, preventing agent misselection.
All tools follow a consistent verb_noun or verb_noun_preposition pattern (e.g., create_record, get_fields_schema, list_records, list_spaces, search_nodes, upload_attachment_via_url). The naming is uniform and predictable, using snake_case throughout without any deviations.
With 6 tools, this server is well-scoped for managing AITable resources. The count covers essential operations (CRUD-like actions, metadata retrieval, search, and attachment handling) without being overly sparse or bloated, fitting typical server purposes.
The tool set provides strong coverage for core AITable operations, including create, read, search, and attachment management, with clear support for metadata and workspace access. A minor gap exists in update/delete operations for records, which agents might need to work around, but the surface is largely complete for the domain.