Skip to main content
Glama
chrischall

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.
      492 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
      3
      MIT

    • MusicBrainz MCP Server

      zas
      A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to query the MusicBrainz music database for artists, albums, recordings, and labels. It provides tools for advanced searches, detailed metadata retrieval, and accessing cover art information.
      17
      13
      GPL 3.0
    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.1/5.0

    Scored across 20 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: search vs. get vs. get-setlists for artists and venues, plus separate user, batch-resolution, and utility tools. The few overlapping-sounding tools (e.g., setlist_get_artist_setlists vs. setlist_search_setlists) are clearly differentiated by their parameters and descriptions.

    Naming Consistency4/5

    All tools share a consistent setlist_ prefix and almost all follow a verb_noun pattern like get_artist, search_venues, mark_attended. Minor deviations like setlist_id_from_url and setlist_healthcheck are still readable but break the strict verb_noun convention.

    Tool Count4/5

    At 20 tools, the server sits at the upper edge of the ideal range, but the count is justified by the breadth of the setlist.fm API: lookup/search for all entity types, user actions, a batch resolver, and utilities. Each tool earns its place without redundancy.

    Completeness5/5

    The surface covers the full read side of the domain (artists, venues, cities, countries, setlists, users), plus write actions (mark/unmark attended), batch resolution, URL parsing, and a healthcheck. There are no obvious dead ends for typical setlist.fm workflows.

    Maintenance

    ActivityActive
    ResponsivenessResponsive

    Resources