MCP Everything Server vs Spotify MCP

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

	MCP Everything Server MCP Servers	Spotify MCP MCP Servers
Tagline	The kitchen-sink reference MCP server that exercises every corner of the Model Context Protocol	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· Free and open source (MIT License). No cloud service or paid tier — you run it locally via npx, Docker, or your MCP client of choice.	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	MCP client conformance testingRegression testing of stdio and Streamable HTTP transportsVerifying sampling round-trip behavior in a new agent hostDebugging elicitation UI in an IDE integrationReference reading for authoring a new MCP serverDemoing MCP primitives in workshops and talksSmoke-testing cancellation and progress-notification handlingValidating resource-subscription update delivery	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	Only server that exercises the full MCP feature matrix in one place — tools, resources, prompts, sampling, elicitation, roots, logging, subscriptions, and Tasks Maintained by the Model Context Protocol project itself, so behavior tracks the spec as it evolves (SEP-1686 Tasks, Streamable HTTP, etc.) Runs anywhere an MCP client runs — npx, Docker, Claude Desktop, VS Code, Cursor, Windsurf — with stdio or HTTP transports TypeScript source is short and readable, making it a de-facto reference for how each handler should be shaped MIT-licensed, no telemetry, no signup, no cloud dependency Includes progress notifications and cancellation flows that most tutorial servers skip, so client cancel/timeout logic can be exercised properly	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	Explicitly not useful for end users — it does not do anything a human would actually want done Feature drift means some primitives (SEP-1686 Tasks, elicitation) may not yet be implemented in every client, producing red herrings during testing Documentation is a single features.md; there is no guided tour that maps each tool to the spec section it exercises TypeScript-only reference — Python or Rust client authors have to translate patterns themselves Sampling and elicitation flows depend on the client honoring them, so a silent client makes it hard to tell whether the server or the client is at fault	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 MCP Everything Server if

✅ Only server that exercises the full MCP feature matrix in one place — tools, resources, prompts, sampling, elicitation, roots, logging, subscriptions, and Tasks
✅ Maintained by the Model Context Protocol project itself, so behavior tracks the spec as it evolves (SEP-1686 Tasks, Streamable HTTP, etc.)
✅ Runs anywhere an MCP client runs — npx, Docker, Claude Desktop, VS Code, Cursor, Windsurf — with stdio or HTTP transports
✅ TypeScript source is short and readable, making it a de-facto reference for how each handler should be shaped

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 →