Manage Airtable bases: schema, field CRUD, views, formula validation, extensions
The io.github.Automations-Project/airtable-user-mcp MCP server provides capabilities to manage Airtable bases, including schema handling, field create/update/delete, view management, and formula validation. It is categorized for Airtable API development and includes tooling topics such as schema-management, formula-editor, and mcp-server.
๐ ๏ธ Key Features
Manage Airtable bases
Schema management
Field CRUD
Views management
Formula validation
Extensions support
๐ Use Cases
Define and update Airtable schemas
Maintain Airtable records/fields via CRUD operations
Validate Airtable formulas during development
Manage Airtable views as part of setup
โก Developer Benefits
Developer-focused tooling for Airtable API work
Supports schema-management and formula-editor workflows
Fits into MCP and mcp-server based integrations
Includes integration-related vscode-extension topic coverage
โ ๏ธ Limitations
The provided excerpt does not describe non-Airtable data sources, authentication/permissions, or supported Airtable API versions.
Full Airtable internal API โ schema, views, fields, records, extensions, templates
โ
Language Server (LSP)
Standalone multi-editor support โ Neovim, Helix, OpenCode
All above
IDE Auto-Setup
One-click MCP config for 23 AI clients (Cursor, Windsurf, Claude Desktop, Claude Code, Cline, Amp, Codex, Gemini CLI and more)
โ
AI Skill
One Airtable skill folder (rules, function reference, MCP tool guide, workflows, prompt recipes) installed into 70+ AI coding clients; it carries the MCP prompts as recipes, with your own edits under global scope
โ
Daemon + Tunnel
Persistent background server; optional Cloudflare or ngrok remote access
Browser-based Airtable login with SSO/2FA โ credentials in your OS keychain
โ
Why this exists
Airtable's public Web API has never exposed some of the most common tasks builders actually need: creating a formula field, tweaking a view's filter set, installing an extension, or validating a formula before it breaks production. The official Airtable MCP server is a thin wrapper over that same REST API, so it inherits every one of those gaps.
airtable-user-mcp is an add-on to the official Airtable MCP, not a replacement. It uses Airtable's own internal API (the one the web UI uses) to cover exactly the surface area the REST API can't reach. Register both servers in your AI client and your assistant gets the full Airtable automation experience โ records over HTTP via the official MCP, plus schema, formulas, views, and extensions via this one.
What airtable-user-mcp adds on top of the official Airtable MCP
This is a coverage map, not a "pick one" decision โ the two servers are complementary and designed to run side-by-side.
Capability
Official Airtable MCP
airtable-user-mcp
Total tools
~17
74 (73 + manage_tools)
Auth model
Personal Access Token or OAuth, per-scope setup
Log in once with your normal Airtable account (SSO/2FA supported)
Transport
HTTP (remote)
stdio (local, private)
Data never leaves your machine
โ Requests go through mcp.airtable.com
โ Runs locally against Airtable's API
Schema read (bases, tables, fields, views)
Partial (no view config)
Full โ filters, sorts, groups, visibility, row height, descriptions
npx -y airtable-user-mcp login # one-time browser login
claude mcp add airtable --scope user -- npx -y airtable-user-mcp # Claude Code
airtable-user-mcp is additive. Register the official Airtable MCP following Airtable's setup guide, then add this one alongside it in the same mcpServers block:
Your MCP client will expose every tool from both servers. The two entries are independent โ rename the keys (airtable, airtable-official, airtable-user-mcp, etc.) however makes sense for your workflow.
What's In This Repo
This monorepo ships three products from one source tree:
List profiles, switch profile, toggle tools/categories (meta-tool, always enabled โ not part of any profile)
Base Sync
1
sync_base โ copy a base's schema, views, and records to another base. mode=plan/diff/status are read-only; mode=apply mutates the destination and, with policy=mirror plus the confirmation flags, can delete tables, fields, views, sections and records; mode=reconcile updates local mapping state. Drift-guarded and resumable via journal.
Daemon Control
1
manage_daemon โ action=status is read-only self-diagnosis: daemon liveness, transport, uptime, tunnel URL, and the live session state (dead session, last breaker trip with Airtable's own response body, browser busy queue) that tells "daemon gone" from "session dead" from "browser busy". Also start / restart / stop / tunnel_enable / tunnel_disable / token_rotate. full profile only.
The extension starts the shared MCP daemon whenever a tool call needs one, so every VS Code window uses one
Airtable browser session instead of one per window โ that duplication is what produced most "session dead" errors.
A daemon you stop from the dashboard stays stopped, and if it cannot start, the extension falls back to a
per-window server so your tools keep working.
Because a daemon is usually running, other MCP clients on the same machine (Claude Desktop, Cursor, Cline, Amp)
attach to it and therefore run under its auth mode and HTTP client rather than their own โ deliberately, since
two browsers on one Airtable profile crash. Each such client prints one stderr line saying so. See
Sharing one daemon across clients.
LSP Server
airtable-user-lsp is a standalone language server for Airtable formula, script, and automation files โ works in any LSP-capable editor, not just VS Code.
bash
# stdio mode โ works standalone, no daemon needed
npx airtable-user-lsp --stdio
Features: diagnostics, completions, hover documentation, and signature help for .formula, .ats, and .ata files.
When the daemon is running, it auto-spawns airtable-user-lsp --tcp so multiple editors share one language server instance. The TCP port is written to ~/.airtable-user-mcp/daemon.lock as port_lsp.
See packages/lsp-server/README.md for per-editor configuration (Neovim, OpenCode, Helix). Zed is not supported: it starts only language servers that a Zed extension registers.
Supported IDEs
The extension auto-configures MCP for 23 AI clients, among them:
image
image
image
Claude Desktop
Claude Code
Cursor
Windsurf
Cline
Amp
Codex CLI
OpenCode
Zed
Also supported: Windsurf Next, Antigravity, Factory Droid, fx, Gemini CLI, GitHub Copilot CLI, Grok Build, Junie, Kilo Code, Kimi Code, Kiro CLI, Mastra Code, MCPorter and Pi.
VS Code itself needs no config file, because the extension registers the server there. Only global config files are written, and never one for a client that is not on this machine. The client table comes from neondatabase/add-mcp (Apache-2.0); see packages/extension/THIRD_PARTY_NOTICES.md.
Don't use VS Code? Use the standalone MCP server directly:
VS Code ^1.100.0 (or any fork exposing the McpServerDefinitionProvider API)
Node.js โ bundled via the VS Code runtime; no separate install needed
Google Chrome (or Edge / Chromium) โ the Airtable login flow uses Patchright in headless mode. Falls back to msedge on Windows and chromium on Linux. The extension shows an actionable warning if no supported browser is detected.
airtable-user-lsp โ LSP server for formula / script / automation files
scripts/
Build tooling (esbuild bundler, dep vendoring)
bash
pnpm install # install all packages
pnpm build # build shared โ webview โ mcp bundle โ extension
pnpm package # build + create airtable-formula-X.Y.Z.vsix
pnpm test# run all unit tests
pnpm dev # start webview dev server (browser preview)
How the MCP server is bundled:scripts/bundle-mcp.mjs esbuilds packages/mcp-server/src/ into packages/extension/dist/mcp/. Then scripts/prepare-package-deps.mjs vendors patchright, patchright-core, otpauth, impit and @ngrok/ngrok into dist/node_modules/ before vsce package runs, so an installed extension needs no npm install at runtime.
Platform-specific VSIXes.impit (the Chrome-TLS HTTP client) and @ngrok/ngrok (the ngrok tunnel provider) keep their compiled native binary in separate per-platform npm packages, and only the one matching the build machine is ever installed. A single VSIX therefore cannot carry working native binaries for every platform. Instead we publish one VSIX per platform, each vendoring only its own binaries โ VS Code and Open VSX hand each user the build matching their machine. Supported targets:
Target
impit
@ngrok/ngrok
win32-x64
impit-win32-x64-msvc
@ngrok/ngrok-win32-x64-msvc
win32-arm64
impit-win32-arm64-msvc
@ngrok/ngrok-win32-arm64-msvc
darwin-x64
impit-darwin-x64
@ngrok/ngrok-darwin-x64
darwin-arm64
impit-darwin-arm64
@ngrok/ngrok-darwin-arm64
linux-x64
impit-linux-x64-gnu
@ngrok/ngrok-linux-x64-gnu
linux-arm64
impit-linux-arm64-gnu
@ngrok/ngrok-linux-arm64-gnu
alpine-x64
impit-linux-x64-musl
@ngrok/ngrok-linux-x64-musl
alpine-arm64
impit-linux-arm64-musl
@ngrok/ngrok-linux-arm64-musl
linux-armhf (32-bit ARM) is not published: impit ships no arm-gnueabihf build, so an armhf VSIX would advertise airtableFormula.mcp.httpClient: "impit" and then fail with "Cannot find native binding". No untargeted fallback is published either, for the same reason.
The matrix is defined once in scripts/vsix-targets.mjs; versions and tarball hashes are pinned to pnpm-lock.yaml. scripts/package-targets.mjs builds every target and scripts/assert-vsix-binaries.mjs verifies each artifact contains exactly its own platform's .node files and no other's โ byte-for-byte, against the SHA-256 digests in scripts/native-binary-digests.json, which are recorded from tarballs verified against pnpm-lock.yaml's integrity hashes. Filenames, package.jsonos/cpu, and a magic number are all labels an artifact carries about itself and cannot distinguish an x64 binary from an ARM64 one, or a glibc build from a musl one; an exact digest can.
Together these are eight target artifact packaging/assertion smokes โ eight .vsix files built and their contents verified on one machine. They are not runtime smokes of eight native bindings: any single host can only load the binding compiled for itself, so only the host target's binding receives a genuine runtime load. Verifying the other seven by exact content is the strongest claim a single-host build can make about them.
The standalone npm package airtable-user-mcp is unaffected and stays universal โ npm resolves the right optional dependency on your own machine at install time.
Support This Project
This project is built and maintained with the help of AI coding tools. If you find it useful and want to support continued development (new tools, updates, bug fixes), you can contribute by gifting Claude Code credits โ the primary tool used to build this project.
Interested? Open an issue or reach out to discuss feature requests and sponsorship.