SetlistMCP
Enables AI assistants to search for and retrieve concert setlists from setlist.fm by artist, city, and date, and to view full setlists with songs, sets, and encores.
README
setlist-mcp
An MCP server that lets Claude find setlist.fm setlists for gigs you've been to.
Ask "I saw The Cure in Wellington in August 1992 — what did they play?" and Claude resolves the artist, searches setlist.fm, and reads back the songs in order.
Features
find_setlists— search by artist, city and date. Returns a compact list of matching gigs with their setlist IDs, venues and song counts.get_setlist— fetch one setlist in full: every song in order, grouped into sets and encores, with cover and guest-appearance notes.- Forgiving about dates. Searching covers the year around the date you give and ranks results by how close they are, so a misremembered day still finds the gig.
- Forgiving about artist names. Names resolve through MusicBrainz, so minor misspellings usually still work. Ambiguous names come back with alternatives.
- Careful with rate limits. Requests are serialised and spaced out, 429s are retried with backoff, and responses are cached. Searches take a few seconds by design.
Installation
git clone git@github.com:adrianparker/setlist-mcp.git
cd setlist-mcp
npm install
cp .env.example .env
Then edit .env and set SETLISTFM_API_KEY. Request a key at
setlist.fm's API settings — it's free, and
requires a setlist.fm account.
Setting MUSICBRAINZ_CONTACT to your email address is good manners: MusicBrainz
asks that clients identify a contact in their User-Agent, and throttles
anonymous-looking clients harder.
Registering with Claude Code
claude mcp add setlist-mcp --scope user -- node /full/path/to/setlist-mcp/src/index.js
Or add it to a project's .mcp.json:
{
"mcpServers": {
"setlist-mcp": {
"command": "node",
"args": ["/full/path/to/setlist-mcp/src/index.js"]
}
}
}
No secrets go in the client config — the server reads .env from its own directory,
so it works whatever directory the client launches it from.
Restart Claude Code, then check it connected with /mcp.
Usage
Once registered, just ask in plain English:
I saw Villainy in Tauranga in March 2026, what was the setlist?
Claude will call find_setlists, pick the matching gig, then call get_setlist.
To check the server directly without a client:
npx @modelcontextprotocol/inspector node src/index.js
Configuration
| Variable | Default | Purpose |
|---|---|---|
SETLISTFM_API_KEY |
— | Required. Your setlist.fm API key. |
MUSICBRAINZ_CONTACT |
repo URL | Contact detail sent to MusicBrainz in the User-Agent. |
NODE_ENV |
app |
Which src/config/<env>.json the logger loads. |
SETLISTFM_MIN_INTERVAL_MS |
1100 |
Minimum gap between setlist.fm requests. |
SETLISTFM_DAILY_LIMIT |
1300 |
Per-process request budget for setlist.fm. |
MUSICBRAINZ_MIN_INTERVAL_MS |
1100 |
Minimum gap between MusicBrainz requests. |
HTTP_TIMEOUT_MS |
10000 |
Per-request timeout. |
Rate limiting
setlist.fm doesn't publish its rate limits. Community reports put the standard tier
at roughly 2 requests per second and 1440 per day, so the defaults here — one request
every 1.1 seconds — sit comfortably inside the slower end of that. Requests are
serialised through a queue, so concurrent tool calls wait their turn rather than
bursting. A 429 backs off the whole queue, honouring Retry-After when the server
sends one.
The daily limit is not a real daily quota. It's held in memory, so it resets whenever the MCP client restarts the server. Treat it as a circuit breaker against a runaway loop, not as compliance. The minimum interval is what actually protects your key: at 1.1s per request, reaching 1440 requests would take 26 minutes of continuous querying.
Responses are cached in memory — artists for 24 hours, searches for 1 hour, setlist detail for 6 hours — so repeated questions about the same gig cost nothing.
Development
Run tests
npm test
npm run test:watch
No test touches the real APIs: test/setup.js installs a global.fetch that throws,
and tests stub it explicitly.
Coverage
npm run coverage
Lint
npm run lint
A note on setlist.fm
The setlist.fm API is free for non-commercial use only — see their API terms. Both tools return the setlist.fm URL for every result so it can be linked back to.
Setlist data is contributed by setlist.fm's users. Gigs may be missing, incomplete, or have the wrong date.
License
MIT
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。