Airtable MCP

Vendor MCP43 toolsOAuth 2.1/DCRProject ManagementDatabasesProductivity

Connect to Airtable MCP. Manage bases, tables, records, views, fields, and automations from your AI workflows.

Airtable MCP connector

Install the SDK
Section titled “Install the SDK”
- Node.js
- Python
Terminal window
1 npm install @scalekit-sdk/node
Terminal window
1 pip install scalekit
Full SDK reference: Node.js | Python
Set your credentials
Section titled “Set your credentials”

Add your Scalekit credentials to your .env file. Find values in app.scalekit.com > Developers > API Credentials.
.env
```
SCALEKIT_ENVIRONMENT_URL=<your-environment-url>
SCALEKIT_CLIENT_ID=<your-client-id>
SCALEKIT_CLIENT_SECRET=<your-client-secret>
```

1
import { ScalekitClient } from '@scalekit-sdk/node'
2
import 'dotenv/config'
3

4
const scalekit = new ScalekitClient(
5
  process.env.SCALEKIT_ENV_URL,
6
  process.env.SCALEKIT_CLIENT_ID,
7
  process.env.SCALEKIT_CLIENT_SECRET,
8
)
9
const actions = scalekit.actions
10

11
const connector = 'airtablemcp'
12
const identifier = 'user_123'
13

14
// Generate an authorization link for the user
15
const { link } = await actions.getAuthorizationLink({ connectionName: connector, identifier })
16
console.log('Authorize Airtable MCP:', link)
17
process.stdout.write('Press Enter after authorizing...')
18
await new Promise(r => process.stdin.once('data', r))
19

20
// Make your first call
21
const result = await actions.executeTool({
22
  connector,
23
  identifier,
24
  toolName: 'airtablemcp_get_create_automation_instructions',
25
  toolInput: {},
26
})
27
console.log(result)

1
import os
2
from scalekit.client import ScalekitClient
3
from dotenv import load_dotenv
4
load_dotenv()
5

6
scalekit_client = ScalekitClient(
7
    env_url=os.getenv("SCALEKIT_ENV_URL"),
8
    client_id=os.getenv("SCALEKIT_CLIENT_ID"),
9
    client_secret=os.getenv("SCALEKIT_CLIENT_SECRET"),
10
)
11
actions = scalekit_client.actions
12

13
connection_name = "airtablemcp"
14
identifier = "user_123"
15

16
# Generate an authorization link for the user
17
link_response = actions.get_authorization_link(
18
    connection_name=connection_name,
19
    identifier=identifier,
20
)
21
print("Authorize Airtable MCP:", link_response.link)
22
input("Press Enter after authorizing...")
23

24
# Make your first call
25
result = actions.execute_tool(
26
    tool_input={},
27
    tool_name="airtablemcp_get_create_automation_instructions",
28
    connection_name=connection_name,
29
    identifier=identifier,
30
)
31
print(result)

What you can do

Connect this agent connector to let your agent:

Update automation, table, records for table — Replaces the entire draft configuration (trigger, graph, name, description) of an existing automation
Trigger test automation webhook — Re-runs the trigger test for a genericWebhookReceived automation and waits briefly for a newly captured payload schema
Form submit — Submits a form, creating a new record in the form’s source table
Search candidate linked records, records, bases — Searches for records that are valid candidates for a linked-record (foreign-key) field, returning each candidate’s record ID along with the fields the linked-record field is configured to display (the same fields shown on the in-product card)
Action revert — Reverts a previous eligible Airtable mutation by performing the inverse write, using the actionId it returned
List views for table, external accounts, automations — Lists the views in a table, returning each view’s ID, name, and type

Tool list

Use the exact tool names from the Tool list below when you call execute_tool. If you’re not sure which name to use, list the tools available for the current user first.

airtablemcp_create_automation#Creates and validates one automation in a base: a trigger plus ordered nodes — action nodes, `repeatingGroup` (run inner nodes once per item), and `conditionalGroup` (if/else-if/else branches). Many trigger and action types are supported; get_create_automation_instructions has the full catalog. Saves the draft configuration only — it is off until the user reviews and turns it on in the Airtable UI. Prefer get_create_automation_instructions once per session for the full catalog. Before building IDs, call list_tables_for_base(baseId). Call get_table_schema(baseId, tables) before filtering on select / multiSelect fields. Every trigger and node input is an expression (literal, $ref, template, fn, or a plain object/array) — not raw JSON. Field shapes, typed {obj}/{tuple} wrappers, write modes, and an error index are in get_create_automation_instructions. Flow: 1. create_automation(baseId, name, trigger, nodes). If isValid is false, nothing was saved: use errors to fix the inputs and call again. After a couple of failed attempts, report the errors to the user instead of looping. 2. On success only the draft configuration is saved; the automation is off. Tell the user to open the automationUrl in the Airtable UI to review and turn it on. {"trigger":{"type":"recordCreated","inputs":{"tableId":"tbl..."}},"nodes":[{"key":"node1","type":"updateRecord","inputs":{"tableId":"tbl...","rowId":{"template":[{"$ref":"trigger","path":["id"]}]},"updateRecordMethod":"customFields","fields":{"fldStatus":{"template":["In Progress"]}}}}]}5 params

Creates and validates one automation in a base: a trigger plus ordered nodes — action nodes, `repeatingGroup` (run inner nodes once per item), and `conditionalGroup` (if/else-if/else branches). Many trigger and action types are supported; get_create_automation_instructions has the full catalog. Saves the draft configuration only — it is off until the user reviews and turns it on in the Airtable UI. Prefer get_create_automation_instructions once per session for the full catalog. Before building IDs, call list_tables_for_base(baseId). Call get_table_schema(baseId, tables) before filtering on select / multiSelect fields. Every trigger and node input is an expression (literal, $ref, template, fn, or a plain object/array) — not raw JSON. Field shapes, typed {obj}/{tuple} wrappers, write modes, and an error index are in get_create_automation_instructions. Flow: 1. create_automation(baseId, name, trigger, nodes). If isValid is false, nothing was saved: use errors to fix the inputs and call again. After a couple of failed attempts, report the errors to the user instead of looping. 2. On success only the draft configuration is saved; the automation is off. Tell the user to open the automationUrl in the Airtable UI to review and turn it on. {"trigger":{"type":"recordCreated","inputs":{"tableId":"tbl..."}},"nodes":[{"key":"node1","type":"updateRecord","inputs":{"tableId":"tbl...","rowId":{"template":[{"$ref":"trigger","path":["id"]}]},"updateRecordMethod":"customFields","fields":{"fldStatus":{"template":["In Progress"]}}}}]}

NameTypeRequiredDescription

