Cloudflare MCP Server vs Spotify MCP

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

	Cloudflare MCP Server MCP Servers	Spotify MCP MCP Servers
Tagline	Official suite of remote MCP servers that let Claude, Cursor, and other agents read and control your Cloudflare account.	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	Freemium· Free: $0 USD · Team: $4 USD per user/month · Enterprise: $21 USD per user/month	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	Debugging Workers with live logs from chatDeploying and configuring Workers bindingsGrounded Q&A over Cloudflare developer docsQuerying Radar for real-time internet traffic dataPulling audit logs for compliance answersRunning a headless browser via Browser RenderingAutoRAG pipelines against R2-hosted corporaReviewing Cloudflare One CASB findingsDNS analytics and Logpush inspectionBuilding custom MCP servers from the Demo Day template	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, first-party servers maintained by Cloudflare with 4k+ GitHub stars and active development. Remote-hosted at stable URLs so most clients need only a URL and OAuth login, no local install. Split into 16 focused servers so agents get relevant tools without prompt bloat. Covers most of the Cloudflare platform: Workers, R2, KV, D1, Radar, DNS analytics, AI Gateway, AutoRAG, Browser Rendering, audit logs, CASB. Works with any MCP-capable client - Claude Desktop, Claude Code, Cursor, Windsurf, and OpenAI Responses API. Apache 2.0 source is on GitHub, so teams can self-host, audit, or extend any server. Docs AI Search server gives agents grounded answers over the full developers.cloudflare.com corpus.	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 useful if you already run on Cloudflare - it is not a general cloud MCP. Advanced capabilities inherit Cloudflare paywalls (Browser Rendering, AutoRAG, CASB, Cloudflare One all require paid plans). Write-capable tools mean a compromised or over-permissioned token can push destructive changes; scoping API tokens carefully is on you. Because the servers are hosted by Cloudflare, your agent's queries and returned data traverse Cloudflare infrastructure - not ideal for teams that want everything to stay in-VPC. OAuth and remote-MCP support is still uneven across MCP clients, so setup varies and some clients need a manual token instead. Sixteen separate endpoints can be confusing - discovery of which server owns which capability is not always obvious from client-side.	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 Cloudflare MCP Server if

✅ Official, first-party servers maintained by Cloudflare with 4k+ GitHub stars and active development.
✅ Remote-hosted at stable URLs so most clients need only a URL and OAuth login, no local install.
✅ Split into 16 focused servers so agents get relevant tools without prompt bloat.
✅ Covers most of the Cloudflare platform: Workers, R2, KV, D1, Radar, DNS analytics, AI Gateway, AutoRAG, Browser Rendering, audit logs, CASB.

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 →