Skip to main content
Glama
delorenj

MCP Server for Ticketmaster Events

by delorenj
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to MCP Server for Ticketmaster Events

No user-submitted related servers found.

    Related Servers

    • Ticketmaster Partner API

      robandrewford
      A
      license
      C
      quality
      D
      maintenance
      Enables discovery and search of Ticketmaster events, venues, and attractions with advanced filtering options including date ranges, location-based search, and event classifications through the Ticketmaster Partner API.
      1
      MIT

    • @pipeworx/ticketmaster

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to search and retrieve live Ticketmaster Discovery v2 data, including events, venues, attractions, classifications, images, and autocomplete suggestions. Supports filtering by keyword, location, date ranges, and market for event discovery.
      267 npm
      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
      483 npm
      3
      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

    B3.1/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined as searching for events, venues, or attractions, making it straightforward for an agent to understand its function without confusion.

    Naming Consistency5/5

    Since there is only one tool, naming consistency is inherently perfect. The tool name 'search_ticketmaster' follows a clear verb_noun pattern, which would be consistent if more tools were added, but as a standalone, it sets a good precedent.

    Tool Count2/5

    A single tool is too few for a server focused on Ticketmaster events, which typically involves operations like browsing events, getting details, checking availability, or purchasing tickets. This minimal set feels thin and incomplete for the apparent scope, limiting agent capabilities.

    Completeness2/5

    The tool surface is severely incomplete for the domain of Ticketmaster events. While search is a useful starting point, there are obvious gaps such as retrieving event details, listing venues, checking ticket availability, or handling bookings, which are essential for comprehensive event management workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources