spotify-mcp
PulseGate's liveness check found it on 24 Sep 2026; it has been in the index since 24 Sep 2026. How this is checked
spotify-mcp is an open-source Model Context Protocol server that connects AI agents such as Claude to Spotify. It exposes much of the Spotify API through token-efficient tools, including intelligent batch operations, for developers building agent workflows.
Inferred · not functionally tested
Overview
6 featuresPurpose: Giving AI agents authenticated, efficient access to Spotify music and playback capabilities.
Inferred · not functionally tested
Audience: developers building AI agents and MCP integrations
Inferred · not functionally tested
Functions: agents
Inferred · not functionally tested
Interfaces: API: indicated (inferred, not tested) · MCP: indicated (inferred, not tested) · CLI: indicated (inferred, not tested) · Self-hosting: indicated (inferred, not tested)
Recorded constraints: pricing: open_source · license: Open Source · platforms: WEB · deployment: browser, self_hosted, cli, api_only
Constraint provenance is unknown; confirm requirements with the publisher.
Record sources: github.com. These links do not verify the individual claims.
In the Frameworks & runtimes space, spotify-mcp takes a focused approach. Inferred · not functionally tested: It focuses on giving AI agents authenticated, efficient access to Spotify music and playback capabilities. Inferred · not functionally tested: It is built as an open-source project for developers building AI agents and MCP integrations. Basis unknown · not verified: The project is open source (Open Source). Basis unknown · not verified: It runs on the web, the command line, and API, and it can be self-hosted.
It is developed by Jamie Wilkinson. Inferred · not functionally tested: Among its 6 catalogued features are Spotify API access, MCP server, and AI agent integration. Inferred · not functionally tested: Catalogued interfaces include an MCP server and a public API.
Summary written by a language model from the project’s public pages.
Tasks: Inferred · not functionally tested
- Spotify API access
- MCP server
- AI agent integration
- Batch tools
- Token-efficient tools
- Playback controls
Topics: Inferred · not functionally tested
Built with & integrations
Trust & compliance
Indexing history
1What PulseGate has recorded for this listing
- Indexed20 Sep · 21:16 UTCSpotify seen via MCP Registry (official)Source: MCP Registry (official) · Open
Frequently asked questions about spotify-mcp
- What does spotify-mcp do?
- Inferred · not functionally tested: Spotify-mcp focuses on giving AI agents authenticated, efficient access to Spotify music and playback capabilities. It is catalogued under Frameworks & runtimes on PulseGate.
- Who is spotify-mcp for?
- Inferred · not functionally tested: spotify-mcp is an open-source project built for developers building AI agents and MCP integrations.
- Does spotify-mcp have a free plan?
- Basis unknown · not verified: Yes — spotify-mcp is open source under the Open Source license and free to use.
- What platforms does spotify-mcp run on?
- Basis unknown · not verified: spotify-mcp runs on the web, the command line, and API. It can also be self-hosted.
- Is spotify-mcp still active?
- PulseGate's liveness check found it on 24 Sep 2026.
- Who makes spotify-mcp?
- spotify-mcp is developed by Jamie Wilkinson.
- Is spotify-mcp open source?
- Basis unknown · not verified: Yes — spotify-mcp is open source under the Open Source license.
- Does spotify-mcp have an API or integrations?
- Inferred · not functionally tested: Yes — spotify-mcp exposes an MCP server and a public API.
Similar projects
Closest matches by what these projects do