setlist.fm via curl + fpx (no MCP)

setlist.fm is hybrid: reads and writes use two different surfaces.

• Reads — a documented public REST API (api.setlist.fm/rest) keyed by an x-api-key header. Plain curl, no browser, no fpx.
• Writes — the only mutation setlist.fm offers is the site's "I was there" attendance toggle, and it exists only on the logged-in website (www.setlist.fm, server-rendered Apache Wicket), not the REST API. There's no login form to script — the credential is your browser's session cookie. fpx lifts that cookie out of your signed-in tab once; every actual request afterward is plain curl carrying it. No bridge round-trip per call.

This is the same data/actions the setlist_* MCP tools expose, reached with curl instead of a running server.

Part 1 — reads (curl + API key)

One-time setup