Runs locally: Airtable records, schema, comments, upserts, base/table allow-lists and PII masking
Maintain this server? Claim it
This server only runs locally, from a package. Install it with the instructions on this page to try it.
Pick your client. Values in capitals, like YOUR_TOKEN, are yours to fill in.
Run in a terminal
claude mcp add airtable-mcp \ -e AIRTABLE_TOKEN=YOUR_AIRTABLE_TOKEN \ -- npx -y @rashidazarang/[email protected]
Environment
AIRTABLE_TOKEN (required): Airtable personal access token from https://airtable.com/create/tokens. Grant data.records, data.recordComments and schema.bases (read and write) and user.email:read.AIRTABLE_BASE_ID (optional, not in the config above): Default base ID. When set, other bases are refused unless listed in AIRTABLE_ALLOWED_BASES. Leave unset to use every base the token can reach.AIRTABLE_ALLOWED_BASES (optional, not in the config above): Comma-separated base IDs the server may use. Unset allows every base the token can reach.AIRTABLE_ALLOWED_TABLES (optional, not in the config above): Comma-separated baseId:tableName pairs. In a base listed here, only the listed tables are allowed.AIRTABLE_TOOLSET (optional, not in the config above): Tools to register: full (all tools), core (18 record tools, for clients that cap enabled tools) or a comma-separated list of tool names.AIRTABLE_GOVERNANCE_PATH (optional, not in the config above): Path to a governance JSON file (allow-lists, allowed operations, PII field policies). Defaults to config/governance.json in the working directory, if present.LOG_LEVEL (optional, not in the config above): Log level. Logs go to stderr.EXCEPTION_QUEUE_SIZE (optional, not in the config above): How many recent errors the list_exceptions tool keeps.We don't run packages, so we can't list this server's tools.