baseIdstringrequiredThe ID of the base to create the automation in. Must start with "app" and is 17 characters long. Example: "appZfrNIUEip5MazD". Do not substitute user-facing names for baseId. To get baseId, use the search_bases or list_bases tool.

namestringrequiredName for the automation.

nodesarrayrequiredOrdered array of nodes (actions, repeatingGroup, or conditionalGroup). Groups (conditionalGroup/repeatingGroup) may be nested at most 2 levels deep. See create_automation description for semantics and the expression language.

triggerobjectrequiredTrigger configuration.

descriptionstringoptionalOptional description for the automation.

airtablemcp_create_base#Creates a new Airtable base with specified tables and fields in a workspace. Use list_workspaces to get the workspaceId first. The first field in each table's fields array becomes the primary field.3 params

Creates a new Airtable base with specified tables and fields in a workspace. Use list_workspaces to get the workspaceId first. The first field in each table's fields array becomes the primary field.

NameTypeRequiredDescription

namestringrequiredThe name for the new base.

workspaceIdstringrequiredThe ID of the workspace to create the base in. Must start with "wsp" and is 17 characters long. Do not substitute user-facing names for workspaceId. To get workspaceId, use the list_workspaces tool.

tablesarrayoptionalOptional. The tables to create in the new base. If omitted, a default table ("Table 1") with a "Name" singleLineText field is created.

airtablemcp_create_field#Creates a new field in an existing Airtable table. Use search_bases and list_tables_for_base to get baseId and tableId first. Supports all field types including singleSelect, number, formula, date, and more.3 params

Creates a new field in an existing Airtable table. Use search_bases and list_tables_for_base to get baseId and tableId first. Supports all field types including singleSelect, number, formula, date, and more.

NameTypeRequiredDescription

baseIdstringrequiredThe ID of the base containing the table. Must start with "app" and is 17 characters long. Do not substitute user-facing names for baseId. To get baseId, use the search_bases or list_bases tool.

fieldobjectrequiredThe field definition to create. Must include at minimum 'name' and 'type'. Some field types require an 'options' object (e.g., singleSelect, number, currency, formula). Types without options: singleLineText, email, url, multilineText, phoneNumber, richText, barcode, multipleAttachments, singleCollaborator, multipleCollaborators.

tableIdstringrequiredThe ID of the table to create the field in. Must start with "tbl" and is 17 characters long. Do not substitute user-facing names for tableId. To get tableId, use the list_tables_for_base tool.

airtablemcp_create_interface#Creates a new interface within an Airtable base. After creation, use create_page to add pages and publish_interface to make the interface live for end users.2 params

Creates a new interface within an Airtable base. After creation, use create_page to add pages and publish_interface to make the interface live for end users.

NameTypeRequiredDescription

baseIdstringrequiredThe ID of the base in which to create the interface. Must start with "app" and is 17 characters long.

namestringrequiredThe display name for the new interface.

airtablemcp_create_page#Creates a new page within an existing Airtable interface. Supported page types are visualization, dashboard, and customElement. Use describe_page_type and describe_page_element to discover the correct pageConfiguration shape.5 params

Creates a new page within an existing Airtable interface. Supported page types are visualization, dashboard, and customElement. Use describe_page_type and describe_page_element to discover the correct pageConfiguration shape.

NameTypeRequiredDescription

baseIdstringrequiredThe ID of the base in which to create the page. Must start with "app" and is 17 characters long.

interfaceIdstringrequiredThe ID of the interface in which to create the page. Must start with "pbd" and is 17 characters long.

namestringrequiredThe display name for the new page.

pageConfigurationobjectrequiredPage type-specific configuration. Schema is provided by describe_page_type and describe_page_element.

pageTypestringrequiredThe type of page to create.

airtablemcp_create_record_comment#Creates a comment on a specific Airtable record. Supports user and group mentions using @[userId] or @[userGroupId] tokens in the comment text, and supports threaded replies via the optional parentCommentId parameter.5 params

Creates a comment on a specific Airtable record. Supports user and group mentions using @[userId] or @[userGroupId] tokens in the comment text, and supports threaded replies via the optional parentCommentId parameter.

NameTypeRequiredDescription

baseIdstringrequiredThe ID of the base.

recordIdstringrequiredThe ID of the record to comment on.

tableIdstringrequiredThe ID of the table.

textstringrequiredThe text of the comment to create.

parentCommentIdstringoptionalThe ID of the parent comment to reply to, for creating a threaded reply.

airtablemcp_create_records_for_table#Creates new records in an Airtable table. Use search_bases and list_tables_for_base to get baseId and tableId before calling this tool. You can create up to 50 records per request.5 params

Creates new records in an Airtable table. Use search_bases and list_tables_for_base to get baseId and tableId before calling this tool. You can create up to 50 records per request.

NameTypeRequiredDescription

recordsarrayrequiredAn array of record objects to create. Each record must have a "fields" property containing the field values.

tableIdstringrequiredThe ID of the table to create records in. Must start with "tbl" and is 17 characters long. Do not substitute user-facing names for tableId. To get tableId, use the list_tables_for_base tool.

fieldIdsarrayoptionalThe IDs of the fields to include in each returned record. If omitted, only the fields you wrote are returned. Pass explicit IDs to include fields you did not write (e.g. the primary field or formula/rollup results).

typecastbooleanoptionalWhether or not to perform best-effort automatic data conversion from string values. Defaults to false to preserve data integrity.

airtablemcp_create_table#Creates a new table in an existing Airtable base. Use search_bases or list_bases to get the baseId first. The first field in the fields array becomes the primary field of the table.4 params

Creates a new table in an existing Airtable base. Use search_bases or list_bases to get the baseId first. The first field in the fields array becomes the primary field of the table.

NameTypeRequiredDescription

baseIdstringrequiredThe ID of the base to create the table in. Must start with "app" and is 17 characters long. Do not substitute user-facing names for baseId. To get baseId, use the search_bases or list_bases tool.

fieldsarrayrequiredThe first field becomes the primary field and must be one of these types: singleLineText, email, url, multilineText, number, percent, currency, duration, date, dateTime, phoneNumber, barcode. Remaining fields can be any type.

namestringrequiredMust be unique within the base (case-insensitive).

descriptionstringoptionalNo description.

airtablemcp_delete_automation#Deletes an existing automation from a base. The automation must be off before it can be deleted. The target automation must be off. If it is on, the user must turn it off in the Airtable UI before it can be deleted.2 params

Deletes an existing automation from a base. The automation must be off before it can be deleted. The target automation must be off. If it is on, the user must turn it off in the Airtable UI before it can be deleted.

NameTypeRequiredDescription

