airtable-user-mcp
Related Servers
Alternatives to airtable-user-mcp
- AlicenseBqualityAmaintenanceA 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.164,130 npm455TypeScriptMIT
Related Servers
- AlicenseNot gradedqualityDmaintenanceMCP server for Airtable API — manage records, bases, tables, fields, and webhooks through 18 tools.4 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.1295 npm75MIT
- AlicenseAqualityAmaintenanceThe 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.1426 npmMIT
- 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.4 npm1MIT
TDQS
Scored across 67 tools
Each tool has a clearly defined purpose with detailed descriptions, enabling an agent to distinguish even closely related operations (e.g., move_overall_columns vs move_visible_columns). There is no overlap that would cause confusion.
All tools follow a consistent verb_noun pattern in snake_case (e.g., create_field, list_tables, update_view_filters). No mixed conventions or ambiguous verb choices.
With 67 tools, the server is far beyond the typical 3-15 well-scoped range. While it covers many aspects of Airtable, the number is excessive and would overwhelm an agent, leading to slower selection.
Surprisingly missing fundamental record CRUD operations (create_record, update_record, delete_record) despite having many advanced features like view configuration and extension management. This gap severely limits the server's usefulness for core Airtable tasks.