The `airtable-mcp-server` package provides a Model Context Protocol (MCP) server designed to enable Large Language Models (LLMs) with read and write access to Airtable databases. It exposes a set of tools allowing LLMs to inspect Airtable schemas, then read and write records. The current stable version is 1.13.0, indicating a pre-1.x release cadence focusing on feature additions and minor fixes, with frequent patch and minor updates. Key differentiators include its adherence to the Model Context Protocol, providing structured access to Airtable via LLMs, and its ease of deployment via `npx` or integration with platforms like Claude Desktop, Cursor, and Cline. It handles schema inspection, record manipulation, and attachment uploads, abstracting Airtable's API for AI agents.
npm install airtable-mcp-serverVerified import paths — ran on the pinned version, not inferred.
This quickstart demonstrates how to programmatically start the Airtable MCP server using its `startServer` function, configuring it with an Airtable API key and an optional base ID, and setting up a basic shutdown handler.
Review the new MCP SDK architecture and update any custom server logic or extensions to align with the changes introduced in v1.9.6.
Upgrade to v1.13.0 or newer to benefit from the fix that addresses body size limits. If on an older version and unable to upgrade, manual configuration of `express.json({ limit: '...' })` might be necessary if running programmatically.Review your data payloads for `createRecord` and `updateRecords` operations to ensure they are compatible with Airtable's typecasting behavior. Adjust data types if unintended coercions occur.
Update any tools or configurations that consume the server's `server.json` metadata to conform to the new schema introduced in v1.9.1.
Set the `AIRTABLE_API_KEY` environment variable with a valid Airtable Personal Access Token (e.g., `export AIRTABLE_API_KEY='pat123.abc123'`). Ensure the token has appropriate scopes and access to the desired bases.
Upgrade to `airtable-mcp-server` v1.13.0 or newer. If running an older version programmatically, you might need to manually configure the `express.json` middleware with a larger `limit` option.
This issue was resolved in v1.10.0. Ensure you are using `airtable-mcp-server` v1.10.0 or newer.