automationIdstringrequiredThe ID of the automation to delete. Must start with "wfl" and is 17 characters long. Example: "wflGlRtkBNWfYnPOV". To get an automationId, use the create_automation tool.

baseIdstringrequiredThe ID of the base containing the automation. Must start with "app" and is 17 characters long. Example: "appZfrNIUEip5MazD". Do not substitute user-facing names for baseId. To get baseId, use the search_bases or list_bases tool.

airtablemcp_delete_interface#Deletes an interface from a base, including all of its pages. The published version, if any, immediately stops being available to end users. The agent MUST ask the user for explicit confirmation before calling this tool. Interface deletion is destructive and should not be performed without the user's go-ahead. Use list_pages_for_base to find the appropriate interfaceId. To delete a single page within an interface instead, use delete_page. On success of delete_interface, the response includes an actionId that can be passed to revert_action to undo the deletion, restoring the interface with its pages.2 params

Deletes an interface from a base, including all of its pages. The published version, if any, immediately stops being available to end users. The agent MUST ask the user for explicit confirmation before calling this tool. Interface deletion is destructive and should not be performed without the user's go-ahead. Use list_pages_for_base to find the appropriate interfaceId. To delete a single page within an interface instead, use delete_page. On success of delete_interface, the response includes an actionId that can be passed to revert_action to undo the deletion, restoring the interface with its pages.

NameTypeRequiredDescription

baseIdstringrequiredThe ID of the base containing the interface to delete. Must start with "app" and is 17 characters long. Example: "appZfrNIUEip5MazD". Do not substitute user-facing names for baseId. To get baseId, use the search_bases or list_bases tool.

interfaceIdstringrequiredThe ID of the interface to delete. Must start with "pbd" and is 17 characters long.

airtablemcp_delete_page#Deletes an existing page from an interface. This action is destructive and requires explicit user confirmation before calling. Use publish_interface after deletion to propagate the change to the live interface.2 params

Deletes an existing page from an interface. This action is destructive and requires explicit user confirmation before calling. Use publish_interface after deletion to propagate the change to the live interface.

NameTypeRequiredDescription

baseIdstringrequiredThe ID of the base containing the page to delete. Must start with "app" and is 17 characters long.

pageIdstringrequiredThe ID of the page to delete. Must start with "pag" and is 17 characters long.

airtablemcp_delete_records_for_table#Permanently deletes records from an Airtable table by record IDs. Use list_records_for_table to get record IDs first. You can delete up to 50 records per request. This action is irreversible.3 params

Permanently deletes records from an Airtable table by record IDs. Use list_records_for_table to get record IDs first. You can delete up to 50 records per request. This action is irreversible.

NameTypeRequiredDescription

recordIdsarrayrequiredAn array of record IDs to delete. Must start with "rec" and is 17 characters long. To get record IDs, use the list_records_for_table or search_records tools.

tableIdstringrequiredThe ID of the table to delete records from. Must start with "tbl" and is 17 characters long. Do not substitute user-facing names for tableId. To get tableId, use the list_tables_for_base tool.

airtablemcp_delete_table#Deletes an entire table from a base, including all of its records, fields, and views. The agent MUST ask the user for explicit confirmation before calling this tool. Table deletion is destructive and should not be performed without the user's go-ahead. Use list_tables_for_base to find the appropriate tableId. A base must always have at least one table, so the last remaining table in a base cannot be deleted; attempting to do so returns an error. On success, the response includes an actionId that can be passed to revert_action to undo the deletion, restoring the table with its records, fields, and views. Reverting is best-effort: it may fail if the base's schema changed after the deletion (for example, another table took the deleted table's former position), so treat the deletion as permanent unless a revert succeeds. Example: delete the table tblABCDEFGHIJKLMN in base appZfrNIUEip5MazD: {"baseId": "appZfrNIUEip5MazD", "tableId": "tblABCDEFGHIJKLMN"}2 params

