pulsemcp scanned Safe content atomic mcp-remote

Spotify

Spotify MCP server that provides AI assistants with comprehensive music control and discovery capabilities through OAuth 2.1 authentication and Spotify's Web API. Built with TypeScript using Hono and Bun, the implementation features a streamable HTTP transport architecture with session management, rate limiting, and token refresh handling, offering five core tools for searching music catalogs, checking playback status, controlling playback (play/pause/skip/volume/transfer), managing playlists, and handling saved music libraries. The server supports both client credentials for public catalog searches and user authentication for personalized features, making it valuable for building AI music assistants, automated playlist curation, and conversational music discovery workflows that need programmatic access to Spotify's full ecosystem of tracks, albums, artists, and user data.

Cognium trust score

63%

Tier

Scanned

Composite of vulnerability cleanliness, spec conformance, provenance, stability, and usage signals — scanned and weighted by Cognium. Human and agent signals are tracked separately. Last scanned 2026-09-02.

Scan details: Circle-IR · 2026-09-02 · Appeal

View full trust & usage report →

Metadata

Version: 1.0.0
Skill type: atomic
Execution layer: mcp-remote
Category: media
Source: PulseMCP
Repository: github.com/iceener/spotify-streamable-mcp-server
Author type: human
Last scanned: 2026-09-02
Updated: 2026-09-02

View source Find related skills

MCP

Resolve Spotify from your agent

Streamable HTTP transport at https://api.skillsregistry.net/mcp. No auth for read tools. Discovery: .well-known/mcp.json.

One command in your shell — Claude Code wires it up and verifies the connection. Run /mcp in any session to confirm.

claude mcp add --transport http --scope user skillsregistry https://api.skillsregistry.net/mcp

Swap --scope user for --scope project to commit it to .mcp.json.

Your client Same endpoint everywhere; only the config key differs. The full list is in the descriptor.

Claude Desktop · Settings → Connectors → Add custom connector

https://api.skillsregistry.net/mcp

Paste the URL as the connector endpoint. No authentication.

ChatGPT · Settings → Connectors → Create (developer mode) → MCP server URL

https://api.skillsregistry.net/mcp

Authentication: none. Works in chat and deep research — the server exposes the connector search and fetch tools.

Codex CLI · ~/.codex/config.toml

[mcp_servers.skillsregistry]
url = "https://api.skillsregistry.net/mcp"