Spotify
Wire your coding agent to search Spotify, control playback, and manage playlists without leaving the terminal.
Overview
io.github.markswendsen-code/spotify is a MCP server for the Build phase that lets AI agents search Spotify, control playback, and manage playlists over stdio.
What is this MCP server?
- stdio MCP server published as @striderlabs/mcp-spotify on npm (v0.1.0)
- Search music and manage playlists from agent tool calls
- Control playback (play, pause, skip) through Spotify’s API
- GitHub source at markswendsen-code/mcp-spotify
- Designed for Claude Code–style agents that need ambient or demo music control
- Server version 0.1.0 in MCP server schema
- npm package identifier @striderlabs/mcp-spotify
- Transport type stdio
What problem does it solve?
Builders who work inside AI agents constantly context-switch to Spotify when they want to queue music or run a demo with real playback.
Who is it for?
Indie devs personalizing agent setups with Spotify for focus music, demos, or assistant-driven playlist edits.
Skip if: Teams that need licensed streaming in a customer-facing SaaS product without building their own Spotify compliance story.
What do I get? / Deliverables
After you register the stdio server, your agent can search, play, and curate playlists through MCP tools instead of manual app juggling.
- Registered stdio MCP server entry pointing at @striderlabs/mcp-spotify
- Agent-callable tools for search, playback control, and playlist management
- Repeatable local workflow for music actions from the coding agent
Recommended MCP Servers
Journey fit
Consumer API bridges are installed while you configure agent tooling for a product or personal dev workflow, not during idea or launch SEO work. Spotify is an external service integration exposed to the model via MCP stdio, which is the integrations shelf rather than core backend code.
How it compares
Spotify MCP integration for agents, not a DAW plugin or music recommendation skill.
Common Questions / FAQ
Who is io.github.markswendsen-code/spotify for?
Solo and indie builders using Claude Code, Cursor, or Codex who want Spotify search and playback as MCP tools during development.
When should I use io.github.markswendsen-code/spotify?
Use it while configuring build-phase agent integrations when you want music control callable from the same session as your code agent.
How do I add io.github.markswendsen-code/spotify to my agent?
Install @striderlabs/mcp-spotify from npm, configure stdio MCP in your client, and provide valid Spotify API or OAuth credentials per the repo README.