airtable-user-mcp
Related Servers
Alternatives to airtable-user-mcp
- AlicenseBqualityBmaintenanceA Model Context Protocol server that provides read and write access to Airtable databases. This server enables LLMs to inspect database schemas, then read and write records.163,650 npm456TypeScriptMIT
Related Servers
- AlicenseNot gradedqualityDmaintenanceMCP server for Airtable API — manage records, bases, tables, fields, and webhooks through 18 tools.6 npmMIT
- AlicenseNot gradedqualityDmaintenanceExtends Airtable MCP server with full CRUD, bulk import/upsert, data analysis, schema validation, and data export capabilities.MIT
- AlicenseAqualityDmaintenanceA Model Context Protocol server that provides tools for programmatically managing Airtable bases, tables, fields, and records through Claude Desktop or other MCP clients.12291 npm75MIT
- AlicenseAqualityBmaintenanceThe world's first dual-engine Airtable MCP server: programmatic control of both Airtable REST/Metadata APIs and Interface Designer (Dashboards, Kanbans, Column Edit Locks, and Publishing) via Chrome CDP.14MIT
- AlicenseAqualityCmaintenanceLightweight TypeScript MCP server for Airtable base discovery, table/view queries, record CRUD, and validated filterByFormula construction.9MIT
- AlicenseNot gradedqualityDmaintenanceA production-ready MCP server for Airtable that enables programmatic management of bases, tables, fields, and records through Claude Desktop or other MCP clients using Effect for type-safe and robust API interactions.6 npm1MIT
TDQS
Scored across 73 tools
There are many overlapping clusters: list_tables/get_base_schema/get_table_schema/list_fields, create_field/create_formula_field/update_field_config/update_formula_field, and a large family of view-column tools (set_view_columns, show_or_hide_view_columns, show_or_hide_all_columns, move_visible_columns, move_overall_columns, reorder_view_fields). Detailed descriptions help, but several tools have genuinely unclear boundaries and are easy to misselect.
Names are consistently snake_case and mostly follow a verb_noun pattern. There are minor deviations with compound names like show_or_hide_view_columns, create_extension_dashboard, set_view_cell_wrap, and similar actions using different verbs (set/update/apply), but the convention remains predictable.
At 73 tools, the surface is far beyond a well-scoped set and includes many micro-operations for views, record templates, extensions, daemon management, and sync. The manage_tools profile mechanism mitigates this somewhat, but the default full profile is still extremely heavy for an agent to navigate.
Coverage is broad across tables, fields, views, records, record templates, formulas, extensions, view sections, and base-to-base sync, with CRUD for most core resources. Minor gaps remain around base-level lifecycle, comments/webhooks/automations, and some record cell types handled indirectly through separate tools.