Airtable OAuth MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOST | No | Server host | 0.0.0.0 |
| PORT | No | Server port | 8000 |
| LOG_LEVEL | No | Logging level | INFO |
| MCP_SERVER_NAME | No | Server name (optional) | |
| AIRTABLE_CLIENT_ID | Yes | OAuth client ID from Airtable | |
| MCP_SERVER_VERSION | No | Server version (optional) | |
| AIRTABLE_REDIRECT_URI | Yes | OAuth callback URL | http://localhost:8000/oauth/callback |
| AIRTABLE_CLIENT_SECRET | Yes | OAuth client secret |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_basesA | List all accessible Airtable bases |
| list_tablesA | List tables in a specific base |
| describe_tableB | Get detailed information about a specific table |
| list_recordsB | List records from a table with optional filtering |
| get_recordB | Get a specific record by ID |
| create_recordC | Create a single record |
| create_recordsC | Create multiple records |
| update_recordsC | Update multiple records |
| delete_recordsC | Delete multiple records |
| search_recordsB | Search records using a formula filter |
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 10 tools
Each tool has a clearly distinct purpose with no ambiguity: create_record vs create_records handles single vs batch creation, list_records vs search_records provides listing vs filtered searching, and get_record vs update_records vs delete_records covers different CRUD operations. The descriptions reinforce these distinctions, making tool selection straightforward.
All tools follow a consistent verb_noun naming pattern using snake_case (e.g., create_record, list_bases, update_records). The verbs are appropriate and predictable (create, delete, describe, get, list, search, update), creating a coherent and readable toolset.
With 10 tools, this server is well-scoped for Airtable operations. Each tool earns its place by covering essential CRUD operations, base/table management, and search capabilities. The count is neither too sparse nor bloated, fitting typical agent workflows effectively.
The toolset provides complete coverage for Airtable interactions: CRUD operations on records (create, get, update, delete, list, search), base and table management (list_bases, list_tables, describe_table), and support for both single and batch operations. There are no obvious gaps that would hinder agent workflows.