| FMRS | 38 / 100 · D | 74 / 100 · B | 72 / 100 · B |
| Reliability | 6 / 20 | 11 / 20 | 10 / 20 |
|---|
| Security and permissions | 6 / 20 | 15 / 20 | 15 / 20 |
|---|
| Maintenance | 2 / 20 | 17 / 20 | 16 / 20 |
|---|
| Documentation | 12 / 20 | 17 / 20 | 17 / 20 |
|---|
| Setup experience | 12 / 20 | 14 / 20 | 14 / 20 |
| Best for | - Developers wanting to integrate Spotify control into AI assistants or custom apps.
- Scenarios requiring quick implementation of playback, playlist management, volume adjustment, etc.
- Users who already have a Spotify Premium account and a developer application.
| - Developers needing quick, API-key-free web search capabilities
- Privacy-conscious users who prefer local search execution
- AI application development with Claude Desktop or Claude Code
| - Privacy-conscious developers who want local data storage.
- Researchers who need AI-assisted management of large note collections.
- Users of Markdown editors like Obsidian.
|
| Not for | - Users without a Spotify Premium account, as some features (playback control, volume) require Premium.
- Those expecting an officially supported or production-grade solution, as this server is third-party and unverified.
- Remote access over HTTPS, as this server only supports stdio.
| - Enterprise applications requiring high-scale, reliable search APIs
- Users needing advanced search features like custom ranking or filters
- Accessing sites blocked by TLS fingerprinting without installing the optional browser backend
| - Users needing cloud sync and mobile access (unless using the paid cloud service).
- Minimalists who want zero configuration.
- Scenarios requiring large-scale vector databases and complex retrieval (local SQLite may be insufficient).
|
| Required permissions | - Access to user's Spotify data, including playlists, liked songs, recent playback.
- Control playback, including play, pause, skip, volume, etc.
- Modify user's playlists (create, delete, add, remove tracks).
- Access device information (available devices, current device, etc.).
| - Outbound network access to DuckDuckGo and other websites
- Reads environment variables for SafeSearch, region, and CA certificates
- Optionally reads a CA certificate file (for TLS-intercepting proxies)
| - Read and write to the local filesystem (default: ~/basic-memory).
- Perform file and directory operations (create, edit, delete).
- Access local SQLite database (or Postgres/Milvus if configured).
|
| Risks and side effects | - Security: OAuth tokens stored locally in spotify-config.json; if leaked, could lead to account misuse.
- Privacy: AI assistants may access personal data like playback history and playlists.
- Misoperation: AI might perform unintended actions like changing playback or modifying playlists.
- Unofficial: Not maintained by Spotify, may have bugs or security vulnerabilities.
| - Search endpoints may occasionally return empty results or errors, especially when blocked
- Content fetching may be subject to SSRF protection, blocking private or loopback addresses by default
- Misuse could lead to rate limiting or IP blocking
| - Tools have write operations that may unintentionally modify or delete notes.
- Edit operations may overwrite existing content, though there are protections.
- Semantic search and reranking features may require model downloads, adding latency.
- Local data backups are the user's responsibility.
|
| Supported clients | Claude Desktop, Cursor, Cline | Claude Desktop, Claude Code | Claude Desktop, Claude Code, Codex CLI, Cursor, VS Code, ChatGPT, Obsidian |
| Tools | 27 | 2 | 21 |