Airtable Full-Stack MCP
Related Servers
Alternatives to Airtable Full-Stack MCP
- AlicenseNot gradedqualityDmaintenanceExtends Airtable MCP server with full CRUD, bulk import/upsert, data analysis, schema validation, and data export capabilities.MIT
- AlicenseAqualityDmaintenanceAn MCP server that gives AI agents geometric spatial awareness of web page layouts using Playwright, enabling detection of visual occlusion, layout shifts, and spatial relationships.630 npmMIT
Related Servers
- AlicenseAqualityCmaintenanceLightweight TypeScript MCP server for Airtable base discovery, table/view queries, record CRUD, and validated filterByFormula construction.9MIT
- AlicenseAqualityAmaintenanceCommunity MCP server for Airtable that provides 30 tools for managing Airtable bases. Uses Airtable's internal API to support capabilities not available through the official REST API:6731MIT
- AlicenseAqualityCmaintenanceA Model Context Protocol server that provides tools for programmatically managing Airtable bases, tables, fields, and records through Claude Desktop or other MCP clients.12217 npm75MIT
- AlicenseNot gradedqualityBmaintenanceA 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.3 npm1MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for Airtable API — manage records, bases, tables, fields, and webhooks through 18 tools.5 npmMIT
- AlicenseNot gradedqualityAmaintenanceA 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.1,682 npm458TypeScriptMIT
TDQS
Scored across 14 tools
Tools are cleanly partitioned by domain (records, schema, webhooks, automation scripts, Interface Designer), and the 'When NOT to Use' sections strongly reinforce boundaries. The only mild risks are pairs like manage_records vs batch_upsert and set_field_permissions vs configure_detail_sheet, but these are clearly distinguished in practice.
All tools share an 'airtable_' prefix and mostly follow a verb_noun snake_case pattern, which is predictable. Minor deviations include 'airtable_batch_upsert' omitting an explicit object and the broad 'manage' verb used for both records and webhooks.
At 14 tools, this is within the ideal 3-15 range and each tool earns its place across distinct sub-domains: record operations, schema management, webhooks, automation script generation, and interface design. The count feels appropriate for a 'full-stack' Airtable server.
Record CRUD and webhook lifecycles are well covered, but schema tools lack delete operations and Interface Designer tools provide no way to list or delete existing pages. These are notable gaps for a server claiming full-stack coverage and may require manual UI workarounds.