Log inSubmit server
Setlist MCP logo

Setlist MCP

Search setlist.fm concert data and manage authenticated attendance through MCP tools.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Setlist MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "setlist-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "setlist-mcp"
      ],
      "env": {
        "SETLIST_API_KEY": "YOUR_VALUE_HERE",
        "SETLIST_ACCEPT_LANGUAGE": "YOUR_VALUE_HERE",
        "SETLIST_SESSION_COOKIE": "YOUR_VALUE_HERE",
        "SETLIST_DISABLE_FETCHPROXY": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Automated check passed— started and listed 20 tools correctly (4d ago).

Overview

The setlist-mcp MCP server connects Claude and other MCP clients to setlist.fm for concert data lookup. It provides 20 tools covering setlists, artists, venues, tours, cities, countries, users, URL resolution, and health checks, with two authenticated attendance actions. Most operations call the setlist.fm REST API live and do not write data; use it when an agent needs current concert information or setlist.fm attendance updates.

Use cases

  • Search an artist’s recent concert setlists
  • Find venues and concerts by city
  • Retrieve a setlist from a setlist.fm URL
  • Review a user’s attended concerts
  • Mark a concert as attended

Key features

  • Searches setlists, artists, venues, cities, and countries
  • Retrieves artist, venue, setlist, and user details
  • Resolves setlist.fm URLs and concerts
  • Supports authenticated attendance updates
  • Localizes city and country names
  • Provides a health check tool

Tools20

What Setlist MCP lets your agent do. Expand a tool for its parameters.

Verified live~6.1k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

5/5 checks healthy over the last 45d

What it can do

From the 20 tools this server returned when we ran it; 20 declare their own safety hints.

Can delete or modify data · 1Handles credentials · 3Makes network requests · 20Read-only tools · 19
Network at startup3 connections
Files written at startupNone
Install scriptsNone
npm provenanceSigned build
Package age132 days
Maintainers1

Observed 2026-10-18 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 15d ago via OSV.dev · setlist-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars1Stargazers on the source repository.
npm downloads2.7kPackage downloads in the last 30 days.
Last commit3d agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed20Callable tools this server registers over MCP.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.

How Setlist MCP works

What setlist-mcp MCP server does

The setlist-mcp MCP server exposes setlist.fm data through MCP tools. It supports searches and lookups for concert setlists, artists, venues, cities, countries, tours, and users. The server also resolves setlist.fm URLs into identifiers and provides a health check for diagnosing availability.

Its 20 tools are divided between read operations and attendance actions. Eighteen tools query the setlist.fm REST API. setlist_mark_attended and setlist_unmark_attended are authenticated actions that update whether the logged-in setlist.fm user attended a concert.

How it works

The server runs as an MCP process and makes a live API request for each tool invocation. It does not maintain a datastore or persist API responses. Results include the source URL returned by setlist.fm, which should be presented as a followable attribution link when the data is shown.

API access uses a setlist.fm API key. The free key described by the project is intended for non-commercial use, and commercial use requires permission from setlist.fm. The server keeps the key in its environment rather than exposing it in tool results.

Setup and configuration

To run the setlist-mcp MCP server, obtain an API key from the setlist.fm account settings and configure an MCP client to launch npx -y setlist-mcp with SETLIST_API_KEY in its environment.

SETLIST_ACCEPT_LANGUAGE is optional and accepts en, es, fr, de, pt, tr, it, or pl. It controls localization for city and country names.

The attendance tools need an authenticated www.setlist.fm session. You can provide the request cookie through SETLIST_SESSION_COOKIE, or use the ContextMint Bridge Chrome extension while signed in. The browser-based fallback can be disabled with SETLIST_DISABLE_FETCHPROXY=1.

Tools and capabilities

Available tool groups include:

  • Search and retrieve artists, their setlists, and individual setlists or versions.
  • Search venues and retrieve venue details or venue setlists.
  • Search and retrieve cities, plus search countries.
  • Retrieve user profiles, attended concerts, and edited setlists.
  • Resolve concerts and extract an ID from a setlist.fm URL.
  • Mark or unmark attendance when an authenticated session is available.
  • Check service health.

Limitations and notes

The setlist-mcp MCP server is primarily read-only because the setlist.fm REST API does not expose general write endpoints. Attendance updates are the exception and require a logged-in session. API terms require attribution, prohibit persistent caching for this use, and restrict free-key use to non-commercial purposes.

The project is distributed under the MIT license. From-source development uses npm, TypeScript, esbuild, and Vitest, but the documented client setup runs the published package through npx.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Setlist MCP

setlist-mcp is an MCP server that connects AI clients to setlist.fm. Its main tools search and retrieve concert setlists, artists, venues, cities, countries, and user data, while also resolving setlist.fm URLs and marking or unmarking attendance when an authenticated session is supplied.

Install it through an MCP client by launching `npx -y setlist-mcp` and setting `SETLIST_API_KEY` in the server environment. Obtain the API key from setlist.fm account settings before starting the server.

Yes, attendance updates are supported through `setlist_mark_attended` and `setlist_unmark_attended`. These tools require a logged-in www.setlist.fm session provided through `SETLIST_SESSION_COOKIE` or the ContextMint Bridge browser fallback.

Yes, it provides separate tools for searching artists, setlists, and venues, as well as retrieving an artist’s or venue’s related setlists. Results come from live setlist.fm API requests.

It requires a setlist.fm API key in `SETLIST_API_KEY`.

Related MCP servers

All in Art & Culture All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewSetlist MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/setlist-mcp?style=directory)](https://allmcps.com/mcp/setlist-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/setlist-mcp"><img src="https://allmcps.com/api/badge/setlist-mcp?style=directory" alt="Setlist MCP on AllMCPs" /></a>