Skip to main content
Glama
enesjakozh
boristopalov

Spotify MCP Server

by boristopalov
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

spotify-mcp MCP サーバー

鍛冶屋のバッジ

ClaudeとSpotifyを接続するMCPプロジェクト。spotipy -devのAPIをベースに構築されています。

特徴

  • 再生を開始、一時停止、スキップする

  • トラック/アルバム/アーティスト/プレイリストを検索

  • トラック/アルバム/アーティスト/プレイリストに関する情報を取得する

  • Spotifyキューを管理する

Related MCP server: Spotify MCP Server

デモ

音声をオンにしてください

構成

Spotify APIキーの取得

developer.spotify.comでアカウントを作成します。ダッシュボードに移動します。redirect_uri をhttp://localhost:8888にしてアプリを作成します。（任意のポートを選択できますが、http と localhost を使用する必要があります）。「使用する API」を「Web Playback SDK」に設定しました。

このプロジェクトをローカルで実行する

このプロジェクトはまだ一時的な環境（ uvx使用など）向けに設定されていません。このリポジトリをクローンしてローカルで実行してください。

git clone https://github.com/varunneal/spotify-mcp.git

このツールを MCP サーバーとして追加します。

MacOS の場合: ~/Library/Application\ Support/Claude/claude_desktop_config.json Windows の場合: %APPDATA%/Claude/claude_desktop_config.json

"spotify": {
    "command": "uv",
    "args": [
      "--directory",
      "/path/to/spotify_mcp",
      "run",
      "spotify-mcp"
    ],
    "env": {
      "SPOTIFY_CLIENT_ID": YOUR_CLIENT_ID,
      "SPOTIFY_CLIENT_SECRET": YOUR_CLIENT_SECRET,
      "SPOTIFY_REDIRECT_URI": "http://localhost:8888"
    }
  }

トラブルシューティング

このMCPが動作しない場合は、問題を報告してください。以下にヒントをいくつか示します。

  1. uvが更新されていることを確認してください。バージョン>=0.54推奨します。

  2. claude にプロジェクトの実行権限があることを確認します: chmod -R 755 。

  3. Spotify Premium があることを確認します (開発者 API を実行するために必要)。

やるべきこと

残念ながら、Spotify API から多くの便利な機能が廃止されました。新しい機能のほとんどは、比較的マイナーなもの、またはプロジェクトの健全性に関するものです。

  • テスト。

  • プレイリストを管理するための API サポートを追加します。

  • ページ分割された検索結果/プレイリスト/アルバムの API サポートを追加します。

展開

（やること）

建築と出版

配布用のパッケージを準備するには:

  1. 依存関係を同期し、ロックファイルを更新します。

uv sync

  1. パッケージディストリビューションをビルドします。

uv build

これにより、 dist/ディレクトリにソースとホイールのディストリビューションが作成されます。

  1. PyPI に公開:

uv publish

注: 環境変数またはコマンド フラグを使用して PyPI 資格情報を設定する必要があります。

  • トークン: --tokenまたはUV_PUBLISH_TOKEN

  • またはユーザー名/パスワード: --username / UV_PUBLISH_USERNAMEおよび--password / UV_PUBLISH_PASSWORD

デバッグ

MCPサーバーはstdio経由で実行されるため、デバッグが困難になる場合があります。最適なデバッグ環境を実現するには、 MCP Inspectorの使用を強くお勧めします。

次のコマンドを使用して、 npm経由で MCP Inspector を起動できます。

npx @modelcontextprotocol/inspector uv --directory /Users/varun/Documents/Python/spotify_mcp run spotify-mcp

起動すると、ブラウザでアクセスしてデバッグを開始できる URL がインスペクタに表示されます。

Available Tools

4 tools
SpotifyGetInfoC

Get detailed information about a Spotify item (track, album, artist, or playlist).

ParametersJSON Schema
NameRequiredDescriptionDefault
item_idYesID of the item to get information about
qtypeNoType of item: 'track', 'album', 'artist', or 'playlist'. If 'playlist' or 'album', returns its tracks. If 'artist',returns albums and top tracks.track

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action ('Get detailed information') but doesn't cover critical aspects like authentication requirements, rate limits, error handling, or what 'detailed information' entails (e.g., fields returned, pagination). This leaves significant gaps for an agent to understand operational constraints.

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