Deletes an entire table from a base, including all of its records, fields, and views. The agent MUST ask the user for explicit confirmation before calling this tool. Table deletion is destructive and should not be performed without the user's go-ahead. Use list_tables_for_base to find the appropriate tableId. A base must always have at least one table, so the last remaining table in a base cannot be deleted; attempting to do so returns an error. On success, the response includes an actionId that can be passed to revert_action to undo the deletion, restoring the table with its records, fields, and views. Reverting is best-effort: it may fail if the base's schema changed after the deletion (for example, another table took the deleted table's former position), so treat the deletion as permanent unless a revert succeeds. Example: delete the table tblABCDEFGHIJKLMN in base appZfrNIUEip5MazD: {"baseId": "appZfrNIUEip5MazD", "tableId": "tblABCDEFGHIJKLMN"}

NameTypeRequiredDescription

baseIdstringrequiredThe ID of the base containing the table to delete. Must start with "app" and is 17 characters long. Example: "appZfrNIUEip5MazD". Do not substitute user-facing names for baseId. To get baseId, use the search_bases or list_bases tool.

tableIdstringrequiredThe ID of the table to delete. Must start with "tbl" and is 17 characters long. Example: "tblGlReoTNWfYnXIG". Do not substitute user-facing names for tableId. To get tableId, use the list_tables_for_base tool.

airtablemcp_describe_page_element#Returns the JSON schema for a page element of the specified type. Use this before create_page to discover the element config shape required within pageConfiguration.1 param

Returns the JSON schema for a page element of the specified type. Use this before create_page to discover the element config shape required within pageConfiguration.

NameTypeRequiredDescription

elementTypestringrequiredThe page element type to get the config schema for.

airtablemcp_describe_page_type#Returns the JSON schema for a page type's configuration. Use this before create_page to discover the required pageConfiguration shape for the chosen page type.1 param

Returns the JSON schema for a page type's configuration. Use this before create_page to discover the required pageConfiguration shape for the chosen page type.

NameTypeRequiredDescription

pageTypestringrequiredThe page type to get the config schema for.

airtablemcp_fetch_automation_input_data#Fetches dynamic input options for an automation action or trigger's input field (e.g. Slack channels, Jira projects, calendars). Requires an `externalAccountId` from list_external_accounts. Use get_create_automation_instructions to discover which `inputKey` values each action or trigger type expects.7 params

Fetches dynamic input options for an automation action or trigger's input field (e.g. Slack channels, Jira projects, calendars). Requires an `externalAccountId` from list_external_accounts. Use get_create_automation_instructions to discover which `inputKey` values each action or trigger type expects.

NameTypeRequiredDescription

externalAccountIdstringrequiredMust start with "eac" and is 17 characters long. Example: "eacZfrNIUEip5MazD". To get externalAccountId, use the list_external_accounts tool.

inputKeystringrequiredThe input field to fetch options for (e.g., "slackConversationId", "msTeamsTeamId").

workflowNodeTypeIdstringrequiredThe action or trigger type ID. Use the camelCase type value (e.g., "sendToSlack", "atlassianJiraCreateIssue", "googleCalendarEventCreated").

dependentInputobjectoptionalValues of prerequisite inputs this field depends on. For example, to fetch MS Teams channels, pass {"msTeamsTeamId": "<team-id>"}.

pagingCountnumberoptionalNumber of results to return. Default 10.

pagingStartIndexnumberoptionalStart index for pagination. Default 0.

searchQuerystringoptionalFilter results by name.

airtablemcp_get_automation#Gets the full configuration of a single automation in an Airtable base, including trigger configuration, action nodes with their input expressions, and deployment status. The returned configuration is the draft (the working copy the user edits). Set includeDeployedVersion to true to also see the most recently published configuration when it differs from the draft — useful for debugging deployed behavior. Edits always apply to the draft. Requires an automationId, which can be obtained from list_automations. {"baseId": "appZfrNIUEip5MazD", "automationId": "wflGlRtkBNWfYnPOV"}3 params

Gets the full configuration of a single automation in an Airtable base, including trigger configuration, action nodes with their input expressions, and deployment status. The returned configuration is the draft (the working copy the user edits). Set includeDeployedVersion to true to also see the most recently published configuration when it differs from the draft — useful for debugging deployed behavior. Edits always apply to the draft. Requires an automationId, which can be obtained from list_automations. {"baseId": "appZfrNIUEip5MazD", "automationId": "wflGlRtkBNWfYnPOV"}

NameTypeRequiredDescription

automationIdstringrequiredThe ID of the automation to retrieve. Must start with "wfl" and is 17 characters long. Example: "wflGlRtkBNWfYnPOV". To get an automationId, use the create_automation tool.

includeDeployedVersionbooleanoptionalWhen true, each returned automation includes a `deployedVersion` field showing the most recently published configuration when it differs from the draft.

airtablemcp_get_create_automation_instructions#Returns the full spec for create_automation — expression language, wrappers, function catalog, trigger and action input catalogs, pitfalls, and a complete example. Call once per session before building an automation payload.1 param

Returns the full spec for create_automation — expression language, wrappers, function catalog, trigger and action input catalogs, pitfalls, and a complete example. Call once per session before building an automation payload.

NameTypeRequiredDescription

baseIdstringoptionalThe ID of the base you plan to create automations in. Providing this includes features that may be available for this base but not globally. If omitted, only globally available features are returned.

airtablemcp_get_form_schema#Returns the schema of a form page — its structure, not the submitted-record data. Returns the form's source table, submission action (create or update), and a hierarchical breakdown of sections, rows, and field elements. Sections are the visual groups inside the form (each with an optional title), rows are the columns-of-fields layout within a section, and elements describe each individual field — its label, helper text, field type, required/read-only status, any prefilled value, and any conditional visibility filter. Single-select and multi-select field elements also list their valid choices. Use this when the user asks how a form is organized, what fields it collects, or which fields are required. visibilityFilters specifies the conditions under which a field or section is shown, not a resolved shown/hidden state. Required fields are required only when visible. Fields inside hidden sections are not visible. Do not call this on non-form pages. Supports entry-level form pages (in an interface or standalone) and record-creation row forms, forms embedded in other interface page types. Do not assume baseId. Obtain it from search_bases or list_bases. Use list_pages_for_base to find the pageId if needed. Record-creation row forms appear in that tool's embeddedForms array; pass any one of the form's interfaceIds as the interfaceId here. {"baseId": "appZfrNIUEip5MazD", "pageId": "pagXxYyZzAaBbCcDd"}3 params

Returns the schema of a form page — its structure, not the submitted-record data. Returns the form's source table, submission action (create or update), and a hierarchical breakdown of sections, rows, and field elements. Sections are the visual groups inside the form (each with an optional title), rows are the columns-of-fields layout within a section, and elements describe each individual field — its label, helper text, field type, required/read-only status, any prefilled value, and any conditional visibility filter. Single-select and multi-select field elements also list their valid choices. Use this when the user asks how a form is organized, what fields it collects, or which fields are required. visibilityFilters specifies the conditions under which a field or section is shown, not a resolved shown/hidden state. Required fields are required only when visible. Fields inside hidden sections are not visible. Do not call this on non-form pages. Supports entry-level form pages (in an interface or standalone) and record-creation row forms, forms embedded in other interface page types. Do not assume baseId. Obtain it from search_bases or list_bases. Use list_pages_for_base to find the pageId if needed. Record-creation row forms appear in that tool's embeddedForms array; pass any one of the form's interfaceIds as the interfaceId here. {"baseId": "appZfrNIUEip5MazD", "pageId": "pagXxYyZzAaBbCcDd"}

NameTypeRequiredDescription

baseIdstringrequiredThe ID of the base containing the form page. Must start with "app" and is 17 characters long. Example: "appZfrNIUEip5MazD". Do not substitute user-facing names for baseId. To get baseId, use the search_bases or list_bases tool.

pageIdstringrequiredThe ID of the form page whose schema you want to read. Must start with "pag" and is 17 characters long. Example: "pagXxYyZzAaBbCcDd".

interfaceIdstringoptionalThe ID of the interface containing the form page, if the form is in an interface. Must start with "pbd" and is 17 characters long.

airtablemcp_get_record_for_page#Gets a single record's details from an interface page element using a navigation path. Supports traversing linked record relationships by appending edges to the path.4 params

Gets a single record's details from an interface page element using a navigation path. Supports traversing linked record relationships by appending edges to the path.

NameTypeRequiredDescription

baseIdstringrequiredThe ID of the base containing the page. Must start with "app" and is 17 characters long.

interfaceIdstringrequiredThe ID of the interface that contains the page. Must start with "pbd" and is 17 characters long.

pathobjectrequiredThe navigation path from the page where the record was listed.

fieldIdsarrayoptionalOnly data for fields whose IDs are in this list will be included in the result.

airtablemcp_get_table_schema#Gets detailed schema information for specified tables and fields in an Airtable base, returning the field ID, type, and configuration for each specified field. Use this before filtering on singleSelect or multipleSelects fields to retrieve choice IDs.2 params

Gets detailed schema information for specified tables and fields in an Airtable base, returning the field ID, type, and configuration for each specified field. Use this before filtering on singleSelect or multipleSelects fields to retrieve choice IDs.

NameTypeRequiredDescription

baseIdstringrequiredThe ID of the base containing the tables.

tablesarrayrequiredAn array of table IDs and corresponding field IDs to get schema information for.

airtablemcp_list_automations#Lists automations in an Airtable base. Returns metadata about each automation including its ID, name, deployment status, trigger info, and graph nodes. Use this when the user asks about automations configured in a base. Optionally filter by trigger type (e.g., 'agentTriggerReceived'). The returned configuration is the draft (the working copy the user edits). Set includeDeployedVersion to true to also see each automation's most recently published configuration when it differs from the draft — useful for debugging deployed behavior. Edits always apply to the draft. Do not assume baseId. Obtain it from search_bases or list_bases. {"baseId": "appZfrNIUEip5MazD"}3 params

Lists automations in an Airtable base. Returns metadata about each automation including its ID, name, deployment status, trigger info, and graph nodes. Use this when the user asks about automations configured in a base. Optionally filter by trigger type (e.g., 'agentTriggerReceived'). The returned configuration is the draft (the working copy the user edits). Set includeDeployedVersion to true to also see each automation's most recently published configuration when it differs from the draft — useful for debugging deployed behavior. Edits always apply to the draft. Do not assume baseId. Obtain it from search_bases or list_bases. {"baseId": "appZfrNIUEip5MazD"}

NameTypeRequiredDescription

baseIdstringrequiredThe ID of the base to list automations from. Must start with "app" and is 17 characters long. Example: "appZfrNIUEip5MazD". Do not substitute user-facing names for baseId. To get baseId, use the search_bases or list_bases tool.

includeDeployedVersionbooleanoptionalWhen true, each returned automation includes a `deployedVersion` field showing the most recently published configuration when it differs from the draft.

triggerTypestringoptionalOptional trigger type to filter automations by (e.g., "agentTriggerReceived").

airtablemcp_list_bases#Lists all Airtable bases that you have access to in your account, including favorited and recently viewed bases. If the response includes an offset, pass it in a subsequent call to retrieve the next page of results.1 param

Lists all Airtable bases that you have access to in your account, including favorited and recently viewed bases. If the response includes an offset, pass it in a subsequent call to retrieve the next page of results.

NameTypeRequiredDescription

offsetstringoptionalPagination cursor from a previous list_bases response.

airtablemcp_list_external_accounts#Lists the external accounts (integrations) accessible to the current user, including accounts they own and accounts shared with them. Each account includes its type (e.g. Google Sheets, Slack, Salesforce), a human-readable label, and an account configuration ID that can be used to reference the account in other tool calls. Only user-managed integration accounts are returned.0 params

Lists the external accounts (integrations) accessible to the current user, including accounts they own and accounts shared with them. Each account includes its type (e.g. Google Sheets, Slack, Salesforce), a human-readable label, and an account configuration ID that can be used to reference the account in other tool calls. Only user-managed integration accounts are returned.

airtablemcp_list_pages_for_base#Lists all interfaces and their pages for a base, returning page IDs, names, and page-type-specific metadata. Use this to discover interfaces, dashboards, overview pages, and forms available in a base.1 param

Lists all interfaces and their pages for a base, returning page IDs, names, and page-type-specific metadata. Use this to discover interfaces, dashboards, overview pages, and forms available in a base.

NameTypeRequiredDescription

baseIdstringrequiredThe ID of the base to list pages from. Must start with "app" and is 17 characters long.

airtablemcp_list_record_comments#Lists comments on a specific Airtable record, ordered from newest to oldest, with support for pagination. Comments may contain user mentions in @[userId] or @[userGroupId] format, and the mentioned field maps these IDs to display names and emails.5 params

Lists comments on a specific Airtable record, ordered from newest to oldest, with support for pagination. Comments may contain user mentions in @[userId] or @[userGroupId] format, and the mentioned field maps these IDs to display names and emails.

NameTypeRequiredDescription

baseIdstringrequiredThe ID of the base.

recordIdstringrequiredThe ID of the record.

tableIdstringrequiredThe ID of the table.

offsetstringoptionalPass the offset from a previous response to fetch the next page.

pageSizeintegeroptionalThe number of comments to return per page.

airtablemcp_list_records_for_page#Lists records from an Airtable interface page. Use this for bases with interface-only access (permissionLevel "none") or when querying interface/page data. Obtain pageId and interfaceId from list_pages_for_base.7 params

Lists records from an Airtable interface page. Use this for bases with interface-only access (permissionLevel "none") or when querying interface/page data. Obtain pageId and interfaceId from list_pages_for_base.

NameTypeRequiredDescription

baseIdstringrequiredThe ID of the base containing the page. Must start with "app" and is 17 characters long. Do not substitute user-facing names for baseId. To get baseId, use the search_bases or list_bases tool.

interfaceIdstringrequiredThe ID of the interface that contains the page. Must start with "pbd" and is 17 characters long.

pageIdstringrequiredThe ID of the interface page to read records from. Must start with "pag" and is 17 characters long.

elementIdstringoptionalThe ID of a specific element to query records for. Required for dashboard pages. Obtain element IDs from the dashboardElements array in the list_pages_for_base response. Must start with "pel" and is 17 characters long.

fieldIdsarrayoptionalOnly data for fields whose IDs are in this list will be included in the result. If not provided, fields visible in the page element's visualization will be returned.

filtersobjectoptionalAdditional filters to apply on top of the page element's built-in filters. These are combined with the element's static filters using AND.

pageSizeintegeroptionalThe maximum number of records to return in the response.

airtablemcp_list_records_for_table#Lists records queried from an Airtable table, with support for field selection, pagination, sorting, record ID filtering, and structured filters. Obtain baseId and tableId from search_bases and list_tables_for_base before calling this tool.8 params

Lists records queried from an Airtable table, with support for field selection, pagination, sorting, record ID filtering, and structured filters. Obtain baseId and tableId from search_bases and list_tables_for_base before calling this tool.

NameTypeRequiredDescription

baseIdstringrequiredThe ID of the base containing the table.

tableIdstringrequiredThe table to list records from (table ID or table name).

cursorstringoptionalThe cursor to start from for paginated requests.

fieldIdsarrayoptionalOnly data for fields whose IDs or names are in this list will be included in the result.

filtersobjectoptionalStructured filters to apply to the records.

pageSizeintegeroptionalThe maximum number of records to return in the response.

recordIdsarrayoptionalAn array of record IDs to filter by.

sortarrayoptionalA list of sort objects specifying how records will be ordered.

airtablemcp_list_tables_for_base#Gets the summary of a specific Airtable base, including the schemas of all its tables with field names and types. If the base is not found or returns a permission error, the user may have interface-only access.1 param

Gets the summary of a specific Airtable base, including the schemas of all its tables with field names and types. If the base is not found or returns a permission error, the user may have interface-only access.

NameTypeRequiredDescription

baseIdstringrequiredThe ID of the base to get the summary of.

airtablemcp_list_views_for_table#Lists the views in a table, returning each view's ID, name, and type. Use this to discover viewId values needed by other tools, such as an automation trigger that fires on records entering a view. Do not assume baseId. Obtain it from search_bases or list_bases. {"baseId": "appZfrNIUEip5MazD", "tableId": "Orders"}2 params

Lists the views in a table, returning each view's ID, name, and type. Use this to discover viewId values needed by other tools, such as an automation trigger that fires on records entering a view. Do not assume baseId. Obtain it from search_bases or list_bases. {"baseId": "appZfrNIUEip5MazD", "tableId": "Orders"}

NameTypeRequiredDescription

baseIdstringrequiredThe ID of the base that contains the table. Must start with "app" and is 17 characters long. Example: "appZfrNIUEip5MazD". Do not substitute user-facing names for baseId. To get baseId, use the search_bases or list_bases tool.

tableIdstringrequiredThe table to list views from. Accepts either a table ID (e.g., "tblGlReoTNWfYnXIG") or a table name (e.g., "Orders"). Names are resolved case-insensitively within the base. To discover tables, use the list_tables_for_base tool.

airtablemcp_list_workspaces#Lists all Airtable workspaces the current user has access to, along with their permission level in each. This is typically the first tool to call when you need a workspaceId.1 param

Lists all Airtable workspaces the current user has access to, along with their permission level in each. This is typically the first tool to call when you need a workspaceId.

NameTypeRequiredDescription

offsetstringoptionalPagination offset from the previous response.

airtablemcp_ping#Pings the Airtable MCP server to check if it is running and reachable. Use this to verify connectivity before performing other operations.0 params

Pings the Airtable MCP server to check if it is running and reachable. Use this to verify connectivity before performing other operations.

airtablemcp_publish_interface#Publishes an interface, promoting each page's working draft to the live version that end users see. Publishing is idempotent — re-publishing with no new changes is a no-op. Pages with publishing state "disabled" are skipped.2 params

Publishes an interface, promoting each page's working draft to the live version that end users see. Publishing is idempotent — re-publishing with no new changes is a no-op. Pages with publishing state "disabled" are skipped.

NameTypeRequiredDescription

baseIdstringrequiredThe ID of the base containing the interface. Must start with "app" and is 17 characters long.

interfaceIdstringrequiredThe ID of the interface to publish. Must start with "pbd" and is 17 characters long.

airtablemcp_revert_action#Reverts a previous eligible Airtable mutation by performing the inverse write, using the actionId it returned. Record updates are not revertible. Use the actionId returned by an eligible mutating tool result. A tool result is eligible only if it explicitly returns an actionId. Examples include create_records_for_table or delete_records_for_table. Reverts one actionId per call (a multi-action revert is not atomic). To revert several, call once per actionId in reverse completion order, stopping on the first error. Example: revert an eligible mutation: {"baseId": "appZfrNIUEip5MazD", "actionId": "actZOTa3BDHxlJNzf"}2 params

Reverts a previous eligible Airtable mutation by performing the inverse write, using the actionId it returned. Record updates are not revertible. Use the actionId returned by an eligible mutating tool result. A tool result is eligible only if it explicitly returns an actionId. Examples include create_records_for_table or delete_records_for_table. Reverts one actionId per call (a multi-action revert is not atomic). To revert several, call once per actionId in reverse completion order, stopping on the first error. Example: revert an eligible mutation: {"baseId": "appZfrNIUEip5MazD", "actionId": "actZOTa3BDHxlJNzf"}

NameTypeRequiredDescription

actionIdstringrequiredThe ID of the action to revert, from a prior eligible tool result in this session. Must start with "act" and is 17 characters long. Example: "actZOTa3BDHxlJNzf".

baseIdstringrequiredThe ID of the base the action ran in — the same baseId you used for the mutation that returned this actionId. Must start with "app" and is 17 characters long. Example: "appZfrNIUEip5MazD". Do not substitute user-facing names for baseId. To get baseId, use the search_bases or list_bases tool.

airtablemcp_search_bases#Searches for Airtable bases by name using a partial, case-insensitive match. Returns bases sorted by relevance score, along with a recommended base ID and a hint on whether the user needs to explicitly select a base.1 param

Searches for Airtable bases by name using a partial, case-insensitive match. Returns bases sorted by relevance score, along with a recommended base ID and a hint on whether the user needs to explicitly select a base.

NameTypeRequiredDescription

searchQuerystringrequiredThe query string to search for bases by name (case-insensitive, partial matches supported).

airtablemcp_search_candidate_linked_records#Searches for records that are valid candidates for a linked-record (foreign-key) field, returning each candidate's record ID along with the fields the linked-record field is configured to display (the same fields shown on the in-product card). Use this to find the record ID to put in a linked-record field when calling submit_form or update_records_for_table. Use list_pages_for_base to find the pageId if needed. Use get_form_schema (for forms) to discover the linked field's fieldId. Pass the fieldId of the linked-record field you are filling (not the table it links to — the foreign table is resolved automatically). The pageId must be a page that surfaces the linked field: for submit_form this is the form's pageId; for update_records_for_table pass the interface page that shows the record/field being edited. Pass interfaceId when the page lives inside an interface; omit it for a standalone form. A linked-record field's candidates can be restricted by dynamic filters that reference the record's OTHER field values, so you must supply those values for the filters to apply: when filling a NEW record (e.g. for submit_form), always pass fields with the other values you have so far or plan to submit; when editing an EXISTING record, pass recordId, plus fields for any other values you are changing in the same update (a value in fields takes precedence over the record's stored value; anything not in fields falls back to the stored value). If you pass neither, the filters are evaluated against blank values and the results may include records that are not actually selectable, or miss ones that are.8 params

Searches for records that are valid candidates for a linked-record (foreign-key) field, returning each candidate's record ID along with the fields the linked-record field is configured to display (the same fields shown on the in-product card). Use this to find the record ID to put in a linked-record field when calling submit_form or update_records_for_table. Use list_pages_for_base to find the pageId if needed. Use get_form_schema (for forms) to discover the linked field's fieldId. Pass the fieldId of the linked-record field you are filling (not the table it links to — the foreign table is resolved automatically). The pageId must be a page that surfaces the linked field: for submit_form this is the form's pageId; for update_records_for_table pass the interface page that shows the record/field being edited. Pass interfaceId when the page lives inside an interface; omit it for a standalone form. A linked-record field's candidates can be restricted by dynamic filters that reference the record's OTHER field values, so you must supply those values for the filters to apply: when filling a NEW record (e.g. for submit_form), always pass fields with the other values you have so far or plan to submit; when editing an EXISTING record, pass recordId, plus fields for any other values you are changing in the same update (a value in fields takes precedence over the record's stored value; anything not in fields falls back to the stored value). If you pass neither, the filters are evaluated against blank values and the results may include records that are not actually selectable, or miss ones that are.

