Skip to main content
Glama
Sign In
good_honker

good_honker

by dmpeters
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

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 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.dmpeters63.workers.dev/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.

Related MCP server: Sessionize

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

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).

Available Tools

14 tools
album_infoB

Goose discography: list albums, or the tracklist of one album.

Inputs: album. Returns: result

appearancesB

Guest sit-ins / musician appearances, optionally filtered to one person.

Inputs: limit, person. Returns: result

get_setlistB

Goose setlist for a given date (YYYY-MM-DD).

Inputs: date (required), include_related. Returns: result

jam_chartC

Notable jams from the ElGoose jam charts, optionally filtered to one song.

Inputs: song, limit. Returns: result

latest_showC

The most recent show's setlist.

Inputs: include_related. Returns: result

pingA

Health check and a manifest of what good_honker can do.

Inputs: no named parameters. Returns: result

random_showA

A random Goose show, with its full setlist. Great for discovery.

Inputs: no named parameters. Returns: result

search_showsC

Find shows by year, city, state, and/or venue name.

Inputs: city, year, limit, state, +2 more. Returns: result

show_extrasB

Poster art, images, and external links attached to a show on a given date.

Inputs: date (required). Returns: result

song_historyD

Every time a song has been played (most recent first).

Inputs: song (required), limit, include_related. Returns: result

song_statsC

Summary stats for a song: times played, debut, last played, jamchart count.

Inputs: song (required), include_related. Returns: result

this_day_in_historyA

Every show played on a given calendar day (month 1-12, day 1-31), across years.

Inputs: day (required), month (required), include_related. Returns: result

upcoming_showsB

Announced upcoming shows (dates on or after today).

Inputs: include_related. Returns: result

venue_infoC

Venue metadata plus how many times Goose has played there.

Inputs: venue (required). Returns: result

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    C2.9/5.0

    Scored across 14 tools

    Disambiguation5/5

    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).

    Naming Consistency3/5

    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.

    Tool Count5/5

    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.

    Completeness5/5

    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.

    Maintenance

    ActivitySlowing
    ResponsivenessOutdated data

    Resources

    Related MCP Connectors

    Related MCP Servers

    • Sessionize

      labjp-mcp
      A
      license
      A
      quality
      C
      maintenance
      MCP server for accessing Sessionize event data. Query speakers, sessions, and schedules from any Sessionize-powered conference using natural language.
      6
      4
      Apache 2.0
    • LabelGrid MCP Server

      LabelGrid MCP Serverofficial

      labelgrid
      A
      license
      A
      quality
      B
      maintenance
      The official MCP server for LabelGrid's music distribution platform, enabling natural language management of music catalogs, releases, files, analytics, royalties, webhooks, and distribution via a thin wrapper over the LabelGrid public API.
      84
      4
      MIT

    • urmusic-mcp

      ipaud
      A
      license
      A
      quality
      C
      maintenance
      A personal MCP server that analyzes your Spotify streaming history locally, enabling queries, artist insights, and recommendations using a local SQLite database.
      7
      MIT