| FMRS | 61 / 100 · C | 79 / 100 · B | 74 / 100 · B |
|---|
| Reliability | 8 / 20 | 12 / 20 | 13 / 20 |
|---|
| Security and permissions | 11 / 20 | 18 / 20 | 13 / 20 |
|---|
| Maintenance | 13 / 20 | 17 / 20 | 17 / 20 |
|---|
| Documentation | 16 / 20 | 17 / 20 | 16 / 20 |
|---|
| Setup experience | 13 / 20 | 15 / 20 | 15 / 20 |
|---|
| Best for | - Teams already using Airtable for projects, tasks, or customer data who want AI assistants to operate on it directly
- Developers integrating Airtable automation into Claude, Codex, Cursor, or other MCP clients
- Use cases needing governance and PII-masking controls over AI access to base data
| - Teams already using ClickHouse who want AI assistants to access data directly.
- Scenarios requiring fast, read-only data queries and schema exploration.
| - Teams that want precise control over which database operations an AI can perform, rather than open arbitrary SQL execution
- Scenarios needing a unified MCP setup across multiple database engines
|
|---|
| Not for | - Users who don't use Airtable
- Organizations requiring guaranteed official vendor support (this is a third-party, community-maintained project, not an Airtable product)
- Environments that can't accept running a remote npm package fetched fresh via npx on each launch
| - Scenarios requiring write access to the database without explicit opt-in.
- Production environments with stringent security requirements that avoid default permission settings.
| - Lightweight cases that just want to run a few ad-hoc SQL queries without maintaining a tools.yaml config (a simpler single-database MCP may be a better fit)
|
|---|
| Required permissions | - data.records:read — read records
- data.records:write — create, update, delete records
- data.recordComments:read — read record comments
- data.recordComments:write — create, update, delete comments
- schema.bases:read — view table schemas
- schema.bases:write — create and modify tables and fields
- user.email:read — read user identity (whoami)
- webhook:manage — manage webhooks (optional)
| - Requires read-only access to ClickHouse database (default).
- Optional: write access via CLICKHOUSE_ALLOW_WRITE_ACCESS.
- Optional: destructive operations via CLICKHOUSE_ALLOW_DROP.
| - Database credentials (username/password/connection string) are supplied via env vars or config
- A tool's actual permission is whatever SQL statement is defined in tools.yaml — designed for least privilege, but misconfiguration can still over-expose access
|
|---|
| Risks and side effects | - The server can write, modify, and delete Airtable data and schema; misuse or prompt injection could cause data loss, though create/update require a dryRun diff review
- The Personal Access Token is stored in plaintext in client config environment variables, so config file access must be protected
- This is a third-party project (not maintained by Airtable) fetched fresh from npm via npx on each run, introducing a supply-chain trust dependency on the maintainer
- Destructive operations like delete_table, delete_field, and batch_delete_records exist; some require confirmation but scopes should still be reviewed carefully before granting
| - If write access is enabled, AI might make unintended modifications.
- If DROP access is enabled, data deletion could occur accidentally.
- Credentials may be exposed via environment variables.
| - If tools.yaml defines SQL statements that allow unconstrained writes or deletes, the AI could accidentally modify data
- The prebuilt toolsets (--prebuilt) favor convenience and may expose broader query capability than a specific business actually needs — use a custom tools.yaml in production
|
|---|
| Supported clients | Claude Desktop, Claude Code, Codex, Cursor, Windsurf, VS Code | Claude Desktop | Claude Code, Gemini CLI, Zed, Antigravity |
|---|
| Tools | 42 | 4 | 0 |
|---|