M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

Compare scores, permissions, risks, and fit in one decision-focused table.

DimensionSpotify Streamable MCP ServerMCP server for Spotify—search music, control playback, manage playlists and saved tracks.BioMCPOne binary. One grammar. Evidence from the biomedical sources you already trust.
FMRS61 / 100 · C75 / 100 · B
Reliability8 / 2010 / 20
Security and permissions14 / 2016 / 20
Maintenance9 / 2018 / 20
Documentation17 / 2017 / 20
Setup experience13 / 2014 / 20
Best for
  • Developers who want to integrate Spotify playback control into AI assistants or workflows
  • Scenarios requiring voice control of music
  • Agents that need batch processing of music searches and playlist operations
  • Biomedical researchers
  • Clinicians
  • AI agents that need efficient access to biomedical literature and data analysis
Not for
  • Scenarios that require a stable, final MCP protocol version (currently targets candidate)
  • Users who do not want to configure OAuth and Spotify API credentials
  • Developers needing fine-grained access to the full raw Spotify API
  • Users needing to write to upstream databases (read-only)
  • Users requiring direct access to closed datasets (e.g., COSMIC is not directly integrated)
  • Users expecting all advanced features without API keys
Required permissions
  • Read playback state, modify playback control (play, pause, skip, volume, etc.)
  • Read and modify playlists (private, collaborative, public)
  • Read and modify saved tracks in the user library
  • Access current track and device information
  • Requires internet access to query public biomedical APIs
  • Optional API keys (NCBI, Semantic Scholar, OpenFDA, etc.) to improve rate limits or unlock features
  • Local read/write access for skills, cache, and local study data (e.g., `~/.local/share/biomcp`)
Risks and side effects
  • OAuth tokens stored in file or KV; security risk if not encrypted
  • Requires correct device ID; playback control may fail if wrong
  • Playback behavior depends on Spotify account type (free may be limited) and Premium service
  • Since targeting MCP candidate version, protocol compatibility may change over time
  • Upstream API rate limits may affect performance
  • Some data sources (e.g., KEGG) have licensing terms that restrict non-academic use
  • Features requiring API keys (e.g., OncoKB) may be incomplete without them
  • Local binary installations need regular updates for compatibility
Supported clientsClaude DesktopClaude Desktop, Claude Code, Codex, Other MCP stdio clients
Tools511