Qdrant MCP Server vs Spotify MCP

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

	Qdrant MCP Server MCP Servers	Spotify MCP MCP Servers
Tagline	Official Qdrant MCP server that turns a vector database into a semantic memory layer for Claude, Cursor, Windsurf, and any MCP client.	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 (Apache-2.0). Qdrant itself can be self-hosted for free or used via Qdrant Cloud (free tier available, paid plans from ~$25/mo for managed clusters).	Free· Free / MIT-licensed open source. Requires a free Spotify developer app and a paid Spotify Premium subscription for playback control.
Model	FastEmbed (default: sentence-transformers/all-MiniLM-L6-v2); pairs with any MCP-capable LLM such as Claude 3.5/4, GPT-4o, or local models	—
Editorial score	—	—
Use cases	Persistent memory for Claude Desktop agentsSemantic code snippet search in Cursor and WindsurfPrivate documentation retrieval for internal LLM copilotsTeam knowledge base backed by Qdrant CloudLocal offline vector memory via QDRANT_LOCAL_PATHRead-only knowledge lookup skill for customer-support agentsCross-session context store for autonomous coding agents	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	Official, actively maintained by the Qdrant team with 1.4k+ stars and frequent releases Two-tool surface (store/find) is small enough that models actually use it correctly Bundled FastEmbed means no separate OpenAI/Cohere embedding key is required to get started Configurable tool descriptions let you rebrand the same server as memory, code search, or docs lookup Works across the major MCP clients: Claude Desktop, Cursor, Windsurf, VS Code, and custom agents Apache-2.0 with local, Docker, and uvx install paths including a fully offline QDRANT_LOCAL_PATH mode Read-only mode makes it safe to expose a curated knowledge base without letting the model write to it	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	Only FastEmbed is supported today, so you cannot plug in OpenAI, Cohere, or Voyage embeddings without forking Just two tools: no filtering, hybrid search, payload updates, or collection management surfaced to the model Single active collection per server process; multi-collection agents need multiple server instances or wrapping Assumes you already run and secure a Qdrant instance (self-hosted or Cloud) — not a turnkey managed product Chunking, ingestion pipelines, and re-ranking are entirely your problem; this is a thin bridge, not a RAG framework	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 Qdrant MCP Server if

✅ Official, actively maintained by the Qdrant team with 1.4k+ stars and frequent releases
✅ Two-tool surface (store/find) is small enough that models actually use it correctly
✅ Bundled FastEmbed means no separate OpenAI/Cohere embedding key is required to get started
✅ Configurable tool descriptions let you rebrand the same server as memory, code search, or docs lookup

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 →