NameTypeRequiredDescription

baseIdstringrequiredThe ID of the base containing the page and the linked-record field. Must start with "app" and is 17 characters long. Example: "appZfrNIUEip5MazD". Do not substitute user-facing names for baseId. To get baseId, use the search_bases or list_bases tool.

fieldIdstringrequiredThe ID of the linked-record (foreign-key) field whose candidate records you want to search. Field IDs must start with "fld" and is 17 characters long. Example: "fldGlRtkBNWfYnPOV". Do not substitute user-facing names for IDs. To get fieldId, use the list_tables_for_base tool.

pageIdstringrequiredThe ID of the page that surfaces the linked-record field. Must start with "pag" and is 17 characters long. Example: "pagXxYyZzAaBbCcDd".

querystringrequiredThe text to search candidate records by. Matching is case-insensitive against each record's display name. Pass an empty string to list candidates without filtering.

fieldsstringoptionalThe values entered so far (or planned) for the OTHER fields of the record being filled. The linked field's cross-field dynamic record-selection filters are evaluated against these values, and omitting them can return records that are not actually selectable. When searching candidates for a new record (e.g. a submit_form submission), always pass every other field value you know. When editing an existing record (recordId provided), pass the values you are changing in the same update — each value here overrides the record's stored value, and fields not passed fall back to the stored values. Field IDs must start with "fld" and is 17 characters long. Example: "fldGlRtkBNWfYnPOV". Do not substitute user-facing names for IDs. To get fieldId, use the list_tables_for_base tool.

