king-crimson-mcp
Retrieves physical pressings, reissues, and edition details from Discogs.
Provides album search and per-track performer/production credits via MusicBrainz, keyed on MBID.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@king-crimson-mcp What incarnation does Elephant Talk belong to?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
King Crimson Discography MCP Server
日本語版: README.ja.md
An MCP server that surfaces King Crimson record and live-performance data — including a curated incarnation (line-up era) model that shows how each song belongs to specific eras of the band.
What makes this different
Generic MusicBrainz/Discogs MCP servers can already fetch releases, credits, and pressings. This server does that too, but adds two things a band-agnostic discography tool structurally can't have:
A cross-source integration layer keyed on MBID. MusicBrainz, Discogs, Cover Art Archive, and setlist.fm are stitched together so one release-group MBID gets you credits, physical editions, artwork, and live history without re-resolving identities per source.
A King Crimson incarnation model. King Crimson's line-up turned over almost completely, many times, over five decades — the same song can mean a totally different band depending on the year. This server hand-curates eight line-up eras and cross-references every tracked song's live-performance history against them:
Song
Incarnations it appears in
"21st Century Schizoid Man"
Spread across every era — the band's signature
"Starless"
Only the Larks' Tongues era and the Three-drummer era
"Elephant Talk"
Born in the Discipline era, gone by the Three-drummer era
A local, offline-first concert cache. Full concert history (1,200+ shows) is fetched once via
refresh_setlist_cacheand cached as JSON. Every subsequent song/tour/era query reads the cache — instant, and immune to setlist.fm's intermittent rate-limit failures during analysis.Reverse lookup: song → the live albums that captured it, by era. Ask "which live releases contain Red?" and get them grouped by incarnation. It cross-references two things this server already knows — when a song was played (from the setlist cache) and when each official live album was recorded (parsed from its title) — so it answers a question neither MusicBrainz nor Discogs answers directly.
For Red, this surfaces 37 single-show live albums across the Discipline, THRAK, ProjeKcts and Three-drummer eras — and correctly shows none from the 1974 line-up that recorded it, which never played it live (numbers as of this writing; MusicBrainz's catalog can grow).
Related MCP server: spotify-mcp
Tools
Tool | Description |
| MusicBrainz album search → MBIDs |
| Per-track performer/production credits, resolved at the recording level, plus a deduplicated album roster |
| Physical pressings/reissues via Discogs, preferring the exact MusicBrainz→Discogs relation over fuzzy search |
| Cover art via the Cover Art Archive |
| One-page setlist.fm search by venue/city/year (no cache needed) |
| Fetch and cache an artist's complete concert history from setlist.fm |
| A song's live history from the cache: |
| The curated line-up eras — members, instruments, key releases |
| Fetch King Crimson's official live releases from MusicBrainz and cache them, parsing a recording date from each title |
| Find official live releases that captured a song, grouped by incarnation — matches the setlist cache against live-release recording dates |
| Fetch King Crimson's compilations and box sets from Discogs and cache their tracklists |
| List box sets / compilations that contain a given song (from Discogs), with year, format, Discogs URL, and occurrence count |
The incarnation model
Eight line-up eras, split on membership changes:
id | Era | Years |
| In the Court era | 1969 |
| Transitional era | 1970 – Sep 1972 |
| Larks' Tongues era | Oct 1972 – 1974 |
| Discipline era | 1981 – 1984 |
| Double Trio / THRAK era | 1994 – 1996 |
| ProjeKcts / Nuovo Metal era | 1997 – 2003 |
| 40th Anniversary era | 2008 |
| Three-drummer era | 2014 – 2021 |
Boundaries are dates, not just years — 1972 in particular splits into the Islands-era "Earthbound" spring tour (Transitional) and the Wetton-era autumn tour (Larks' Tongues), since the band's membership genuinely changed mid-year.
Line-up eras are a matter of fan interpretation, and this is one reasonable cut, not the only one. The full definition lives in KING_CRIMSON_INCARNATIONS in src/king_crimson_mcp/server.py — edit it (members, key releases, date boundaries) to match your own view; the aggregation logic doesn't need to change.
Song → releases (reverse lookup)
"Which releases have Red on them?" is answered in two complementary ways, because King Crimson's live catalog splits cleanly into single-show albums and multi-show compilations.
Single-show live albums, mapped to eras — song_live_releases
Needs two local caches, built once:
refresh_setlist_cache— every show and what was played (already covered above).refresh_live_releases_cache— King Crimson's official live releases from MusicBrainz, with a recording date parsed out of each title where possible.
Both are one-time builds: the band's history is fixed, so neither cache needs to be rebuilt unless you want to pick up new MusicBrainz entries.
How it works: a song's performance dates come from the setlist cache; each live release carries a recording date parsed from its title (e.g. "Live in Toronto – June 24, 1974"). Where a release's recording date matches a date the song was played, that release is taken to contain the song. This is a straightforward, transparent rule — reliable for single-show live albums.
Known limits (by design): King Crimson has about 187 official live releases, of which only about 87 (as of this writing) have a title MusicBrainz-parseable into a full recording date — that's the range song_live_releases can match with confidence. The other ~100 (box sets, compilations, titles without a date) can't be matched this way; song_live_releases reports exactly how many were skipped in its coverage field rather than silently under-reporting. Excerpt compilations are an edge case too: a song played at a show can, in principle, be matched to that show's release even if the specific release is a highlights disc that omits the track — date-matching can't distinguish "recorded that night" from "included on the disc."
Box sets & compilations, listed — song_box_sets
The multi-show box sets and compilations that song_live_releases can't date-match are covered here, from Discogs. It filters King Crimson's Discogs releases to compilations and box sets (format contains "Comp" or "Box" — which excludes single-show downloads) and lists the ones whose tracklist contains the song: title, year, format, Discogs link, and how many times the song appears on each.
Why no era grouping here: Discogs doesn't structure per-track recording dates, so a box set can't be split into eras the way single-show albums can. song_box_sets therefore lists the box sets containing a song rather than classifying them — era-level precision is song_live_releases's job. Together they cover both halves of the question.
Needs its own one-time cache: run refresh_box_sets_cache (about a minute; ~38 box sets/compilations from Discogs, as of this writing). Requires DISCOGS_TOKEN.
For Red, song_box_sets returns 14 box sets/compilations (the "Collectors' King Crimson" volumes, "1972–1974", the "2015 Japan Tour Box", …), while song_live_releases handles the single-show side.
The honesty of both tools' coverage reporting is the point: results are exactly as complete as the underlying data lets them be, and you (or the calling agent) can see where to dig further instead of getting a silently incomplete answer.
Quick start
Three one-time steps, then it runs inside Claude.
Step 1 — Install uv (one time)
uv is a small tool that can fetch and run this server for you.
macOS / Linux:
curl -LsSf https://astral.sh/uv/install.sh | shWindows (PowerShell):
powershell -c "irm https://astral.sh/uv/install.ps1 | iex"
Close and reopen your terminal afterward. To check it worked:
uv --versionStep 2 — Get your free API keys
This server reads public music databases. Two of them need a free key:
setlist.fm (live performance history) — apply for a key at https://api.setlist.fm/docs/1.0/index.html
Discogs (physical editions) — create a token at Discogs → Settings → Developers → Generate token
You also set a contact email (MCP_CONTACT) — MusicBrainz requires this so
their servers know who's calling. Any email you own is fine.
(MusicBrainz and Cover Art Archive need no key.)
Step 3 — Add it to Claude Desktop
Open Claude Desktop's config file:
macOS:
~/Library/Application Support/Claude/claude_desktop_config.jsonWindows:
%APPDATA%\Claude\claude_desktop_config.json
Add this (fill in your email and keys):
{
"mcpServers": {
"king-crimson": {
"command": "uvx",
"args": ["king-crimson-mcp"],
"env": {
"MCP_CONTACT": "you@example.com",
"SETLISTFM_API_KEY": "your-setlistfm-key",
"DISCOGS_TOKEN": "your-discogs-token"
}
}
}
}Restart Claude Desktop. King Crimson tools will appear automatically — you don't run anything in a terminal yourself.
Step 4 — First use
In Claude, ask something like "Refresh the King Crimson setlist cache" once (it downloads the full concert history, ~40 seconds). After that, try "Show me the performance history of Starless" or "Which incarnations played 21st Century Schizoid Man?"
Troubleshooting
"uvx: command not found" / server won't start in Claude Desktop.
uvisn't installed or isn't on your PATH. Redo Step 1, then fully quit and reopen Claude Desktop. On Windows you may need the full path touvxin thecommandfield.A warning appears if you run it manually in a terminal. Running
uvx king-crimson-mcpdirectly just waits silently for a client — that's normal (it speaks over stdin/stdout). You don't need to run it by hand; Claude Desktop starts and stops it for you. Press Ctrl+C to stop.get_editions/ setlist tools return an error about a missing key. That tool's API key isn't set in your config'senvblock. See Step 2.setlist data looks incomplete for older tours. setlist.fm is user-submitted; some historical shows or songs simply aren't logged there. This is a data limitation, not a bug.
Install from PyPI
For developers — the same package as Quick start above, without the Claude Desktop config:
# run directly without installing (recommended)
uvx king-crimson-mcp
# or install as a persistent tool
pipx install king-crimson-mcp
king-crimson-mcpSecrets (MCP_CONTACT, DISCOGS_TOKEN, SETLISTFM_API_KEY) go either in a .env file in the directory you run the command from, or directly in the Claude Desktop config's env block (see below) — either is read. .env is loaded from the current working directory, since an installed package has no project directory of its own to keep one in.
Setup from source (development)
# Python 3.10+ required (3.12 recommended)
uv venv --python 3.12
source .venv/bin/activate
uv pip install -e .
# configure secrets
cp .env.example .env
# then edit .env.env variables:
MCP_CONTACT— required by MusicBrainz policy; identifies your app to their API via the User-Agent header.DISCOGS_TOKEN— needed forget_editions(Discogs personal access token).SETLISTFM_API_KEY— needed forget_live_history,refresh_setlist_cache, andsong_performance_history.KC_CACHE_DIR— optional; overrides where the setlist cache is written (see below).
Running
# quick tool check via MCP Inspector
mcp dev src/king_crimson_mcp/server.pyRun refresh_setlist_cache once first — it fetches King Crimson's full concert history (~1,200 shows, ~40 seconds) and caches it locally under $XDG_CACHE_HOME/king-crimson-mcp (or ~/.cache/king-crimson-mcp; override with KC_CACHE_DIR) as setlists_<artist_mbid>.json. After that, song_performance_history reads from the cache and returns instantly.
Run refresh_live_releases_cache once as well if you want song_live_releases — it writes live_releases_<artist_mbid>.json alongside the setlist cache, in the same directory. refresh_box_sets_cache similarly writes box_sets_<artist_mbid>.json there, for song_box_sets.
Register with Claude Desktop
Using the published package:
{
"mcpServers": {
"king-crimson": {
"command": "uvx",
"args": ["king-crimson-mcp"],
"env": {
"MCP_CONTACT": "you@example.com",
"DISCOGS_TOKEN": "...",
"SETLISTFM_API_KEY": "..."
}
}
}
}Or, running from a local clone instead (after uv pip install -e ., which installs the same king-crimson-mcp console script into the venv):
{
"mcpServers": {
"king-crimson": {
"command": "/absolute/path/to/.venv/bin/king-crimson-mcp",
"env": { "MCP_CONTACT": "you@example.com" }
}
}
}Secrets can live in .env (in the directory the command is run from) instead of the env block — either is read.
Data sources & attribution
This project is an unofficial client with no affiliation with or endorsement from MusicBrainz, the MetaBrainz Foundation, the Internet Archive, Discogs, or setlist.fm.
MusicBrainz — free, no API key. Requires an identifying User-Agent with contact info (rate limit: 1 req/sec). Data is largely CC0; crediting MusicBrainz in your app is good practice.
refresh_live_releases_cachealso uses this: it lists King Crimson's official live release groups (type=live) — no additional service or key involved.Cover Art Archive — a joint MusicBrainz / Internet Archive project. Images are contributed by individual uploaders; follow the same attribution etiquette as MusicBrainz.
Discogs — requires a personal access token and a unique User-Agent (60 req/min authenticated). Use is subject to the Discogs API terms of service.
song_box_setsuses the same Discogs API asget_editions(no additional service or key).setlist.fm — requires an API key (apply at api.setlist.fm). Any display of setlist.fm data must include an attribution link to the source setlist — every performance returned by this server includes its
urlfor exactly that purpose; surface it wherever you show the data. setlist.fm data is user-submitted, so completeness and accuracy are not guaranteed.
Limitations
setlist.fm data is user-submitted — some shows or songs may be missing or incorrect, especially from older tours.
The incarnation boundaries are one interpretation of King Crimson's line-up history, not an official taxonomy.
Performer credits depend on what MusicBrainz has cataloged for a given release; sparser releases yield sparser credits.
song_live_releasescan only match live releases whose title yields a full recording date (about half of King Crimson's ~187 official live releases); see Song → releases above for what's out of reach and why.song_box_setscan't classify box sets by incarnation — Discogs doesn't structure per-track recording dates, so it lists matching box sets/compilations rather than era-grouping them. A handful of the ~38 compilations it scans are multi-artist collections where King Crimson contributed only one track; these can surface as noise for very common song titles.
License
MIT — see LICENSE.
Available Tools
12 toolsget_artworkA
Get cover art for a release group from the Cover Art Archive.
Args:
mbid: MusicBrainz release-group ID (from search_release).
Returns:
A dict with an images list of {front, back, thumbnails, url}.
Inputs: mbid (required).
get_creditsA
Get performer and production credits for an album (release group).
Returns the headline artist credit and release-group relationships, plus per-track performer credits resolved from the recording level in MusicBrainz (individual musicians and their instruments), and a deduplicated album roster.
Args:
mbid: MusicBrainz release-group ID (from search_release).
release_mbid: Optional specific release (edition) to read track credits
from. If omitted, a representative official release is chosen.
Returns: A dict with title, artist_credit, release_used, performers (roster), tracks (per-track credits), relations, and external_links.
Inputs: mbid (required), release_mbid.
get_editionsA
List physical editions/pressings of an album via Discogs.
Resolves the Discogs master for the album -- preferring the discogs
relation stored on the MusicBrainz release group (exact match), and
falling back to a Discogs title/artist search when no such relation
exists. Then lists the master's versions (pressings, reissues, box sets)
with format, country, year and community stats. Requires DISCOGS_TOKEN.
Args:
mbid: MusicBrainz release-group ID (from search_release).
max_versions: Max editions to return (1-50).
Returns:
A dict with master info and a versions list. match_method
reports how the master was resolved ("musicbrainz-relation" or
"discogs-search").
Inputs: mbid (required), max_versions.
get_incarnationsA
List King Crimson's line-up eras (incarnations): id, name, date range, members with instruments, key releases, and a one-line note.
Use this to look up who played in a given era. Song analysis
(song_performance_history) reports per-era counts under by_incarnation
keyed by the same ids/names, so this is the reference for those.
Returns:
A dict with an incarnations list.
Inputs: no named parameters.
get_live_historyA
Search live performance history / setlists via setlist.fm.
Useful for King Crimson given their extensive touring: cross-reference official live albums against what was actually played on a given tour. Requires SETLISTFM_API_KEY.
Args: query: Optional venue or city keyword to narrow the search. artist: Artist name. Defaults to "King Crimson". year: Optional year filter. limit: Max setlists to return (1-20; one API page).
Returns:
A dict with a setlists list of {date, venue, city, country, songs}.
Inputs: year, limit, query, artist.
refresh_box_sets_cacheA
Fetch King Crimson's compilations and box sets from Discogs and cache their tracklists, so song_box_sets can list which box sets contain a song.
Filters the artist's Discogs releases to Main-role compilations/box sets (format contains "Comp" or "Box"), which excludes single-show live downloads (those are covered by song_live_releases). Requires DISCOGS_TOKEN.
Returns: A summary: releases scanned, box sets cached, and the cache path.
Inputs: force, artist_mbid, discogs_artist_id.
refresh_live_releases_cacheA
Fetch King Crimson's official live releases from MusicBrainz and cache them locally, parsing a recording date out of each title where possible.
Used by song_live_releases to map songs to the live albums that captured them. King Crimson's live catalog is fixed, so this rarely needs re-running. Requires MCP_CONTACT (MusicBrainz User-Agent policy).
Args: artist_mbid: MusicBrainz artist MBID. Defaults to King Crimson. max_pages: Safety cap on pages to fetch (100 release groups/page). max_retries: Retries per page on transient error (e.g. MusicBrainz's intermittent 503s) before giving up. force: Re-fetch even if a cache file already exists.
Returns: A summary: totals, how many titles yielded a full recording date, and the cache path.
Inputs: force, max_pages, artist_mbid, max_retries.
refresh_setlist_cacheA
Fetch an artist's complete concert history from setlist.fm and cache it locally as JSON, so song/tour analysis runs instantly and offline.
Robust against setlist.fm's intermittent failures: each page is retried with backoff, and any page that still fails is recorded rather than aborting the whole run. King Crimson's history is fixed (band ended 2021), so this rarely needs re-running. Requires SETLISTFM_API_KEY.
Args: artist_mbid: MusicBrainz artist MBID. Defaults to King Crimson. max_pages: Safety cap on pages to fetch (20 shows/page). max_retries: Retries per page on transient error before recording it failed. force: Re-fetch even if a cache file already exists.
Returns: A summary dict (not the setlists themselves): counts, coverage, any failed pages, date range, and the cache file path.
Inputs: force, max_pages, artist_mbid, max_retries.
search_releaseA
Search MusicBrainz for release groups (albums) matching a query.
A "release group" is the canonical album, independent of its many physical
editions -- the right granularity for browsing a discography. Use the
returned mbid with the other tools.
Args: query: Free-text album title or keywords (e.g. "Red", "Larks' Tongues"). artist: Restrict to this artist. Defaults to "King Crimson". limit: Max results (1-25).
Returns:
A dict with a results list of {mbid, title, primary_type,
first_release_date, disambiguation}.
Inputs: query (required), limit, artist.
song_box_setsA
List King Crimson box sets / compilations that contain a given song (from Discogs). Complements song_live_releases: that tool maps single-show live albums to eras; this one covers the multi-show box sets and comps that date-matching can't resolve.
Run refresh_box_sets_cache first.
Args: song: Song title (e.g. "Red"). artist_mbid: MusicBrainz artist MBID (cache key). Defaults to King Crimson. match: "exact" (case-insensitive full track title) or "contains".
Returns: The box sets/compilations whose tracklist includes the song, with title, year, format, Discogs URL, and how many times the song appears on each.
Inputs: song (required), match, artist_mbid.
song_live_releasesA
Find official live releases that captured a given song, grouped by incarnation (line-up era).
How it works: the song's performance dates come from the setlist cache; live releases carry a recording date parsed from their title. Where a release's recording date matches a date the song was played, that release is taken to contain the song. This is authoritative for single-show live albums; excerpt compilations are an edge case.
Requires both caches: run refresh_setlist_cache and refresh_live_releases_cache first.
Args: song: Song title (e.g. "Red"). artist_mbid: MusicBrainz artist MBID. Defaults to King Crimson. match: "exact" (case-insensitive full title) or "contains" (substring).
Returns: by_incarnation groupings of matched live releases, plus a coverage note stating how many live releases could not be matched by date (box sets, compilations, undated titles) so the caller can decide to search further.
Inputs: song (required), match, artist_mbid.
song_performance_historyA
Trace how often and when a song was played live, from the local setlist cache. Run refresh_setlist_cache first. Aggregates by year and by tour so a song's life across decades and line-ups is visible at a glance.
Args: song: Song title to trace (e.g. "Starless", "21st Century Schizoid Man"). artist_mbid: MusicBrainz artist MBID. Defaults to King Crimson. match: "exact" (case-insensitive full title) or "contains" (substring).
Returns: A dict with cache_info, performance_count, first/last performance, by_year and by_tour breakdowns, and the list of performances.
Inputs: song (required), match, artist_mbid.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 12 tools
Most tools target distinct resources (albums, credits, editions, artwork, setlists, incarnations, song analyses), and descriptions clearly delineate boundaries. The three refresh_* tools and three song_* tools are each distinct by domain, though get_live_history and song_performance_history both touch live performance data and could be briefly confused before reading details.
There are multiple naming conventions: get_* for direct lookups, search_release for searching, refresh_* for cache updates, and song_* for song-specific analyses (which drop the leading verb). While each family is internally consistent, the mix of verb-first and noun-first patterns across the tool set is noticeable and not fully uniform.
Twelve tools is well within the ideal range and each appears justified for the server's purpose of King Crimson discography and live-performance research. The count covers exploration, analysis, and necessary cache maintenance without feeling bloated or sparse.
The tool surface covers the core workflows: searching albums, retrieving credits, editions, artwork, live history, incarnations, and per-song analyses across live releases and box sets. Minor gaps exist—there's no direct song search tool, and the song analysis tools depend on running refresh_* commands first—but these are workable given clear prerequisites and the ability to discover songs via get_credits.
Maintenance
Related MCP Connectors
MCP server for Producer/Riffusion AI music generation
MCP server for progressive tool usage at any scale (see https://klavis.ai)
MCP server for RiverScript, an AI transcription platform - fetches transcripts shared via a link.
An MCP server that provides congressional transcripts
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceAn MCP server for Spotify control and synchronized lyrics retrieval that enables playback management, queue navigation, and music search capabilities. It also features perception tools for real-time track analysis, including BPM, key detection, and timestamped lyrics.3Apache 2.0
- AlicenseCqualityDmaintenanceThis is a 93-tool Spotify MCP server for Claude, Cursor, and any MCP client. Smart shuffle, vibe analysis, natural language search, artist networks, and more.9310MIT
- AlicenseNot gradedqualityBmaintenanceSearch, rate and organise your Discogs collection, wantlist and folders from an AI assistant. Self-hosted: deploy your own copy to Cloudflare Workers with the Deploy to Cloudflare button in the README. Not affiliated with Discogs.20MIT
- FlicenseBqualityDmaintenanceMCP server for managing Cassette music releases and Creator clips through AI assistants via personal access tokens.285 npm-