Setlist Mcp
Wire setlist.fm concert history into your agent when you are building music apps, tour trackers, or research workflows without hand-scraping setlist pages.
Overview
setlist-mcp is a Build-phase MCP server that connects agents to setlist.fm for concert setlists, artists, venues, tours, and cities via a stdio npm package.
What is this MCP server?
- Queries setlist.fm for artists, venues, tours, cities, and full setlists from npm package setlist-mcp v0.7.0 over stdio
- Requires SETLIST_API_KEY from setlist.fm/settings/api; optional SETLIST_ACCEPT_LANGUAGE for localized place names (en, e
- Optional SETLIST_SESSION_COOKIE unlocks attendance write tools when you are logged in on www.setlist.fm.
- stdio transport—fits Claude Code and other MCP clients without running a separate HTTP gateway.
- GitHub source at chrischall/setlist-mcp for auditing env vars and tool surface before production use.
- Package version 0.7.0 on npm registry identifier setlist-mcp
- Transport type stdio per MCP server schema
- One required secret env var: SETLIST_API_KEY
What problem does it solve?
Agents cannot answer tour or setlist questions from setlist.fm unless you build custom API clients and keep credentials wired by hand.
Who is it for?
Indie builders and content makers who need authoritative setlist and tour data inside Claude Code or Cursor while prototyping music or events products.
Skip if: Teams that need offline catalogs, guaranteed SLAs, or bulk historical exports without setlist.fm’s API limits and terms.
What do I get? / Deliverables
After you add SETLIST_API_KEY and register the server, your agent can query and optionally record setlist.fm data through MCP tools instead of manual site browsing.
- MCP tools that read setlist.fm artists, venues, tours, cities, and setlists
- Optional write-side attendance tools when SETLIST_SESSION_COOKIE is configured
Recommended MCP Servers
Journey fit
MCP servers that expose a third-party HTTP API belong on the Build shelf because the solo builder installs them while wiring product or agent features, not during abstract ideation alone. Integrations is the right subphase because the server is a stdio bridge to setlist.fm’s API—artists, venues, tours, cities, and optional attendance writes—not a standalone skill or deploy pipeline.
How it compares
setlist.fm API bridge via MCP, not an agent skill that plans releases or writes marketing copy.
Common Questions / FAQ
Who is setlist-mcp for?
Solo developers and creators who want setlist.fm concert data—setlists, artists, venues, tours, and cities—available as MCP tools in their coding agent.
When should I use setlist-mcp?
Use it while building or iterating on features that need real concert histories, venue lookups, or tour context without writing a bespoke setlist.fm client.
How do I add setlist-mcp to my agent?
Install the npm package setlist-mcp, set SETLIST_API_KEY from setlist.fm/settings/api, configure stdio MCP in Claude Code or your client, and restart the agent session.