setlist.fm concert data for Claude — setlists, artists, venues, tours, and cities
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"io-github-chrischall-setlist-mcp": {
"command": "<see-readme>",
"args": []
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
MCP server for setlist.fm — search concert setlists, artists, venues, tours, and cities from Claude via natural language. Mostly read-only (the setlist.fm REST API exposes no write endpoints), plus authenticated "I was there" attendance actions via your logged-in session.
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in ai-ml
Dynamic problem-solving through sequential thought chains
Persistent memory using a knowledge graph
Just a Better Chatbot. Powered by Agent & MCP & Workflows.
Workspace template + MCP server for Claude Code, Codex CLI, Cursor & Windsurf. Multi-agent knowledge engine (ag-refresh / ag-ask) that turns any codebase into a queryable AI assistant.
MCP Security Weekly
Get CVE alerts and security updates for io.github.chrischall/setlist-mcp and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
MCP server for setlist.fm — search concert setlists, artists, venues, tours, and cities from Claude via natural language. Mostly read-only (the setlist.fm REST API exposes no write endpoints), plus authenticated "I was there" attendance actions via your logged-in session.
This project was developed and is maintained by AI (Claude). Use at your own discretion.
Exposes 20 tools — 18 read-only over the setlist.fm REST API, plus 2 authenticated "I was there" attendance actions:
| Area | Tools |
|---|---|
| Artists | setlist_search_artists, setlist_get_artist, setlist_get_artist_setlists |
| Setlists | setlist_search_setlists, setlist_get_setlist, setlist_get_setlist_version |
| Venues | setlist_search_venues, setlist_get_venue, setlist_get_venue_setlists |
| Cities & countries | setlist_search_cities, setlist_get_city, setlist_search_countries |
| Users | setlist_get_user, setlist_get_user_attended, setlist_get_user_edited |
| Resolve | setlist_resolve_concerts |
| Attendance (authenticated writes) | setlist_mark_attended, setlist_unmark_attended |
| Utility | setlist_healthcheck, setlist_id_from_url |
Get a free API key (non-commercial use) at setlist.fm/settings/api, then add the server to your .mcp.json:
{
"mcpServers": {
"setlist": {
"command": "npx",
"args": ["-y", "setlist-mcp"],
"env": {
"SETLIST_API_KEY": "your-api-key-here"
}
}
}
}
Optional: SETLIST_ACCEPT_LANGUAGE (one of en, es, fr, de, pt, tr, it, pl) localizes city/country names.
See SKILL.md for from-source setup, the full tool reference, and example flows.
Use is governed by the setlist.fm API terms. In short:
url; surface it as a followable source link (no nofollow) wherever the data is shown. The tool descriptions instruct the model to do this, and results pass the url through verbatim.SETLIST_API_KEY (.env is gitignored) and never appears in tool output.npm install
npm run build # tsc + esbuild bundle → dist/
npm test # vitest
For local runs, put SETLIST_API_KEY=<key> in a .env file (gitignored) next to the project root.
See CLAUDE.md for architecture, conventions, and gotchas.
MIT