Airtable MCP Server Setup for Cursor IDE (2026)

If your team tracks anything outside of Jira or Linear — content calendars, vendor lists, QA test matrices — there's a decent chance it lives in Airtable. The Airtable MCP server lets Cursor read and write records directly, which is mostly useful for one thing: generating code or content that needs to match structured data you already maintain, without you manually copying rows into the chat.

What You Can Do with Airtable MCP in Cursor

Once connected:

That schema-to-code prompt is the one worth trying first — it saves the tedious part of writing types by hand for a base whose columns change every few weeks.

Prerequisites

Step 1: Create an Airtable Personal Access Token

1. Go to airtable.com/create/tokens
2. Click Create new token
3. Name it something identifiable, like cursor-mcp
4. Under Scopes, add at minimum data.records:read — add data.records:write and schema.bases:read if you want Cursor to create/update records or inspect schema
5. Under Access, add the specific bases you want reachable (Airtable requires explicit per-base or per-workspace access — a token isn't account-wide by default)
6. Click Create token and copy it immediately

Scope this narrowly. A token with write access to every base in your workspace is a bigger blast radius than most people intend when they're just trying to query one table.

Step 2: Get Your Base ID

Open the base in Airtable, click Help → API documentation, and the base ID (starts with app) is shown at the top. Alternatively it's in the URL when you have the base open: airtable.com/appXXXXXXXXXXXXXX/...

Step 3: Add to Cursor's MCP Config

Open ~/.cursor/mcp.json:

{
  "mcpServers": {
    "airtable": {
      "command": "npx",
      "args": ["-y", "airtable-mcp-server"],
      "env": {
        "AIRTABLE_API_KEY": "your_personal_access_token_here"
      }
    }
  }
}

This community server auto-discovers whatever bases your token has access to — you don't need to hardcode base IDs into the config, just reference them (or the base name) in your prompts.

Step 4: Restart Cursor and Test

Fully quit and reopen Cursor, then try:

List the bases my Airtable token can access

Followed by something scoped to a real table:

Show me the field names and types in the "Tasks" table of my "Product Roadmap" base

If nothing comes back, check View → Output → MCP for connection errors before assuming your token is wrong — a surprising number of first-run failures are Node version issues, not auth issues.

Practical Workflows

Generating Types from a Live Schema

Look at the "Inventory" table schema and generate a matching Zod schema I can use to validate API input

Useful specifically because Airtable schemas drift — someone adds a field in the UI, nobody updates the code that reads it. Regenerating from the live schema catches that.

Bulk Status Checks

Find every record in "Vendor Contracts" where the renewal date is within 30 days and list them with the vendor name and contact email

Cross-Table Reconciliation

Compare record IDs between the "Support Tickets" table and "Customers" table and flag any tickets linked to a customer that no longer exists

Gotchas Worth Knowing

Airtable's API has real rate limits. Free and Team plans cap around 5 requests per second per base. Bulk operations (creating dozens of records in one prompt) can hit this — if you see intermittent failures on large batches, that's usually why, not a config problem.

Linked records don't resolve automatically in every query. If a field links to another table, asking "show me the linked customer's email" sometimes requires a follow-up query rather than resolving in one shot, depending on how the MCP server's tool call is structured. If a prompt returns record IDs instead of readable data, ask it to "resolve the linked record" explicitly.

Field names with spaces or special characters can cause the AI to misquote them in generated formulas or filters. If a filterByFormula-style query fails, check whether the field name needs to be wrapped differently — this is an Airtable formula syntax quirk, not something the MCP server controls.

Write access is genuinely write access. Unlike read-only lookups, "add a record" or "update this field" prompts actually mutate the base immediately — there's no draft/confirm step. Scope your token to read-only until you're confident in how the AI is interpreting write prompts.

Troubleshooting

"Invalid API key" errors
Confirm you're using a Personal Access Token (starts with pat), not an old-style API key — Airtable deprecated those and they won't authenticate.

"NOT_FOUND" or missing bases
The token's Access scope doesn't include that base. Go back to your token settings and add it explicitly — Airtable requires per-base grants, it's not automatic even for bases you own.

Server not appearing in Cursor
Run npx -y airtable-mcp-server manually in a terminal to see the raw error output — this surfaces Node version or dependency issues that Cursor's MCP panel sometimes swallows.

Records come back but fields are empty
Check the token's scopes include data.records:read at minimum. Some setups accidentally scope only schema.bases:read, which returns structure but not data.

Frequently Asked Questions

Q: Is the Airtable MCP server official, or is it a community project?
A: airtable-mcp-server is a community-maintained package, not something published by Airtable itself. It works against Airtable's public REST API, so it's stable, but don't expect Airtable support to help troubleshoot it.

Q: Can Cursor create new tables or only work with existing ones?
A: This server is built around records and schema reads — creating new tables from scratch is a base-structure change that's outside what most Airtable MCP implementations expose. Stick to records, fields, and views within tables that already exist.

Q: Will this work with Airtable's automation or scripting features?
A: No, those are separate systems. The MCP server talks to the standard records API — it doesn't trigger Airtable Automations or interact with the Scripting block.

Q: How is this different from just using Airtable's API directly?
A: Functionally similar under the hood, but the MCP server means you don't write API-calling code yourself — you describe what you want in the Cursor chat and the AI translates it into the right API calls.

Q: Can I connect multiple Airtable accounts or workspaces at once?
A: You can add multiple entries under mcpServers with different tokens and key names (e.g., airtable-personal, airtable-work) if you need to keep workspaces separate.

Related Guides

---