What is spotify-mcp CLAUDE.md?

A set of project instructions for developing the spotify-mcp server, which connects coding tools to Spotify. It documents setup commands, required Spotify credentials, testing, type checks, and Git rules.

Use it when setting up, testing, type-checking, configuring, or committing changes to the spotify-mcp server.

It gives contributors one place to find the commands and checks expected for this codebase. This reduces setup mistakes and helps catch problems before commits.

How jamiew/spotify-mcp configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to jamiew/spotify-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/jamiew/spotify-mcp/main/CLAUDE.md

Clone the repo

git clone --depth 1 https://github.com/jamiew/spotify-mcp

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/jamiew/spotify-mcp/claude-md/github.svg)](https://agentmods.dev/instructions/jamiew/spotify-mcp/claude-md)

Your own site

<a href="https://agentmods.dev/instructions/jamiew/spotify-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/jamiew/spotify-mcp/claude-md/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/jamiew/spotify-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/jamiew/spotify-mcp/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 2,803 This file is loaded in full into every session.

When invoked 2,803 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin fork From a forked repository.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.02803	$0.02803
Opus 5.5	$0.01121	$0.01121
Sonnet 5.5	$0.00561	$0.00561
Haiku 4.5	$0.00280	$0.00280

Measured 5d ago against content hash f107e926dd82, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

spotify-mcp CLAUDE.md scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 5d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

CLAUDE.md · 201 lines

How it starts

The opening of the file, as written. The whole thing — 201 lines — stays where its author put it; the contents beside it link to each section on GitHub.

CLAUDE.md

This file provides essential guidance for working with the Spotify MCP server codebase.

Essential Commands

Development

uv run spotify-mcp - Start the MCP server (local alias; the package publishes as spotify-mcp-jamiew, so end users run uvx spotify-mcp-jamiew)
uv sync - Sync dependencies
uv run pytest - Run all tests (must pass before commits)
uv run mypy src/ - Type checking (must pass before commits)
- Optional speedup on mypy 2.x: uv run mypy src/ --num-workers 4 (parallel checking)
uv run ruff check src/ tests/ and uv run ruff format --check src/ tests/ - Lint and format (CI gate)
uv run bandit -r src/ - Security lint (CI gate)

Environment Setup

Required environment variables:

SPOTIFY_CLIENT_ID - Spotify API Client ID
SPOTIFY_CLIENT_SECRET - Spotify API Client Secret
SPOTIFY_REDIRECT_URI - OAuth redirect URI registered in the Spotify app (http://127.0.0.1:8888)

Three-tier configuration (highest priority first):

Environment variables (for production/MCP usage)
.env file (for local development)
pyproject.toml defaults (fallback - edit [tool.spotify-mcp.env] section)

Git Workflow

Quality Gates: Before any commit, ALWAYS run the same checks CI runs:

uv run mypy src/ - Type checking must pass
uv run pytest - All tests must pass
uv run ruff check src/ tests/ and uv run ruff format --check src/ tests/ - Lint must pass
uv run bandit -r src/ - Security lint must pass

Commit Message Format:

Brief description of change

Detailed explanation of what and why.

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <[email protected]>

Releasing

Publishing is fully automated via OIDC trusted publishing — no tokens stored anywhere.

Bump version in pyproject.toml and both versions in server.json (tests/test_packaging.py fails if they differ), commit, and create a GitHub release for tag vX.Y.Z (the /release skill or release.sh does the tag + gh release create).
The release: published event triggers .github/workflows/publish.yml, which tests → checks the tag matches the package version → builds → publishes to PyPI (pypa/gh-action-pypi-publish, OIDC) → publishes server.json to the MCP Registry (mcp-publisher login github-oidc). A manual run of the workflow skips the PyPI upload if that version already exists, so it can retry a failed registry publish.

Read the full file on GitHub · 201 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

5d ago Changed · +8 lines · +207 tokens per session f107e926dd82
1mo ago Changed · +42 lines · +646 tokens per session 625fc427b140
1mo ago Changed · -1 tokens per session fcfef5c70d96
1mo ago Changed · +7 lines · +105 tokens per session 822d59162a49
2mo ago First seen · 144 lines · 1,846 tokens per session scan A c58678e6a1a9

Subscribe to this mod's changes

spotify-mcp CLAUDE.md is an instructions file published in the GitHub repository jamiew/spotify-mcp (12 stars, last pushed 5d ago), licensed MIT. It adds 2,803 tokens to every session, about $0.0112 per session on Opus 5.5. A static security scan graded it A with 0 findings. It comes from a forked repository.

mcp spotify

spotify-mcp CLAUDE.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
spotify-mcp CLAUDE.mdjamiew/spotify-mcp	Instructions file	12	5d ago	MIT	A	2,803	Claude Code
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	yesterday	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	yesterday	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

spotify-mcp: Instructions file for Claude Code