Skip to main content
Glama
Sign In
setlist-mcp

setlist-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to setlist-mcp

No user-submitted related servers found.

    Related Servers

    • SetlistMCP

      adrianparker
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to search for and retrieve concert setlists from setlist.fm by artist, city, and date, and to view full setlists with songs, sets, and encores.
      315 npm
      MIT

    • mcp-umphreys

      pete-builds
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables querying Umphrey's McGee setlist data including shows, songs, jam charts, and guest appearances through natural language.
      MIT

    • mcp-phish

      pete-builds
      A
      license
      Not graded
      quality
      A
      maintenance
      Combines phish.net and phish.in APIs into twelve tools for setlists, songs, jam-charts, reviews, and audio.
      1
      MIT

    • SeatGeek MCP Server

      PeterShin23
      A
      license
      A
      quality
      D
      maintenance
      Enables users to search for events, performers, and venues through the SeatGeek API. Provides event recommendations, detailed venue seating information, and performer discovery capabilities for ticketed entertainment events.
      4
      397 npm
      3
      MIT

    • scrobble-gateway

      ojimpo
      A
      license
      Not graded
      quality
      B
      maintenance
      Exposes a self-hosted SQLite master of a user's complete Last.fm listening history over Streamable HTTP with OAuth 2.1, so ChatGPT or Claude can answer questions about any date range without hitting the Last.fm API. Provides 32 tools covering recent plays, period rankings, range comparisons, artist listening intensity, session segmentation, and shifts in taste over time.
      312 npm
      MIT
    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

    A4/5.0

    Scored across 20 tools

    Disambiguation4/5

    Each tool maps to a clear entity+action pair (artist, venue, city, country, user, setlist with get/search/batch-resolve/toggle variants), and the write pair mark_attended/unmark_attended is unambiguous. The only mild overlap is between setlist_search_setlists and setlist_resolve_concerts, both of which locate setlists, but their descriptions clearly separate single-search from bulk-batch resolution.

    Naming Consistency5/5

    Every tool follows the identical setlist_{verb}_{noun} snake_case pattern (setlist_get_artist, setlist_search_venues, setlist_mark_attended). Verb choice is consistent (get/search/resolve/mark/unmark), making the surface highly predictable.

    Tool Count4/5

    20 tools is on the heavier side, but the domain legitimately spans six entity types each warranting get/search plus setlist-specific helpers. Each tool earns its place with little redundancy, so it sits just over the comfortable range rather than bloating it.

    Completeness4/5

    Coverage is broad: artists, venues, cities, countries, users, and setlists all have retrieval paths, plus write (attended), bulk resolve, URL parsing, and a healthcheck. Minor gaps exist (e.g. no user search endpoint, no direct song-level lookup), but core lifecycle workflows are fully served.

    Maintenance

    ActivityActive
    ResponsivenessResponsive

    Resources