← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

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

DimensionSpotifyscraperPublic Spotify metadata, lyrics and podcasts for LLM agents. No API key, read-only.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
Maintenance14 / 2018 / 20
Documentation13 / 2017 / 20
Setup experience12 / 2014 / 20
Best for
  • Developers needing quick, keyless access to public Spotify metadata.
  • LLM applications that want to provide Spotify data to agents.
  • Personal projects needing music metadata for audio content.
  • Researchers looking to add music search to AI applications.
  • Biomedical researchers
  • Clinicians
  • AI agents that need efficient access to biomedical literature and data analysis
Not for
  • Applications that need to write to a user's Spotify account or access private/library data.
  • Use cases requiring market-accurate availability or region-specific data.
  • Production-critical applications where breakage risk is unacceptable.
  • 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
  • No authentication is required by default.
  • Optionally, SPOTIFY_SP_DC cookie is required to enable lyrics, transcripts, and account tools. This cookie is secret.
  • 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
  • This relies on Spotify's public private endpoints, which can change without notice, causing breakage.
  • There is risk of Spotify banning, but the library includes anti-ban measures.
  • This is unofficial and may violate Spotify's terms of service; use for educational or personal purposes.
  • 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 Desktop, Claude Code, Codex, Other MCP stdio clients
Tools011