Skip to main content
Glama
Airtable MCP Server

Airtable MCP Server

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
AIRTABLE_TOKENYesYour Airtable personal access token.
AIRTABLE_BASE_IDNoOptional. Your Airtable base ID. If not provided, can be discovered using list_bases tool.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

Use describe and query tools for read flows. All mutations require diff review and idempotency keys.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}
prompts
{
  "listChanged": true
}
resources
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_basesA

List all accessible Airtable bases with their names, IDs, and permission levels

describeC

Describe Airtable base or table schema.

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.

createB

Create Airtable records (requires diff-before-write via dryRun first).

updateB

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

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.1/5.0

Scored across 11 tools

Disambiguation4/5

Most tools target clearly distinct operations: query vs. describe vs. list_bases separate records, schema, and base discovery, and the three webhook tools are well differentiated. However, the bare names create/update/upsert don't indicate the resource, so an agent could plausibly confuse create with create_webhook or wonder whether update touches records or schema.

Naming Consistency3/5

Half the tools follow a clean verb_noun pattern (list_bases, list_webhooks, create_webhook, refresh_webhook, list_governance), but the core record operations are bare verbs with no object (create, update, upsert, query, describe). The convention is readable but clearly mixed within a single server.

Tool Count5/5

Eleven tools is well within a healthy range for an Airtable surface covering bases, records, schema, webhooks, and governance. Each tool maps to a recognizable Airtable capability rather than padding the list.

Completeness3/5

Record creation, update, upsert, query, and schema description are covered, but there is no delete-record tool, which is a core lifecycle operation agents will need. Webhooks also lack a delete/deactivate operation, leaving dead ends in two areas.

Maintenance

ActivitySlowing
ResponsivenessNo recent community issues