mcp-airtable-query
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AIRTABLE_API_KEY | Yes | Airtable API key, e.g. pat... |
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 | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| airtable_statusA | Report non-secret Airtable configuration. |
| list_basesB | List bases available to the token. |
| get_base_schemaA | List tables, fields, and views for a base. |
| list_recordsA | Query records with view, formula, fields, sorting, and pagination. |
| get_recordC | Retrieve one Airtable record. |
| create_recordsA | Create up to ten records in one Airtable request. |
| update_recordsA | Update up to ten records by ID. |
| delete_recordsA | Permanently delete up to ten records. |
| build_filter_formulaA | Build an Airtable filterByFormula string from a validated AND/OR comparison tree. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| airtable_workflow | Prepare a read-first base workflow. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| airtable-server-status | Non-secret runtime capabilities. |
TDQS
Scored across 9 tools
Each tool targets a distinct resource and action: status, bases, schema, records (list/get/create/update/delete), and filter formula building. There is no overlap or ambiguity between tools.
Most tools follow a clear verb_noun pattern (e.g., list_bases, create_records), with 'get' for single items and 'list' for collections. The one deviation is 'airtable_status', which reads more like a noun than a verb, but it is still easily understood.
With 9 tools, the server is well-scoped for Airtable data operations. Each tool serves a necessary function without unnecessary bloat.
The CRUD lifecycle for records is fully covered (list, get, create, update, delete), along with base and schema discovery and a filter helper. There are no significant missing operations for a query-focused Airtable server.