Conciseness5/5

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

The description is a single, efficient sentence that directly states the tool's purpose without redundancy. It's front-loaded with the core action and resource, making it easy to parse quickly. There's no wasted verbiage or unnecessary elaboration.

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

Completeness2/5

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

Given the complexity of retrieving varied Spotify item types and the lack of annotations and output schema, the description is insufficient. It doesn't explain what 'detailed information' includes (e.g., track metadata, artist albums), how results are structured, or any behavioral traits like authentication needs. For a tool with no structured safety or output guidance, more context is needed.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents both parameters thoroughly (item_id and qtype with default and effects). The description doesn't add any meaningful semantic details beyond what's in the schema, such as format examples for item_id or nuances in qtype behavior. Baseline 3 is appropriate as the schema does the heavy lifting.

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

Purpose4/5

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

The description clearly states the verb ('Get') and resource ('detailed information about a Spotify item'), specifying the item types (track, album, artist, or playlist). However, it doesn't explicitly differentiate from sibling tools like SpotifySearch, which might also retrieve information but through search queries rather than direct ID lookup.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives like SpotifySearch or other siblings. It lacks context about prerequisites (e.g., authentication), exclusions, or specific scenarios where this direct ID lookup is preferred over search-based methods.

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

SpotifyPlaybackB

Manages the current playback with the following actions: - get: Get information about user's current track. - start: Starts of resumes playback. - pause: Pauses current playback. - skip: Skips current track.

ParametersJSON Schema
NameRequiredDescriptionDefault
actionYesAction to perform: 'get', 'start', 'pause' or 'skip'.
track_idNoSpecifies track to play for 'start' action. If omitted, resumes current playback.
num_skipsNoNumber of tracks to skip for `skip` action.

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While it describes what each action does at a basic level, it lacks important behavioral details like authentication requirements, rate limits, error conditions, or what happens during concurrent playback management. The description doesn't contradict any annotations since none exist.

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

Conciseness4/5

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

The description is efficiently structured with a clear opening statement followed by bullet points for each action. Each bullet is concise and directly relevant. However, the repetition of the opening sentence in the schema description suggests some redundancy that could be eliminated.

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

Completeness3/5

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

For a playback management tool with 3 parameters and no output schema, the description provides adequate basic information but lacks completeness. Without annotations or output schema, it should ideally cover more behavioral aspects like response format, error handling, or prerequisites. The description meets minimum requirements but leaves gaps.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents all three parameters thoroughly. The description lists the four action types but doesn't add meaningful parameter semantics beyond what's in the schema. The baseline of 3 is appropriate when the schema does the heavy lifting.

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

Purpose4/5

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

The description clearly states the tool's purpose as managing current playback with four specific actions (get, start, pause, skip), providing a verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like SpotifyQueue or SpotifySearch, which likely handle different aspects of Spotify functionality.

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

Usage Guidelines3/5

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

The description implies usage context through action descriptions (e.g., 'get' for track information, 'skip' for skipping tracks), but doesn't provide explicit guidance on when to use this tool versus alternatives like SpotifyQueue or SpotifySearch. No when-not scenarios or clear alternatives are mentioned.

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

SpotifyQueueB

Manage the playback queue - get the queue or add tracks.

ParametersJSON Schema
NameRequiredDescriptionDefault
actionYesAction to perform: 'add' or 'get'.
track_idNoTrack ID to add to queue (required for add action)

TDQS

B3.4/5.0
Behavior2/5

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

No annotations exist, so the description bears full responsibility. It fails to disclose behavior such as whether adding a track requires an active device, if the queue is appended or overwritten, or what errors occur. Minimal behavioral detail beyond the schema.

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

Conciseness5/5

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

Single, concise sentence that immediately communicates the tool's purpose. No superfluous words, front-loads the resource and actions.

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

Completeness4/5

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

