Skip to content
Custom Connectors

Connect Airtable to Claude Code

Let Claude create, update, and organize records in Airtable. From the terminal, inside the sessions where you already work.

How do you connect Airtable to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Airtable, you add a Airtable MCP server: a small hosted service that exposes Airtable's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Airtable account. No API keys pasted into config files.

claude mcp add --transport http airtable https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in Airtable once connected?

Full read-write Airtable access lets Claude create records, update fields, attach links, set field values so records land in the right view, and keep a base in sync with your real work. The data entry and cleanup that used to mean copy-paste from chat back into a grid happen directly where the records already live, once you approve.

  • Create new records in a table from details you describe
  • Update field values across one or many existing records
  • Find records matching a filter and propose batched edits
  • Populate a linked-record field to connect rows across tables
  • Add or change a select option, then retag records to it
  • Delete a stale record once you confirm the change

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Airtable access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the Airtable API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Airtable changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Airtable connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same Airtable connector work in claude.ai and Claude Code?
Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Airtable account, so access always matches what that person can already see and do.
Do I need to host or maintain anything myself?
No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Airtable's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.
Is it safe to give a coding agent write access to Airtable?
Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Airtable account it signs in with. Revoking access is one click in Airtable.

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.