interfaceIdstringoptionalThe ID of the interface containing the page, or null/omitted for a standalone form (one that is not inside an interface). Must start with "pbd" and is 17 characters long.

limitintegeroptionalThe maximum number of records to return. The server may return fewer. Defaults to a small page size when omitted.

recordIdstringoptionalThe ID of the EXISTING record being updated, when searching linked records in the context of an existing record (e.g. for update_records_for_table). The record's stored values are used to apply the linked field's cross-field dynamic record-selection filters, except for values you also pass in fields, which take precedence — so pass both when the update changes a value those filters depend on. Must start with "rec" and is 17 characters long. Example: "recZOTa3BDHxlJNzf". Do not substitute user-facing names for IDs To get recordId, use the list_records_for_table tool or display_records_for_table tools.

airtablemcp_search_records#Searches for records in a table using a free-text query with fuzzy matching and token-based search. Prefer this over list_records_for_table for free-text search on large tables.4 params

Searches for records in a table using a free-text query with fuzzy matching and token-based search. Prefer this over list_records_for_table for free-text search on large tables.

NameTypeRequiredDescription

baseIdstringrequiredThe ID of the base containing the table. Must start with "app" and is 17 characters long.

fieldsstringrequiredThe fields to search over. Either pass an array of field IDs/names, or the literal string "ALL_SEARCHABLE_FIELDS" to search across all searchable fields.

