Airtable MCP Server vs MCP Memory Server

A side-by-side look at pricing, capabilities, pros, cons, and our editorial scores.

	Airtable MCP Server MCP Servers	MCP Memory Server MCP Servers
Tagline	Model Context Protocol server that gives LLMs full read/write access to your Airtable bases.	Persistent knowledge-graph memory for Claude and other MCP clients
Category	MCP Servers	MCP Servers
Pricing	Free· Open source (MIT) and free to run. You still need an Airtable account and personal access token; Airtable itself is Free / Team $20 per user/mo / Business $45 per user/mo / Enterprise (custom).	Free· Free and open source (MIT). Self-hosted; no vendor charges. Runs locally via npx or Docker.
Model	—	—
Editorial score	—	—
Use cases	Natural-language CRM queries against AirtableLLM-driven lead triage and enrichmentAutomated content calendar updatesBootstrapping new bases, tables and fields from a specRead-only reporting agentsProject tracker status summariesBulk record cleanup via chatThreaded comments and mentions from an assistant	Persistent Claude Desktop memory across chatsLong-lived coding-agent project memoryLightweight personal CRM of people and companiesResearch-agent scratch knowledge graphCross-session preference and style memoryTeam convention and past-bug recall for coding assistantsStructured note-taking backend for MCP clientsLocal-first alternative to hosted memory APIs
Pros	Broad tool coverage — records, schema inspection, table/field creation, and record comments in one server. Works with every major MCP client (Claude Desktop, Claude Code, Cursor, Cline, VS Code) via a generated install config. Fine-grained scope control through Airtable personal access tokens lets you ship a strictly read-only agent. Open source under MIT, zero runtime cost, distributed as a small npm package you can pin or fork. Supports filterByFormula and a dedicated search_records tool so agents can query without downloading whole tables. Honest, prominent security warning about the HTTP transport rather than a silent footgun.	Official, Anthropic-maintained reference implementation - the canonical way to add persistent memory to an MCP client Zero-config install via npx or a one-line Docker command; works out of the box with Claude Desktop's claude_desktop_config.json Simple, inspectable JSONL storage on disk that you can grep, diff, back up and edit by hand Structured entity/relation/observation model is more queryable than a raw text scratchpad and cheaper than a vector DB Nine well-scoped tools plus a live-updating knowledge-graph Resource, so agents can both read and mutate memory Fully open source (MIT) and vendor-neutral - runs against any MCP-speaking model, not just Claude Trivial to fork or wrap for team-specific schemas since the codebase is a single small TypeScript file
Cons	HTTP transport ships with no authentication — safe defaults require a reverse proxy you have to configure yourself. No batching primitives beyond Airtable's own limits, so large writes can be slow and quota-hungry. Airtable API rate limits (5 req/sec/base) still apply and can bottleneck chatty agents. Requires a personal access token with real write power; a compromised MCP client can delete records or alter schema. Community project maintained largely by one developer — response times to issues will vary.	Reference-quality, not production-grade: single-file JSONL storage with no concurrency control, indexing or replication search_nodes is a plain substring match with no embeddings or semantic ranking - large graphs degrade quickly No built-in multi-user, auth or per-project isolation; a shared install mixes memories from every session The model still has to be prompted to actually call the memory tools - forgetful assistants forget to remember No web UI, visualisation or admin surface; you inspect and clean the graph by editing the JSONL yourself Only a local filesystem backend - no Postgres, SQLite or cloud sync option is shipped
Website	github.com	github.com

Pick Airtable MCP Server if

✅ Broad tool coverage — records, schema inspection, table/field creation, and record comments in one server.
✅ Works with every major MCP client (Claude Desktop, Claude Code, Cursor, Cline, VS Code) via a generated install config.
✅ Fine-grained scope control through Airtable personal access tokens lets you ship a strictly read-only agent.
✅ Open source under MIT, zero runtime cost, distributed as a small npm package you can pin or fork.

Pick MCP Memory Server if

✅ Official, Anthropic-maintained reference implementation - the canonical way to add persistent memory to an MCP client
✅ Zero-config install via npx or a one-line Docker command; works out of the box with Claude Desktop's claude_desktop_config.json
✅ Simple, inspectable JSONL storage on disk that you can grep, diff, back up and edit by hand
✅ Structured entity/relation/observation model is more queryable than a raw text scratchpad and cheaper than a vector DB

Compare a different pair →