CommunityActive· 13d★ 4.3by Adam Jones (domdomegg)

Airtable MCP

Airtable integration with schema inspection and read and write record access, backed by a personal access token.

View repo

Safety & Trust

Delv Safety Grade: B

Score 72/100 · assessed 2026-04-18

Maintainer55

Permissions65

Supply chain85

Transparency80

Incidents100

Airtable MCP is a community server by solo developer Adam Jones (domdomegg) that provides full read-write access to Airtable bases via personal access token. The implementation is clean and distributed through npm with standard installation, making supply chain risk moderate. The maintainer has reasonable GitHub activity but this is a single-person project with bus factor concerns. Permissions are moderately scoped: it can read and write database records plus inspect schemas, but access is limited to whatever the PAT allows in Airtable's own permission model. The token lives in environment variables which is appropriate, though it grants broad access to all bases the token can reach. Documentation is adequate and the code is open source. No known security incidents. The main risk is the combination of solo maintenance and write access to potentially business-critical data stores.

Green flags

Distributed via npm with standard versioning
Open source with clear repository and documentation
Schema inspection reduces blind write failures
Uses Airtable's native permission model for scoping
No known security incidents or credential leaks

Red flags

Solo maintainer with bus factor risk
Full write access to Airtable bases within token scope
Personal access token grants broad multi-base access
Limited community review for database write operations

Permissions requested

DB readDB writeOutbound networkAccess secrets

Assessed by Delv Editorial using public metadata. Grades are advisory and update as the ecosystem changes. They do not replace your own review of permissions and code before granting an agent access to sensitive systems.

Install

npx -y airtable-mcp-server

Env vars needed: AIRTABLE_API_KEY

Review

Airtable MCP bridges Claude to your Airtable bases with schema inspection and full read-write access. You authenticate with a personal access token, and Claude can then query tables, create records, update fields, and even introspect your base structure to understand what columns exist and what types they expect. I've used this to let Claude update a product inventory table after parsing supplier emails, and to enrich CRM records by pulling in data from other tools. The schema inspection is the standout feature: Claude can ask what fields are available before writing, which means fewer failed writes due to typos or missing columns. It's particularly good for repetitive data entry tasks where you'd otherwise be copying and pasting between tabs, or for building ad-hoc automations without touching Airtable's scripting layer. The setup is straightforward if you've generated Airtable tokens before. You'll need a personal access token with the right scopes (data.records:read and data.records:write at minimum), and you'll want to scope it to specific bases rather than your entire workspace. The MCP doesn't enforce any rate limiting on its own, so if you're working with large bases or running bulk operations, you'll need to keep Airtable's API limits in mind. One quirk: Airtable's API uses record IDs that look like recXXXXXXXXXXXXXX, and if you're asking Claude to update a specific record, you'll need to reference it by ID rather than by a human-readable field. This means you often need a two-step workflow: query to find the record, then update it. Not a dealbreaker, but it adds friction for one-off tasks. Who shouldn't bother: if your Airtable bases are purely for manual data entry and you're not doing any programmatic updates, this won't add much. It's also overkill if you're just reading data occasionally, since you could export a CSV and upload it to Claude directly. But if you're using Airtable as a lightweight database for projects, inventory, or CRM, and you want Claude to interact with it in real time, this is the cleanest way to do it.

Verdict

Install this if you treat Airtable as a working database and want Claude to read or write records without manual copy-paste. Skip it if your bases are static or you're not comfortable managing API tokens. It's a solid, no-frills integration that does exactly what it claims.

Good at

Schema inspection lets Claude see what fields and types exist before writing, which prevents most common errors.
Works with any Airtable base you can generate a token for, no special setup on the Airtable side.
Read and write access means you can build two-way workflows, not just pull data out.
Straightforward token-based auth with no OAuth dance or webhook configuration.

Watch out

No built-in rate limiting, so you'll hit Airtable's API limits if you're doing bulk operations without pacing.
Requires record IDs for updates, which means you often need a query step before modifying a specific record.
Personal access tokens expire and need manual rotation, which can break workflows silently.
Limited to Claude Desktop, Cursor, and Claude Code unless you configure other hosts manually.

Use cases

CRM updates
inventory management
no-code workflows
record enrichment

Getting started

1. Generate a personal access token in Airtable's developer settings with data.records:read and data.records:write scopes, limited to the bases you want Claude to access. 2. Run `npx -y airtable-mcp-server` and add it to your Claude Desktop config with `AIRTABLE_API_KEY` set to your token. 3. Restart Claude Desktop and ask it to list tables in one of your bases to confirm the connection works. 4. Watch out for Airtable's rate limits (five requests per second per base). If you're doing bulk operations, Claude might hit the limit and you'll need to retry. 5. Remember that record updates require the record ID, not just a field value, so you'll often need to query first, then update.

Works with

Claude DesktopClaude CodeCursor