querystringrequiredThe search query. Matches are case-insensitive and term-order independent.

tablestringrequiredThe table to search. Accepts either a table ID (e.g., "tblGlReoTNWfYnXIG") or a table name (e.g., "Orders"). Names are resolved case-insensitively within the base.

airtablemcp_submit_form#Submits a form, creating a new record in the form's source table. Call get_form_schema first on the form's pageId to discover which fields the form collects, their fieldIds, types, required/read-only flags, select-field choices, and any prefilled values and visibility filters — do not assume every column on the source table is on the form. The schema response includes the interfaceId (null for standalone forms) to pass back here. For linked-record fields, use search_candidate_linked_records to find the record IDs to submit. Always include that tool's fields param with the other values you plan to submit here, so its results respect the linked field's dynamic record-selection filters. Use list_pages_for_base to find the pageId if needed. Pass the baseId and pageId of the form, the interfaceId if the form lives inside an interface (otherwise omit it), and a fields object mapping field IDs to cell values (same shape as the create_records_for_table tool). For singleSelect and multipleSelects fields, the value must be a choice name from the field's options.choices in the get_form_schema response, exactly as written there — do not invent or reword option names. Supports entry-level form pages and record-creation row forms (forms embedded in other interface page types). Respect the visibility filters from get_form_schema: do not submit a value for any field hidden by its own visibilityFilters or its section's visibilityFilters. A field is visible only when the submitted values satisfy its filter and the filters of any fields it depends on. Do not set a field that wasn't requested just to make another visible. If a hidden field is requested to be filled but the values don't reveal it, confirm how to proceed before submitting. {"baseId": "appXxx...", "pageId": "pagXxx...", "interfaceId": "pbdXxx...", "fields": {"fldXxx...": "Hello world"}}4 params

Submits a form, creating a new record in the form's source table. Call get_form_schema first on the form's pageId to discover which fields the form collects, their fieldIds, types, required/read-only flags, select-field choices, and any prefilled values and visibility filters — do not assume every column on the source table is on the form. The schema response includes the interfaceId (null for standalone forms) to pass back here. For linked-record fields, use search_candidate_linked_records to find the record IDs to submit. Always include that tool's fields param with the other values you plan to submit here, so its results respect the linked field's dynamic record-selection filters. Use list_pages_for_base to find the pageId if needed. Pass the baseId and pageId of the form, the interfaceId if the form lives inside an interface (otherwise omit it), and a fields object mapping field IDs to cell values (same shape as the create_records_for_table tool). For singleSelect and multipleSelects fields, the value must be a choice name from the field's options.choices in the get_form_schema response, exactly as written there — do not invent or reword option names. Supports entry-level form pages and record-creation row forms (forms embedded in other interface page types). Respect the visibility filters from get_form_schema: do not submit a value for any field hidden by its own visibilityFilters or its section's visibilityFilters. A field is visible only when the submitted values satisfy its filter and the filters of any fields it depends on. Do not set a field that wasn't requested just to make another visible. If a hidden field is requested to be filled but the values don't reveal it, confirm how to proceed before submitting. {"baseId": "appXxx...", "pageId": "pagXxx...", "interfaceId": "pbdXxx...", "fields": {"fldXxx...": "Hello world"}}

NameTypeRequiredDescription

