de en es ja ko ru zh

Spotify MCP Server

Name: Spotify MCP Server
Author: hrishi0102

by hrishi0102

Overview Schema Source Related Servers Discussions Admin

JavaScript

Local

Spotify MCP-Server

Ein einfacher Model Context Protocol (MCP)-Server, der die Interaktion mit Spotify über Claude ermöglicht. Dieser Server ermöglicht es Claude, über Ihr Spotify-Konto nach Songs zu suchen, Playlists zu erstellen, Empfehlungen zu erhalten und vieles mehr.

Merkmale

Suche nach Titeln auf Spotify
Ihr Spotify-Profil anzeigen
Erstellen Sie Wiedergabelisten
Titel zu Wiedergabelisten hinzufügen
Erhalten Sie personalisierte Musikempfehlungen

Related MCP server: Spotify MCP Server

Verfügbare Tools

Werkzeugname	Beschreibung
`set-spotify-credentials`	Legen Sie Ihre Spotify-Authentifizierungsdaten fest
`check-credentials-status`	Überprüfen Sie, ob Ihre Anmeldeinformationen gültig sind und wer angemeldet ist
`search-tracks`	Suchen Sie nach Titeln nach Name, Interpret oder Schlüsselwörtern
`get-current-user`	Holen Sie sich Ihre Spotify-Profilinformationen
`create-playlist`	Erstellen Sie eine neue Playlist in Ihrem Konto
`add-tracks-to-playlist`	Titel zu einer vorhandenen Playlist hinzufügen
`get-recommendations`	Erhalten Sie Empfehlungen basierend auf Seed-Tracks

Installationsanweisungen

1. Voraussetzungen

Node.js v16 oder höher
npm
Ein Spotify-Konto
Eine registrierte Spotify-Entwickleranwendung

2. Erstellen Sie eine Spotify-Entwickler-App

Gehen Sie zum Spotify Developer Dashboard
Melden Sie sich mit Ihrem Spotify-Konto an
Klicken Sie auf „App erstellen“.
Geben Sie den App-Namen und die Beschreibung ein
Fügen Sie http://localhost:8888/callback als Umleitungs-URI hinzu
Notieren Sie Ihre Client-ID und Ihr Client-Geheimnis

3. Installieren Sie das Projekt

# Clone or download the project first
cd spotify-mcp-server

# Install dependencies
npm install

4. Holen Sie sich Ihre Spotify-Token

Bearbeiten Sie die Datei spotify-auth.js um Ihre Client-ID und Ihr Client-Geheimnis einzuschließen:

// Replace these with your Spotify app credentials
const CLIENT_ID = "your_client_id_here";
const CLIENT_SECRET = "your_client_secret_here";

Führen Sie dann das Authentifizierungsskript aus:

node spotify-auth.js

Dies wird:

Öffnen Sie eine URL in Ihrem Browser
Fordern Sie Sie auf, sich bei Spotify anzumelden
Bitten Sie um Ihre Erlaubnis, auf Ihr Konto zuzugreifen
Speichern Sie die Token in secrets.json

5. Erstellen Sie den MCP-Server

npm run build

6. Konfigurieren Sie Claude Desktop

Bearbeiten Sie Ihre Claude Desktop-Konfigurationsdatei:

Unter macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Unter Windows: %APPDATA%\Claude\claude_desktop_config.json

Fügen Sie die folgende Konfiguration hinzu:

{
  "mcpServers": {
    "spotify": {
      "command": "node",
      "args": ["/full/path/to/spotify-mcp-server/build/spotify-mcp-server.js"]
    }
  }
}

Ersetzen Sie /full/path/to/spotify-mcp-server durch den tatsächlichen Pfad zu Ihrem Projektverzeichnis.

7. Starten Sie Claude Desktop neu

Schließen Sie Claude Desktop und öffnen Sie es erneut, um die neue Konfiguration zu laden.

Verwendung

Wenn Sie eine Unterhaltung mit Claude beginnen, müssen Sie zunächst Ihre Spotify-Anmeldeinformationen festlegen:

