| FMRS | 61 / 100 · C | 74 / 100 · B |
|---|
| Reliability | 8 / 20 | 13 / 20 |
|---|
| Security and permissions | 11 / 20 | 13 / 20 |
|---|
| Maintenance | 13 / 20 | 16 / 20 |
|---|
| Documentation | 16 / 20 | 15 / 20 |
|---|
| Setup experience | 13 / 20 | 17 / 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
| - Scenarios wanting the smallest possible tool count and lowest context-window overhead for database access
- Cases needing to grant non-technical teammates safe, read-only database access
|
|---|
| 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 needing database administration operations (creating indexes, altering schema) rather than just querying (DBHub is positioned as a query tool, not a DBA management tool)
|
|---|
| 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 a database connection string (DSN), which may contain sensitive credentials
- execute_sql can run arbitrary SQL (including writes) by default — must be constrained via read-only mode or the underlying database account's own permissions
|
|---|
| 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
| - Under default settings, if the connected database account has write access, execute_sql could let the assistant perform an unintended write or delete — pair with a read-only database account in production
- The DSN contains a plaintext password — pay attention to the access permissions on wherever the config is stored
|
|---|
| Supported clients | Claude Desktop, Claude Code, Codex, Cursor, Windsurf, VS Code | Claude Desktop, Claude Code, VS Code, Cursor, Zed |
|---|
| Tools | 42 | 2 |
|---|