MCP server
Airtable
Read and change Airtable records only in a copied base with synthetic data and tightly scoped authorisation.
Published by the company that makes the product.
What it can access
Uses Airtable authentication and can be scoped to selected bases and actions. Write tools can modify records or structure.
Security note
Connect only a copied base with synthetic data. Grant the smallest set of scopes and resources, keep schema-changing tools off, and inspect the activity log.
Do you need it?
Connect only when repeated record updates justify an action-capable integration. For a one-off analysis, export a redacted CSV.
Capability and permissions
The official Airtable MCP tooling can read records and may update records or schema depending on the tools and scopes granted.
Least-privilege setup
As of 2026-09-01, use Airtable’s official repository and authentication instructions. Copy the base, replace real data with synthetic rows, authorise only that base, and omit schema-changing or destructive scopes.
Harmless success test
Ask the client to add reviewed: no to one invented record. Confirm no other row, field, view, or base changed.
Disable, revoke, remove
Disconnect the MCP, revoke its Airtable token or OAuth grant, remove the workshop collaborator, and delete the copied base. Rotate any exposed token.
When not to connect
Do not connect a contacts, grants, beneficiary, case, payroll, or donor base. Do not connect if nobody can inspect record and schema changes.