Spotify MCP By UnClick
Let your coding agent search Spotify, manage playlists, and pull music metadata without hand-writing OAuth and Web API calls.
Overview
io.github.malamutemayhem/spotify is a MCP server for the Build phase that exposes Spotify music and playlist tools to AI coding agents over stdio.
What is this MCP server?
- stdio MCP server runnable via npx @unclick/spotify-mcp (v0.1.0)
- Spotify-focused tools for tracks, playlists, and music discovery from UnClick
- Published npm package with Model Context Protocol server schema
- Fits agent-driven prototypes for music apps, DJ tools, or playlist automations
- Source in unclick monorepo under packages/standalone/spotify-mcp
- Server version 0.1.0 per MCP server.schema.json
- npm package @unclick/spotify-mcp with stdio transport
- Published under UnClick repository subfolder packages/standalone/spotify-mcp
Community signal: 4 GitHub stars.
What problem does it solve?
Hooking Spotify’s Web API into an agent workflow means OAuth setup, endpoint knowledge, and repetitive glue code every time you prototype a music feature.
Who is it for?
Indie builders adding Spotify-powered features to agents, side projects, or SaaS prototypes who want MCP instead of custom API middleware.
Skip if: Teams that need enterprise Spotify partner quotas, heavy batch ETL, or production playback licensing without their own backend.
What do I get? / Deliverables
After you register the server, your agent can invoke packaged Spotify tools from the chat so you ship playlist and discovery features faster.
- Registered stdio MCP server in your agent config
- Agent-callable Spotify music and playlist tools
- Faster iteration on Spotify-backed features without custom API wrappers
Recommended MCP Servers
Journey fit
Third-party API bridges belong on the Build shelf because you wire them while implementing product features, not during early ideation. Integrations is the canonical home for MCP servers that expose an external SaaS API to Claude Code, Cursor, or Codex.
How it compares
Spotify API MCP bridge, not a Claude skill markdown workflow.
Common Questions / FAQ
Who is io.github.malamutemayhem/spotify for?
Solo and indie developers using Claude Code, Cursor, or Codex who want agent-callable Spotify tools while building music or playlist products.
When should I use io.github.malamutemayhem/spotify?
Use it during Build when you are wiring integrations and want the model to search tracks, reason about playlists, or draft features against live Spotify data.
How do I add io.github.malamutemayhem/spotify to my agent?
Add an MCP stdio entry pointing at npx @unclick/spotify-mcp, configure Spotify API credentials per UnClick’s repo docs, then restart your client.