create_record
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.
Find the datasheet inside an AITable space, read its records with filters and sorting, and file new ones with attachments pulled in from a URL.
LABSCO SUMMARY
The read path runs spaces, then a node search, then records, with pagination, field filtering and sorting available on the way down. Writing is the part worth having: the schema of the target datasheet goes to the model first, so a new record fills a known structure rather than guessing at column names. Attachments arrive by web URL rather than from local disk, and the storage information that comes back is what gets attached to the row.
A server over AITable workspaces — spaces, datasheets, forms, dashboards and folders — that reads records out of a datasheet and creates new ones in it.
An AITable account with permission on the spaces you want to reach; every tool acts as the currently authenticated user.
One command plus a key — npx -y @apitable/aitable-mcp-server, then supply credentials
USE CASES
The field schema is fetched first and handed to the model, which then pulls the values out of the user's text into a record that matches the datasheet.
The spaces the account can open are listed, a node search narrows to the datasheets matching a query, and the records come back paginated.
A formula filter, a field list and a sort order cut the datasheet down to the rows and columns the report needs, one page at a time.
The attachment is uploaded from its URL and the storage information that comes back is passed straight into the record being created.
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
create_recordCreate 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.
get_fields_schemaReturns 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.
list_recordsRead the records from a specified datasheet with support for pagination, field filtering, and sorting options.
list_spacesFetches all workspaces that the currently authenticated user has permission to access.
search_nodesRetrieve 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.
upload_attachment_via_urlUpload 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.
BEFORE YOU INSTALL
6 tools when we connected. update_record is documented but marked TODO, so records can be created and given attachments but not edited or deleted.
Both documented clients run the server on your machine.
CONTEXT COST
Rated by the size of the 6 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
npx -y @apitable/aitable-mcp-server{
"mcpServers": {
"aitable": {
"command": "npx",
"args": [
"-y",
"@apitable/aitable-mcp-server"
],
"env": {
"AITABLE_API_KEY": "<YOUR_AITABLE_API_KEY>"
}
}
}
}{
"mcpServers": {
"aitable": {
"command": "cmd",
"args": [
"/c",
"npx",
"-y",
"@apitable/aitable-mcp-server"
],
"env": {
"AITABLE_API_KEY": "<YOUR_AITABLE_API_KEY>"
}
}
}
}