Airtable MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BASE_ID | No | Your Airtable base ID | |
| AIRTABLE_TOKEN | Yes | Your Airtable API token |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_basesA | List all accessible Airtable bases with their names, IDs, and permission levels |
| describeB | Describe Airtable base or table schema. Use detailLevel to optimize context usage:
|
| queryC | Query Airtable records with filtering, sorting, and pagination. |
| list_governanceB | Return governance allow-lists and PII masking policies. |
| list_exceptionsC | List recent exceptions and remediation proposals. |
| createA | Create Airtable records (requires diff-before-write via dryRun first). |
| updateA | Update Airtable records (requires diff-before-write via dryRun first). |
| upsertC | Upsert Airtable records using performUpsert.fieldsToMergeOn. |
| list_webhooksB | List Airtable webhooks for the default base. |
| create_webhookB | Create a new webhook for a base. |
| refresh_webhookB | Refresh webhook expiration. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 11 tools
Most tools have distinct purposes, but 'create' and 'upsert' could cause confusion as both handle record creation with overlapping functionality. The other tools target clearly different operations like webhooks, schema description, listing, and querying.
The naming is mostly consistent with a verb_noun pattern (e.g., list_bases, create_webhook, refresh_webhook), but 'create', 'describe', 'query', and 'update' deviate by omitting the noun, creating minor inconsistency.
With 11 tools, the count is well-scoped for an Airtable integration, covering core operations like CRUD, webhooks, schema management, and governance without being overwhelming.
The toolset provides strong coverage for Airtable operations, including CRUD, querying, webhooks, and governance. A minor gap exists in missing explicit delete operations for records or webhooks, but agents can likely work around this.