Airtable MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AIRTABLE_TOKEN | Yes | Your Airtable personal access token | |
| AIRTABLE_BASE_ID | Yes | Your Airtable base ID | |
| AIRTABLE_TABLE_NAME | Yes | The name of the table in Airtable (e.g., 'Employee information') |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| createEmployeeC | Create a new employee in Airtable |
| updateEmployeeC | Update an existing employee in Airtable |
| deleteEmployeeC | Delete an employee from Airtable |
| dashboardB | Get employee dashboard statistics |
| advancedEmployeeSearchC | Search employees using different fields |
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 5 tools
Each tool has a clearly distinct purpose: create, update, delete, dashboard statistics, and employee search. The CRUD actions target different operations, and search is distinguishable from dashboard aggregation.
The CRUD tools consistently use camelCase verb_noun naming (createEmployee, updateEmployee, deleteEmployee). However, dashboard is a bare noun and advancedEmployeeSearch is noun-oriented rather than following the same verb_noun pattern.
Five tools is well-scoped for an employee-management Airtable integration. Each tool earns its place by covering a core operation or query capability without excessive surface area.
The set covers create, update, delete, search, and dashboard statistics, which supports most employee workflows. A direct getEmployee-by-ID or list-all-employees operation is missing, but search can partially compensate.