Adobe Customer Journey Analytics
Run cross-channel reports and build segments in Adobe Customer Journey Analytics.
Read, write and restructure Airtable bases from your AI assistant.
Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.
Paste it into any MCP client. Setup docs
The Airtable MCP server connects your Airtable bases to Claude, ChatGPT and any MCP-compatible agent. It reads and writes records, and it also edits structure — creating and updating tables and fields, building interfaces, and drafting automations. Sign-in is OAuth against Airtable, with a consent screen that lets you pick which bases the agent may touch.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
data.records:write — the same scope as a routine edit. There is no separate delete scope.update_field's effect on existing cell values during a type conversion is undocumented. The REST endpoint exposes no type parameter; the MCP example prompt implies conversion. We could not resolve the contradiction from public sources.revert_action's eligibility rules are unpublished. Do not treat undo as a general safety net.Yes, and Anthropic's directory listing does not show it. Airtable's own tools reference documents `delete_records_for_table`, `delete_table`, `delete_interface`, `delete_page` and `delete_automation`, none of which appear in the twelve tool names the directory publishes. A reader who judged the connector's reach from the directory listing alone would conclude it cannot delete anything, and would be wrong on five counts.
Grant four of the seven scopes and drop the three write ones. Airtable's help centre documents the exact read-only set as `data.records:read`, `schema.bases:read`, `data.recordComments:read` and `workspacesAndBases:read`. Omitting `schema.bases:write` blocks every structural change while leaving reads intact, so the schema half of the grant can genuinely be declined.
Airtable documents type-specific option changes, not type conversion. The Web API update-field endpoint takes name, description and options only, with no type parameter, and Airtable's own example prompt for `update_field` describes converting a field to a single select. The docs do not state what happens to existing cell values in that case, so treat the gap as unresolved rather than safe.
Airtable does not document the answer for MCP writes specifically. Its help centre states the MCP server uses the public API underneath, and Airtable automations offer record-created and record-updated triggers, so a write plausibly fires them. Because Airtable publishes no explicit statement about MCP-initiated triggers, treat outbound effects such as emails or webhooks as possible and untested.
Only the ones you pick during authorization. Airtable's developer docs state that the OAuth flow lets you choose exactly which bases, apps and workspaces to connect, and its help centre describes adding or removing bases afterwards from the third-party integrations page. This is real per-base granularity, not an all-or-nothing grant across your whole account.
Sometimes, through a dedicated tool. Airtable's tools reference documents `revert_action`, which reverts a previous eligible mutation by action ID. The word eligible is Airtable's and it is not defined in the reference, so the set of reversible operations is unpublished. Structural deletions such as `delete_table` carry no documented reversal path at all.
No. Airtable's help centre lists plan availability for the MCP server as all plans, and states there are no additional Airtable charges for MCP usage. Existing API rate limits still apply. On enterprise accounts an admin may have to allowlist the integration first, which is a permission gate rather than a billing one.
Five requests per second per base. Airtable's Web API rate limits page documents that ceiling, plus 50 requests per second across all personal access token traffic from one user or service account. Exceeding either returns a 429 and requires a 30-second wait. The MCP server inherits these because it runs on the same public API.
Yes, on enterprise accounts. Airtable documents a third-party integration allowlist under Admin Panel, Settings, Integrations and development. Where restrictions are enabled the MCP integration will not connect until an admin adds its client ID to the allowlist. Individual users can also revoke a connection from their own third-party integrations page at any time.
documentation URL at /docs/using-the-airtable-mcp-server redirects here) · retrieved 2026-08-18.md suffix affordance) · retrieved 2026-08-18WWW-Authenticate challenge on https://mcp.airtable.com/mcp — observed 2026-08-18 · retrieved 2026-08-18support.airtable.com/robots.txt allowlists ClaudeBot, Claude-User and Claude-SearchBot by name; airtable.com/robots.txt permits /developers/. No Content-Signal directive on either host (checked 2026-08-18). · retrieved 2026-08-18Connect Airtable once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.