io.github.markswendsen-code/spotify
strider-spotify
MCP server for Spotify - let AI agents control playback, search music, and manage playlists
alive probed 2026-10-19
15tools
≈ 1.0ktokens, estimate
≈ 0.5 %of Claude's 200k window
0.7×the median server
318 msto initialize
7 msto list tools
- Run it
- npx -y @striderlabs/mcp-spotify@0.1.0 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Reports itself as
- strider-spotify 0.1.0
- Capabilities
- tools
- Instructions
- none
- Of a 1M window
- ≈ 0.1 % of a 1M context window, estimate
- Claude count
- The count_tokens endpoint refused the tool schemas: invalid x-api-key. The estimate stands in.
- Repository
- https://github.com/markswendsen-code/mcp-spotify
- Registry
- active, updated 2026-03-15 · registry entry
- Reachable
- 1 of the last 1 probe
Most expensive tools
Estimates with the o200k_base tokenizer.
| Tool | o200k estimate | Share of this server |
|---|---|---|
| play | 142 | 14 % |
| search | 132 | 13 % |
| play_playlist | 111 | 11 % |
| add_to_queue | 88 | 9 % |
| seek | 68 | 7 % |
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The Anthropic count_tokens endpoint refused the tool schemas (invalid x-api-key). A client that validates schemas can refuse them too.