What your AI apps can do with Airtable
- Search and update records
- Inspect bases and table schemas
Airtable MCP tools
32 tools, taken from the publisher's documentation on 29 October 2026. The server decides what it offers and can add or rename tools at any time; after you connect, Toolstile shows the current list.
| Tool | What it does |
|---|---|
list_workspaces | List workspaces you can access |
list_bases | List bases or find one by name |
search_bases | List bases or find one by name |
list_tables_for_base | Return schemas for every table in a base |
get_table_schema | Return a table's fields, IDs, types and options |
list_views_for_table | List a table's views |
list_records_for_table | List records with optional filtering and sorting |
search_records | Search a table's records by keyword |
search_candidate_linked_records | Find records that can go in a linked-record field |
list_records_for_page | Read records shown on an interface page (works with interface-only access) |
get_record_for_page | Read records shown on an interface page (works with interface-only access) |
create_records_for_table | Add records (up to 10 per request) |
update_records_for_table | Change specified fields on existing records |
delete_records_for_table | Delete records by ID |
revert_action | Undo an eligible earlier change by action ID |
create_table | Add a table or change its name and description |
update_table | Add a table or change its name and description |
delete_table | Delete a whole table, including records, fields and views |
create_field | Add a field or change its name, description or formula |
update_field | Add a field or change its name, description or formula |
create_base | Create a base in a workspace where you are a Creator |
create_interface | Build a new interface or page |
create_page | Build a new interface or page |
delete_interface | Delete an interface (with all pages) or a page |
delete_page | Delete an interface (with all pages) or a page |
get_form_schema | Read a form's fields and rules |
submit_form | Submit a form |
list_automations | Read automations and their configuration |
get_automation | Read automations and their configuration |
create_automation | Draft an automation (stays off until enabled in Airtable) |
update_automation | Overwrite an automation's draft configuration |
delete_automation | Delete an automation that is turned off |
Suggested access for each AI app
The documentation this list comes from doesn't mark Airtable's tools as read-only or destructive. Read each tool's description and decide per app before allowing it.
Coding agent in Claude Code or Cursor. Allow the read tools so the agent can look things up without stopping, and require approval for tools that change shared data.
Chat or research app in Claude Desktop. Allow reading and searching. Allow writes only where you want the app to act for you.
Unattended agent, such as a scheduled Codex job. No one is watching the session, so keep it narrow: allow what the job needs, require approval for changes and block the rest.
Blocked tools are removed from the tool list an app sees, so it won't try them. Because rules apply per app, the same Airtable connection can be broad in one app and read-only in another, and the credential stays in Toolstile instead of each app's config file.
How it works with Toolstile
- Connect once. Add Airtable to a workspace (browser sign-in). Toolstile keeps the credential, so no agent config holds it.
- Choose access per app. Give Claude Code every Airtable tool, give Cursor only the read tools, or keep Airtable away from an app entirely.
- Share approved accounts. Teammates use the connection without copying tokens, and you can remove access in one place.
- Review activity. See which app called which tool and when, so you can tighten access with evidence.
Add the Airtable MCP server to an AI app
Through Toolstile, every AI app uses one gateway entry, whichever servers you connect. In Claude Code:
claude mcp add --transport http toolstile 'https://mcp.toolstile.com/mcp'Then connect Airtable in your workspace and choose which of its tools that app may use. Client setup covers Codex, Cursor and Claude Desktop.
To connect directly instead, add the Airtable endpoint to each app separately. In Claude Code:
claude mcp add --transport http airtable 'https://mcp.airtable.com/mcp'In Cursor's mcp.json:
{
"mcpServers": {
"airtable": {
"url": "https://mcp.airtable.com/mcp"
}
}
}Some servers accept only clients they have approved, or need a token header. Check the Airtable MCP documentation for what your client needs.
Before you connect
An Airtable account. Sign-in uses your Airtable permissions.
Server details
| Detail | Value |
|---|---|
| Publisher | Airtable |
| Endpoint | https://mcp.airtable.com/mcp |
| Authentication | Browser sign-in |
| Categories | Productivity, Data & infrastructure |
| Tool list | 32 tools, observed 29 October 2026 (docs) |