Airtable MCP Server vs Spotify MCP

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

	Airtable MCP Server MCP Servers	Spotify MCP MCP Servers
Tagline	Model Context Protocol server that gives LLMs full read/write access to your Airtable bases.	Model Context Protocol server that hands your LLM the Spotify Web API — playback control, search, queue and playlist management from inside Claude Desktop or any MCP client.
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 / MIT-licensed open source. Requires a free Spotify developer app and a paid Spotify Premium subscription for playback control.
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	Voice-style playback control from Claude DesktopNatural-language playlist buildingQueue management during focus/work sessionsTrack and artist lookup inside a chatBulk playlist reorganization and renamingReference implementation for writing your own MCP serverDemoing agent tool-use on a familiar consumer API
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.	Turnkey MCP install — a single uvx snippet in claude_desktop_config.json is enough to be running in a couple of minutes. Covers the everyday listening surface: playback control, search, queue and full playlist CRUD. Built on the mature spotipy library, so auth and Web API quirks are handled for you. Runs entirely locally over stdio — Spotify tokens never leave your machine. MIT-licensed, ~610 stars, and small enough (a few Python files) to read end-to-end and fork. Works with any MCP-compatible client, not just Claude Desktop — Cursor, Zed and the MCP Inspector all connect.
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.	Explicitly marked inactive as of March 2026 — most incoming PRs will not be merged. Requires a paid Spotify Premium subscription; the Web API blocks playback control on free accounts. No recommendations/audio-features tooling because Spotify deprecated those endpoints in late 2024. OAuth redirect popup can trigger on every tool call when run via uvx; avoiding it means cloning the repo and running locally. Pagination is not yet wrapped, so search results, large playlists and albums are truncated to the first page. No automated test suite, so regressions from upstream spotipy or MCP SDK changes have to be caught by hand.
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 Spotify MCP if

✅ Turnkey MCP install — a single uvx snippet in claude_desktop_config.json is enough to be running in a couple of minutes.
✅ Covers the everyday listening surface: playback control, search, queue and full playlist CRUD.
✅ Built on the mature spotipy library, so auth and Web API quirks are handled for you.
✅ Runs entirely locally over stdio — Spotify tokens never leave your machine.

Compare a different pair →