Reaper MCP vs Spotify MCP — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Reaper MCP vs Spotify MCP
In-depth architectural comparison of the Reaper MCP and Spotify MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Reaper MCP
Art & Culture · Local stdio
Quality: 63/100 (Good) | Auth: No auth required
Spotify MCP
Art & Culture · Local stdio
Quality: 52/100 (Good) | Auth: No auth required
Verdict Summary: Choose Reaper MCP if you need specialized Art & Culture tools running via a local process. Choose Spotify MCP if your workspace requires Art & Culture integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Reaper MCP when:
You need dedicated capabilities in the Art & Culture domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
MCP server enabling AI assistants to control REAPER DAW for mixing, mastering, MIDI composition, and full music production with 129 tools
Conversational Spotify control with intent-shaped tools: play by description, queue, devices, playlists, and library, plus a 2-minute PKCE setup wizard. Built for the post-Feb-2026 Spotify Web API. npx -y @xavifabregat/spotify-mcp
Category & Scope
Tools & Capabilities Breakdown
Reaper MCP Tools (176)
get_track_count
Get the total number of tracks in the current REAPER project (excluding master track).
get_track
Get information about a track.
Args:
track_index: Track index (0-based). Use -1 for the master track.
Returns:
Object with 'info': guid, name, volume, volume_db, pan, muted, soloed,
has_midi, has_audio, fx_names, role.
get_all_tracks
Get information about all tracks in the project.
get_master_track
Get information about the master track.
insert_track
Insert a new track at the specified index.
Args:
index: Position to insert track (0-based). If not specified, adds at end.
name: Optional name for the new track.
Returns:
Info about the created track.
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Reaper MCP is categorized under Art & Culture and uses a local stdio subprocess. In contrast, Spotify MCP belongs to Art & Culture using local stdio subprocess. Select Reaper MCP when you need capabilities focused on art & culture and Spotify MCP when you require tools for art & culture.
Delete a track.
Args:
track_index: Track index to delete (0-based). Cannot delete master track (-1).
set_track_name
Set the name of a track.
Args:
track_index: Track index (0-based) or -1 for master track.
name: New name for the track.
set_track_volume
Set the volume of a track in decibels.
Args:
track_index: Track index (0-based) or -1 for master track.
volume_db: Volume in dB (0 = unity gain, -inf to +12 typical range).
set_track_pan
Set the pan position of a track.
Args:
track_index: Track index (0-based) or -1 for master track.
pan: Pan position from -1.0 (full left) to 1.0 (full right). 0 = center.
set_track_mute
Set the mute state of a track.
Args:
track_index: Track index (0-based) or -1 for master track.
mute: True to mute, False to unmute.
set_track_solo
Set the solo state of a track.
Args:
track_index: Track index (0-based) or -1 for master track.
solo: True to solo, False to unsolo.
track_fx_get_count
Get the number of FX plugins on a track.
Args:
track_index: Track index (0-based) or -1 for master track.
Returns:
Object with 'ret' field containing count.
+164 more tools listed on main page
Spotify MCP Tools (11)
play
Play by free-text query (search → best match → play) or Spotify URI