Schauen Sie sich Ihre secrets.json -Datei an, um Ihre Anmeldeinformationen zu erhalten
Verwenden Sie das Tool set-spotify-credentials zur Authentifizierung
Dann nutzen Sie eines der anderen Spotify-Tools

Beispiel-Eingabeaufforderungen

Einrichten der Anmeldeinformationen

I want to connect to my Spotify account. Here are my credentials from secrets.json:

Tool: set-spotify-credentials
Parameters:
{
  "clientId": "your_client_id",
  "clientSecret": "your_client_secret",
  "accessToken": "your_access_token",
  "refreshToken": "your_refresh_token"
}

Grundlegende Befehle

Überprüfen Sie Ihr Konto:

Can you check who I'm logged in as on Spotify?

Tool: get-current-user
Parameters: {}

Suche nach Titeln:

Search for songs by Weekend

Tool: search-tracks
Parameters:
{
  "query": "Taylor Swift",
  "limit": 5
}

Erstellen Sie eine Wiedergabeliste:

Create a new playlist called "My Pretty pretty girlfriend"

Tool: create-playlist
Parameters:
{
  "name": "My Pretty pretty girlfriend",
  "description": "For my girlfriend. Created with Claude and the Spotify MCP server"
}

Mehrstufige Aufgaben

Erstellen einer Playlist mit Songs:

I want to create a workout playlist with energetic songs. First, search for some high-energy songs. Then create a playlist called "Workout Mix" and add those songs to it.

Empfehlungen basierend auf Favoriten erhalten:

I like the song "Blinding Lights" by The Weeknd. Can you search for it, then find similar songs, and create a playlist with those recommendations?

Fehlerbehebung

Fehler: Kein Zugriffstoken verfügbar : Sie müssen Ihre Anmeldeinformationen zuerst mit dem Tool set-spotify-credentials festlegen.
Authentifizierungsfehler : Ihre Token sind möglicherweise abgelaufen. Führen Sie das Authentifizierungsskript erneut aus, um neue Token zu erhalten.
Ungültige Anmeldeinformationen : Überprüfen Sie noch einmal, ob Sie die richtige Client-ID und das richtige Client-Geheimnis verwenden.

Hinweise

Der Server speichert Anmeldeinformationen nur im Speicher
Sie müssen jedes Mal Anmeldeinformationen festlegen, wenn Sie eine neue Konversation beginnen
Wenn Claude Desktop neu gestartet wird, müssen Sie die Anmeldeinformationen erneut festlegen

Available Tools

7 tools

add-tracks-to-playlistD

Name	Required	Description	Default
`playlistId`	Yes	The Spotify playlist ID
`trackUris`	Yes	Array of Spotify track URIs to add

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

check-credentials-statusD

Name	Required	Description	Default
No parameters

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

create-playlistD

Name	Required	Description	Default
`description`	No	Description of the playlist
`name`	Yes	Name of the playlist

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get-current-userD

Name	Required	Description	Default
No parameters

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get-recommendationsD

Name	Required	Description	Default
`limit`	No	Number of recommendations to return
`seedTracks`	Yes	Spotify track IDs to use as seeds (max 5)

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

search-tracksD

Name	Required	Description	Default
`limit`	No	Number of results to return
`query`	Yes	Search query for tracks

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

set-spotify-credentialsD

Name	Required	Description
`accessToken`	Yes	The Spotify Access Token
`clientId`	Yes	The Spotify Client ID
`clientSecret`	Yes	The Spotify Client Secret
`refreshToken`	Yes	The Spotify Refresh Token

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

7 tool updatesv1.0.0Apr 9, 2025
- First observedadd-tracks-to-playlist
- First observedcheck-credentials-status
- First observedcreate-playlist
- First observedget-current-user
- First observedget-recommendations
- First observedsearch-tracks
- First observedset-spotify-credentials

Deploy Server

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

D1.8/5.0