fieldsobjectrequiredAn object containing field IDs as keys and field values as values. Field values should match the field type (e.g., strings for singleLineText fields, numbers for numeric fields, arrays of strings for multipleSelects fields). For singleSelect fields, use the option name as a plain string (e.g., "Done"). For multipleSelects fields, use an array of option name strings (e.g., ["Tag1", "Tag2"]). For multipleRecordLinks (linked-record) fields, use an array of record IDs from the linked table. Field IDs must start with "fld" and is 17 characters long. Example: "fldGlRtkBNWfYnPOV". Do not substitute user-facing names for IDs. To get fieldId, use the list_tables_for_base tool.

pageIdstringrequiredThe ID of the form page to submit. Must start with "pag" and is 17 characters long. Example: "pagXxYyZzAaBbCcDd".

interfaceIdstringoptionalThe ID of the interface containing the form page, or null/omitted for a standalone form. When set, this is required so the agent's interface-level access permissions are evaluated correctly. Must start with "pbd" and is 17 characters long.

airtablemcp_test_automation_webhook_trigger#Re-runs the trigger test for a genericWebhookReceived automation and waits briefly for a newly captured payload schema. This is an automation trigger operation, not an Airtable Webhooks API operation. Call get_automation first. The external system must POST a representative object payload to the returned webhookUrl before this tool can capture its schema. For a deployed automation, posting the sample also runs the live automation and may cause side effects. This tool does not send the sample or deploy or undeploy the automation. {"baseId": "appZfrNIUEip5MazD", "automationId": "wflGlRtkBNWfYnPOV"}2 params

Re-runs the trigger test for a genericWebhookReceived automation and waits briefly for a newly captured payload schema. This is an automation trigger operation, not an Airtable Webhooks API operation. Call get_automation first. The external system must POST a representative object payload to the returned webhookUrl before this tool can capture its schema. For a deployed automation, posting the sample also runs the live automation and may cause side effects. This tool does not send the sample or deploy or undeploy the automation. {"baseId": "appZfrNIUEip5MazD", "automationId": "wflGlRtkBNWfYnPOV"}

NameTypeRequiredDescription

automationIdstringrequiredThe ID of the automation whose webhook trigger should be tested. Must start with "wfl" and is 17 characters long. Example: "wflGlRtkBNWfYnPOV". To get an automationId, use the create_automation tool.

airtablemcp_update_automation#Replaces the entire draft configuration (trigger, graph, name, description) of an existing automation. If the automation is on, live behavior is unchanged until unpublished changes are applied with Update in the Airtable UI. Use list_automations to find the automationId, then call get_automation to retrieve the current trigger, nodes, and description before updating — list_automations returns node summaries without their inputs. Call get_create_automation_instructions once per session for the full catalog of trigger types, action types, and expression shapes. This is a full replacement — all fields (trigger, nodes, name, description) must be provided, even if only one changed. The previous configuration is discarded entirely. On success, the response includes an actionId that can be passed to revert_action to undo the update and restore the previous configuration.6 params

Replaces the entire draft configuration (trigger, graph, name, description) of an existing automation. If the automation is on, live behavior is unchanged until unpublished changes are applied with Update in the Airtable UI. Use list_automations to find the automationId, then call get_automation to retrieve the current trigger, nodes, and description before updating — list_automations returns node summaries without their inputs. Call get_create_automation_instructions once per session for the full catalog of trigger types, action types, and expression shapes. This is a full replacement — all fields (trigger, nodes, name, description) must be provided, even if only one changed. The previous configuration is discarded entirely. On success, the response includes an actionId that can be passed to revert_action to undo the update and restore the previous configuration.

NameTypeRequiredDescription

automationIdstringrequiredThe ID of the automation to update. Must start with "wfl" and is 17 characters long. Example: "wflGlRtkBNWfYnPOV". To get an automationId, use the create_automation tool.

namestringrequiredName for the automation.

triggerobjectrequiredTrigger configuration.

descriptionstringoptionalOptional description for the automation.

airtablemcp_update_field#Updates the name, description, and/or options of a field in an existing Airtable table. At least one of name, description, or options must be specified. Use list_tables_for_base to get fieldId.6 params

Updates the name, description, and/or options of a field in an existing Airtable table. At least one of name, description, or options must be specified. Use list_tables_for_base to get fieldId.

NameTypeRequiredDescription

fieldIdstringrequiredThe ID of the field to update. Field IDs must start with "fld" and is 17 characters long. Do not substitute user-facing names for IDs. To get fieldId, use the list_tables_for_base tool.

tableIdstringrequiredThe ID of the table containing the field. Must start with "tbl" and is 17 characters long. Do not substitute user-facing names for tableId. To get tableId, use the list_tables_for_base tool.

descriptionstringoptionalNo description.

namestringoptionalThe new name for the field. Must be unique within the table (case-insensitive).

optionsobjectoptionalType-specific field options. Currently supports updating formula expressions for formula fields.

airtablemcp_update_records_for_table#Updates records in an Airtable table, leaving all unspecified fields unchanged. Use search_bases and list_tables_for_base to get baseId and tableId first. You can update up to 50 records per request.6 params

Updates records in an Airtable table, leaving all unspecified fields unchanged. Use search_bases and list_tables_for_base to get baseId and tableId first. You can update up to 50 records per request.

NameTypeRequiredDescription

recordsarrayrequiredAn array of record objects to update. Each record must have a "fields" property. Include "id" to update by record ID, or use performUpsert to match by field values.

tableIdstringrequiredThe ID of the table to update records in. Must start with "tbl" and is 17 characters long. Do not substitute user-facing names for tableId. To get tableId, use the list_tables_for_base tool.

fieldIdsarrayoptionalThe IDs of the fields to include in each returned record. If omitted, only the fields you wrote are returned.

performUpsertobjectoptionalEnables upsert behavior. When set, records without a recordId use the fields in fieldIdsToMergeOn to match existing records. If no match, a new record is created. If a match is found, it is updated. If multiple matches, the request fails.

typecastbooleanoptionalWhether or not to perform best-effort automatic data conversion from string values. Defaults to false to preserve data integrity.

airtablemcp_update_table#Updates an existing table's name and/or description in an Airtable base. At least one of name or description must be provided. Use search_bases and list_tables_for_base to get baseId and tableId first.4 params

Updates an existing table's name and/or description in an Airtable base. At least one of name or description must be provided. Use search_bases and list_tables_for_base to get baseId and tableId first.

NameTypeRequiredDescription

tableIdstringrequiredThe ID of the table to update. Must start with "tbl" and is 17 characters long. Do not substitute user-facing names for tableId. To get tableId, use the list_tables_for_base tool.

descriptionstringoptionalNo description.

namestringoptionalThe new name for the table. Must be unique within the base (case-insensitive).

Airtable MCP

Airtable MCP connector

Install the SDK

Set your credentials

Authorize and make your first call

What you can do

Tool list