Connect the data API

Tweezer Picks runs on a read-only Model Context Protocol (MCP) server over Phish setlist data. Point any MCP client at it and ask questions in plain language: search songs, find bust-out candidates, pull a show's full setlist, or trace a song's history.

The endpoint

It's a Streamable HTTP MCP server. No auth, read-only, rate-limited.

https://www.tweezerpicks.com/mcp

Claude Code (CLI)

One command adds it to your user config:

claude mcp add -t http -s user phish https://www.tweezerpicks.com/mcp

Then start a session and ask, e.g. "what Phish songs are overdue for a bust-out?"

Claude Desktop

Add a remote (HTTP) server to your claude_desktop_config.json:

{
  "mcpServers": {
    "phish": {
      "type": "http",
      "url": "https://www.tweezerpicks.com/mcp"
    }
  }
}

Restart Claude Desktop and the tools appear under the plug icon.

Any MCP client

It speaks the current MCP spec over Streamable HTTP. Configure your client with the transport set to HTTP and the URL above. No headers or tokens required.

Available tools

search_songs — find songs by title; returns play counts and current gap.
get_song — one song's record: debut, last play, total plays, current gap.
songs_by_gap — songs ranked by shows since last play (bust-out radar).
song_history — every performance of a song, most recent first.
recent_shows — the latest shows, newest first.
get_show — a single show with its full setlist and venue.
venue_history — every show played at a given venue.
jam_chart — editorially flagged notable jams.
appearances — guest sit-ins, by guest or by show.
stats_overview — catalog-wide roll-up (also powers the Stats page).
validate_song_slugs — batch-check song slugs against the catalog.
health — server + data-freshness status.

The MCP server is open source too: the game and the data layer are both yours to self-host.