good_honker
# good_honker 🪿
A free, non-commercial **conversational Goose MCP** — a natural-language front end to
the band **Goose**'s show history, usable from Claude / claude.ai.
It is a **live proxy over the open [ElGoose.net](https://elgoose.net) API v2**. It does
**not** build, store, or redistribute a setlist dataset — every answer is fetched live
and credited to ElGoose.net. Short-lived caching (minutes) is used only to reduce load
and stay under ElGoose's rate limit.
> **Data: ElGoose.net (https://elgoose.net).** All setlist data belongs to the ElGoose
> community. good_honker is an independent fan tool, not affiliated with ElGoose or Goose.
## Use it
The server is live at **`https://good-honker.mino-yakking.com/mcp`** (Streamable HTTP).
Add it as a custom connector in claude.ai (**Settings → Connectors → Add custom
connector**), paste the URL above, then just ask:
- "What's the latest Goose show?"
- "What did Goose play on this day in history?"
- "How many times have they played Hot Tea, and when was the debut?"
- "Give me a random Goose show."
> Custom connectors require a paid Claude plan.
## Tools
`ping` · `get_setlist` · `latest_show` · `this_day_in_history` · `search_shows` ·
`random_show` · `song_stats` · `song_history` · `jam_chart` · `venue_info` ·
`upcoming_shows` · `album_info` · `appearances` · `show_extras`
## How it works
- **All data comes live from the ElGoose.net API v2** — no scraping, no stored dataset.
- Queries run per user request; caching is short-lived and only to reduce load.
- Every response credits ElGoose.net and links back.
- A Cloudflare Worker (`McpAgent` + Durable Object) serves the MCP over Streamable HTTP,
edge-caches upstream responses, and rate-limits per client. A Python stdio server
(`src/good_honker/`) mirrors the same tools for local use.
## Develop
```bash
uv sync
uv run pytest # Python stdio server + client tests
cd worker
npm install --legacy-peer-deps
npm run typecheck
npm run dev # local MCP at http://localhost:8787/mcp
```
## Attribution & license
Independent fan project, run non-commercially. Not affiliated with ElGoose.net or Goose.
Setlist data © the ElGoose.net community, served live under attribution — the data is
theirs and is not covered by this repo's license.
The good_honker source is MIT licensed ([LICENSE](LICENSE)).
TDQS
Scored across 14 tools
Each tool targets a distinct aspect of the Goose database: shows by date, search, random, song history, stats, jam charts, venues, upcoming, albums, appearances, extras, setlists, and health check. While there are multiple date-related tools, their descriptions clearly differentiate them (calendar day across years vs. specific date vs. most recent).
All names are snake_case and readable, but there is no consistent verb-noun pattern. Some use verbs (search_shows, get_setlist), others are noun phrases (song_history, venue_info), and a few are adjectives (random_show, latest_show). This mixed style reduces predictability, though not to the point of confusion.
With 14 tools, the server covers a rich domain without being bloated. Each tool serves a distinct purpose in the Goose data ecosystem, from search to deep dives into songs, venues, and show extras, making the count well-scoped.
The surface is thorough for a band-centric server: it includes discovery (search, random, history), detailed song data (history, stats, jam charts), show-specific info (setlist, extras), venue metadata, upcoming shows, album discography, and guest appearances. There are no obvious gaps for the intended use case.