For a simple tool with two parameters and two actions, the description adequately covers purpose. It lacks details on return values or error cases but is sufficient for basic usage given no output schema and limited complexity.

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

Parameters3/5

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

Schema coverage is 100% with parameter descriptions. The description adds marginal value by linking 'add tracks' to the action parameter and implying track_id for add. Baseline score is appropriate as schema handles semantics.

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

Purpose5/5

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

The description clearly states the tool manages the playback queue with two specific actions: get or add tracks. It distinguishes itself from sibling tools like SpotifyPlayback by focusing on queue management.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives like SpotifyPlayback for control operations. The description simply lists actions without context on prerequisites or typical use cases.

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

SpotifySearchB

Search for tracks, albums, artists, or playlists on Spotify.

ParametersJSON Schema
NameRequiredDescriptionDefault
queryYesquery term
qtypeNoType of items to search for (track, album, artist, playlist, or comma-separated combination)track
limitNoMaximum number of items to return

TDQS

B3.4/5.0
Behavior2/5

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

No annotations provided, so description carries burden. It mentions search types and parameters but omits behavior like response structure, pagination, error handling, auth needs, or rate limits.

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

Conciseness5/5

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

Single clear sentence, front-loaded with action verb. No wasted words.

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

Completeness2/5

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

Given 3 parameters, no output schema, and no annotations, the description is too brief. Lacks guidance on output format, pagination, or effective usage compared to sibling tools.

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

Parameters3/5

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

Schema has 100% coverage with descriptions for all 3 parameters. Description adds minimal context beyond schema (e.g., hinting at qtype values already documented). Baseline score of 3 is appropriate.

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

Purpose5/5

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

Description clearly states it searches for tracks, albums, artists, or playlists on Spotify. Distinct from sibling tools like SpotifyGetInfo (specific item info), SpotifyPlayback (playback control), SpotifyQueue (queue management).

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

Usage Guidelines3/5

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

Description implies usage for searching Spotify content, but no explicit when-to-use vs alternatives, no when-not or exclusions provided.

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.

  1. 4 tool updatesv1.0.0
    • ChangedSpotifyGetInfo2 fields changed
      • addedInput schema / description
        Added value: +"Get detailed information about a Spotify item (track, album, artist, or playlist)."
      • addedInput schema / title
        Added value: +"GetInfo"
    • ChangedSpotifyPlayback2 fields changed
      • addedInput schema / description
        Added value: +"Manages the current playback with the following actions:\n- get: Get information about user's current track.\n- start: Starts of resumes playback.\n- pause: Pauses current playback.\n- skip: Skips current track."
      • addedInput schema / title
        Added value: +"Playback"
    • ChangedSpotifyQueue2 fields changed
      • addedInput schema / description
        Added value: +"Manage the playback queue - get the queue or add tracks."
      • addedInput schema / title
        Added value: +"Queue"
    • ChangedSpotifySearch2 fields changed
      • addedInput schema / description
        Added value: +"Search for tracks, albums, artists, or playlists on Spotify."
      • addedInput schema / title
        Added value: +"Search"
  2. 4 tool updates
    • First observedSpotifyGetInfo
    • First observedSpotifyPlayback
    • First observedSpotifyQueue
    • First observedSpotifySearch
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

A3.5/5.0

Scored across 4 tools

Disambiguation5/5

Each tool has a clearly distinct purpose with no overlap: GetInfo retrieves metadata, Playback controls active listening, Queue manages upcoming tracks, and Search finds new content. The separation between Playback (current track control) and Queue (future track management) is particularly well-defined.

Naming Consistency5/5

All tools follow a perfect 'Spotify[Action]' naming pattern with consistent PascalCase throughout. The pattern is immediately recognizable and predictable across all four tools.

Tool Count5/5

Four tools is ideal for this music streaming domain - it covers the essential workflows (discovery, playback control, queue management, and information lookup) without being overwhelming or sparse. Each tool earns its place in the set.

Completeness4/5

The toolset covers core Spotify functionality well with only minor gaps. Notable missing operations include playlist/library management (saving/removing tracks), volume control, and seeking within tracks, but the provided tools enable basic listening workflows.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers