Sentry MCP vs Spotify MCP

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

	Sentry MCP MCP Servers	Spotify MCP MCP Servers
Tagline	Official Sentry MCP server: give Claude Code, Cursor, and other AI agents real access to your errors, traces, and triage.	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	Bring-your-own LLM (OpenAI, Anthropic, Azure OpenAI, or OpenRouter) for natural-language search skills; agent-side model is whatever your MCP client runs.	—
Editorial score	—	—
Use cases	Debug production error from IDE agentRoot-cause a latency regression via trace lookupTriage new issues (assign, resolve, comment) from chatCorrelate a failing test with recent Sentry eventsNatural-language search across eventsPost-deploy error-rate investigationPull stack trace and open the offending file for a fixSummarize top issues for a standupQuery self-hosted Sentry from an internal coding agent	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 server from Sentry — kept in step with API changes, not a community wrapper Both a hosted remote endpoint (mcp.sentry.dev, OAuth or Bearer) and a local stdio binary via npx Works with self-hosted Sentry, not only sentry.io One-line install for Claude Code through the Sentry plugin marketplace; also documented for Cursor and MCP Inspector Fine-grained skill toggles let you scope which tools the agent can call Covers the full debugging loop: issues, events, traces, search, and triage actions like assign/resolve/comment Open source, so the tool surface and prompts can be audited or extended	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	You still need a paid Sentry plan to get useful volumes of events, retention, and org seats Natural-language search tools require you to bring your own OpenAI/Anthropic/Azure/OpenRouter key — extra cost and setup Value collapses if your team is not already invested in Sentry as its error/APM backend Remote server is single-tenant per token — sharing across a team means each engineer wires their own auth MCP itself is still young; some clients handle remote servers with headers imperfectly and stdio is often the fallback Read/write tools mean a misbehaving agent can resolve or reassign real issues — human-in-the-loop is not optional	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 Sentry MCP if

✅ Official first-party server from Sentry — kept in step with API changes, not a community wrapper
✅ Both a hosted remote endpoint (mcp.sentry.dev, OAuth or Bearer) and a local stdio binary via npx
✅ Works with self-hosted Sentry, not only sentry.io
✅ One-line install for Claude Code through the Sentry plugin marketplace; also documented for Cursor and MCP Inspector

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 →