Scored 2026-04-18 10:35 across 7 tools

Disambiguation4/5

Most tools have distinct purposes targeting different Spotify resources like playlists, user info, recommendations, and tracks, but 'add-tracks-to-playlist' and 'create-playlist' could be confused if an agent needs to both create and populate a playlist in one operation. The lack of descriptions increases minor ambiguity.

Naming Consistency3/5

The naming uses a mix of verb-noun patterns (e.g., 'create-playlist', 'search-tracks') and more descriptive phrases (e.g., 'check-credentials-status', 'set-spotify-credentials'), with all tools using kebab-case. This is readable but lacks a strict, predictable convention across all tools.

Tool Count5/5

With 7 tools, this server is well-scoped for a Spotify integration, covering core functionalities like user management, playlist operations, search, and recommendations without being overwhelming or too sparse.

Completeness3/5

The toolset covers key Spotify operations like user info, search, recommendations, and playlist management, but lacks update or delete operations for playlists and tracks, and missing tools for managing playback or albums creates notable gaps in a full music streaming workflow.

Maintenance

ActivityInactive

ResponsivenessNo recent community issues

Resources

Related MCP Connectors

platform7n
tech.p7n
Connect Claude to your Platform7n workspaces: chat, links, work and decks. One-click OAuth.
Communication Project Management Workplace & Productivity
2
https://api.p7n.tech/mcp
podpast
io.github.tomdoeswork
Search and ask the podcasts you follow inside Claude, with the exact quote and timestamp.
Entertainment & Media Search
2
https://api.podpast.ai/mcp
memol
app.memol
Search, read, create and edit your Memol notes from Claude. Team note-taking with AI search.
Note Taking Search
2
https://memol.app/api/mcp
Fathom MCP Server
io.github.agencyenterprise
Connect Claude to Fathom meeting recordings, transcripts, and summaries
Communication App Automation Search
216
https://fathom-mcp-server.com/mcp

Related MCP Servers

Spotify MCP Server
Entertainment & Media App Automation
Naunau75
F
license
Not graded
quality
D
maintenance
Connects Claude with Spotify to control playback, search music, get track information, and manage the queue through conversation.
Updated 2 years ago (2025-04-02 09:27 UTC)
1
-
Spotify MCP Server
Entertainment & Media API Testing
g2dgaming
F
license
A
quality
D
maintenance
Connects Claude with Spotify, allowing users to control playback, search for music, get track/artist information, and manage the queue via the Spotify API.
Updated a year ago (2025-06-02 17:27 UTC)
5
1
-
Spotify MCP Server
Entertainment & Media Search App Automation
lauechlo
A
license
Not graded
quality
Not graded
maintenance
Connects Claude to Spotify for music discovery, playlist creation, and collection analysis through natural language. Enables searching songs, analyzing music diversity, creating playlists, and getting recommendations using Spotify's API.
Updated a year ago (2025-10-27 02:06 UTC)
-
MCP Spotify AI Assistant
Entertainment & Media App Automation
iankan04
A
license
Not graded
quality
D
maintenance
Enables Claude to control Spotify features including playback control, playlist management, search, and accessing user's listening history and preferences through the Spotify API.
Updated a year ago (2025-06-20 05:49 UTC)
1
ISC

Spotify MCP-Server

Merkmale

Verfügbare Tools

Installationsanweisungen

1. Voraussetzungen

2. Erstellen Sie eine Spotify-Entwickler-App

3. Installieren Sie das Projekt

4. Holen Sie sich Ihre Spotify-Token

5. Erstellen Sie den MCP-Server

6. Konfigurieren Sie Claude Desktop

7. Starten Sie Claude Desktop neu

Verwendung

Beispiel-Eingabeaufforderungen

Einrichten der Anmeldeinformationen

Grundlegende Befehle

Mehrstufige Aufgaben

Fehlerbehebung

Hinweise

Available Tools

Tool Schema Changelog

Maintenance

Resources

Related MCP Connectors

Related MCP Servers

Appeared in Searches