How to
How to connect Claude to Airtable with write access
Claude can already talk about your Airtable data, but copying its output back into a grid is still your job. A custom connector lets Claude create and update the records itself, with deletes waiting for your approval.
Connect Claude to Airtable through a custom MCP connector that authenticates with a scoped personal access token or OAuth, limited to the bases the work needs. Claude then queries records freely and uses write tools to create rows, update fields, and link records across tables, with deletes gated behind a confirmation you approve.
Key takeaways
- A custom connector gives Claude create and update tools for Airtable, so rows land in the base instead of in the chat.
- Claude can update field values across many records at once and populate linked-record fields between tables.
- Delete is a separate, gated action that only runs after you confirm it.
- Access is scoped to the bases you grant, and Claude never gets more than your own account has.
Does Claude have an Airtable integration already?
Partly. The Airtable connections available to Claude today tend to be read-leaning or cover a thin slice of the API, so Claude can often query records but cannot reliably create, update, or organize them across bases. Full read-write access to a base comes from a custom connector.
Read access answers questions: what is in this table, which records match this filter, what changed this week. But an Airtable base is something you maintain, and maintenance is writing. Creating records, fixing field values, connecting rows across tables, retagging after a schema change. A read-leaning connection leaves all of that as copy-paste from the chat back into the grid.
A custom Airtable connector adds those write actions with scoped, human-in-the-loop controls, so Claude maintains the base instead of only describing it.
The wider pattern holds beyond this one tool: in our June 2026 review of 264 business tools, 77 percent had no Claude connector at all, and none shipped full read-write out of the box.
How do I connect Claude to Airtable with write access?
You connect Claude to Airtable by having a custom MCP connector built against the Airtable API, authenticated with a scoped personal access token or OAuth limited to the bases and permissions the work needs. Once added to Claude, you describe changes in plain language and approve the destructive ones.
The setup runs like this:
- 1Tell us which bases and workflows Claude should handle: data entry, cleanup, cross-table linking, whatever your team defers.
- 2We build a small MCP server with read tools like
list_recordskept separate from write tools likecreate_recordandupdate_record. - 3You authenticate with a personal access token or OAuth scoped to just the bases you grant, so Claude inherits your permissions and nothing more.
- 4Claude starts working in your bases from your conversations, with
delete_recordgated behind your confirmation every time.
After that, the workflow inverts. Instead of asking Claude for text you paste into a grid, you describe the records and Claude puts them in the base, once you approve.
What can Claude do in an Airtable base with full read-write access?
With full read-write access, Claude can create records from details you describe, update field values across one or many rows, populate linked-record fields to connect tables, add or change select options and retag records, and find records matching a filter to propose batched edits. Deletes wait for your approval.
The write tools cover the base maintenance teams actually put off:
create_recordadds new rows to a table from a description, a list, or a document you paste in.update_recordchanges field values on one record or across many matching records at once.- Populating a linked-record field connects rows across tables, so relationships stay intact as data grows.
- Adding or changing a select option and retagging records keeps views and filters working after a schema tweak.
delete_recordremoves a stale row, but only after you confirm the change.
Setting field values correctly also means records land in the right views, since Airtable views are filters over the same data.
Will Claude delete Airtable records without asking?
No. Delete is a separate, gated write action. Claude can identify the stale records and prepare the change, but nothing is removed until you approve it. You decide which actions run automatically and which require a confirmation step, so destructive edits to a base never happen silently.
Most teams let creates and updates flow with review, and hold deletes behind an explicit confirmation. Since read tools, write tools, and destructive tools are separate, the gate sits exactly where you want it.
Batched edits are where this pays off
Ask Claude to find every record matching a filter and propose the edit across all of them. You review one proposed change set instead of touching fifty rows by hand.
Is it safe to give Claude access to my Airtable bases?
Yes, when access is scoped. The connector authenticates with a personal access token or OAuth limited to the bases you grant, and it inherits your existing permissions. Claude cannot reach a base you cannot, read and write tools are separate, and deletes require your confirmation every time.
The token boundary is the key control. Unlike a full-account integration, a scoped token means the connector physically cannot see bases outside the grant, no matter what is asked of it.