create_comment
Create a comment on a record
LABSCO SUMMARY
It edits the schema, not only the rows.
Most table connectors stop at reading and writing records; this one creates tables and fields too, so a base can be reshaped in the same conversation that fills it. Two limits shape how you batch work: ten records per update call, and 5 MB per attachment, with anything larger having to arrive as a public URL on a record write.
What it is
An Airtable client covering both planes of a base: the data (records, comments, attachments) and the schema (tables and fields). What it can reach is exactly what your personal access token can reach.
What you get
- Record reads with Airtable's own query surface: a filterByFormula expression, a sort, a named view, a chosen field subset and a record cap that starts at 100
- Free-text search across every text field, or a named subset of them, for when you do not have a formula in mind
- Record writes: create one, update up to 10 in a single call, delete by id, and fetch one back by id
- The schema as data — every base the token can reach, the tables inside one, and a table described down to its fields, at the detail level you ask for
- Schema changes in place: create a table, rename or re-describe it, add a field, rename or re-describe a field
- Comments on a record, read and written, including a reply to an existing comment
- A file uploaded straight into an attachment field, up to 5 MB, with anything larger going in as a public URL through a record write
Requirements
An Airtable personal access token in AIRTABLE_API_KEY, and the scopes decide what works: schema.bases:read and data.records:read to look, schema.bases:write and data.records:write to change anything, and the record-comment scopes for the comment tools. Grant it access only to the bases you want reachable — the base listing returns exactly what the token can see. Node.js for npx, or a published Docker image or .mcpb bundle instead. Attachment upload needs a record that already exists.
Setup effort
One command plus a key — npx -y airtable-mcp-server, then supply credentials
USE CASES
01
Finding your way around a base you did not build
List the bases the token can see, then the tables, then one table's fields — at the level of detail you actually need.
02
Answering a question about the records
Filter with an Airtable formula, or search the text fields when you do not know the formula, and read only the fields that matter.
03
Applying a batch of edits you have agreed
Update up to ten records per call, and delete the ones that should not be there.
04
Adding structure the base is missing
Create the table and its fields in the same conversation that decided they were needed.
05
Attaching a file to a record
Upload it straight into the attachment field — under 5 MB, on a record that already exists.
06
Leaving a note where the team will see it
Read the comments on the record and reply in the same thread rather than starting a new one.
16 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
create_field
Create a new field in a table
create_record
Create a new record in a table
create_table
Create a new table in a base
delete_records
Delete records from a table
describe_table
Get detailed information about a specific table
get_record
Get a specific record by ID
list_bases
List all accessible Airtable bases
list_comments
List comments on a record
list_records
List records from a table
list_tables
List all tables in a specific base
search_records
Search for records containing specific text
update_field
Update a field's name or description
update_records
Update up to 10 records in a table
update_table
Update a table's name or description
upload_attachment
Upload a file directly to an attachment field on an existing record using Airtable's upload API. Supports files up to 5 MB. For larger files, use create_record or update_records with a public URL. The record must already exist.
BEFORE YOU INSTALL
What to know first
Tools you get
16 tools when we connected. upload_attachment is missing from the documentation. Token scopes decide what succeeds: with only schema.bases:read and data.records:read, write tools are listed but fail, and comment tools also need data.recordComments:read / :write.
Requires
- npx on PATH
- AIRTABLE_API_KEY in your environment
CONTEXT COST
Light Standing cost
Rated by the size of the 16 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
npx -y airtable-mcp-serverMCP Clients
Any MCP client — npx
ANY MCP CLIENT — NPX · JSON
{
"mcpServers": {
"airtable": {
"command": "npx",
"args": [
"-y",
"airtable-mcp-server"
],
"env": {
"AIRTABLE_API_KEY": "<YOUR_AIRTABLE_API_KEY>"
}
}
}
}HTTP server
Put your Airtable token in AIRTABLE_API_KEY, then start the server in HTTP mode:
HTTP SERVER · TERMINAL
MCP_TRANSPORT=http PORT=3000 npx airtable-mcp-serverIt serves a stateless HTTP endpoint at http://localhost:3000/mcp; point a remote MCP client there. The HTTP transport has no built-in authentication, so run it only behind a reverse proxy or gateway that requires a credential. For a client on the same machine, use the stdio config instead.
