Skip to main content
Glama
Sign In
biletix-mcp

biletix-mcp

by mohammad-abbasi-sh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to biletix-mcp

No user-submitted related servers found.

    Related Servers

    • DICE MCP

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables browsing live event, venue, and lineup listings city by city, with optional category filtering for gigs, club nights, comedy, theatre, and talks. Also returns full detail for any single event, including dates, venue and address, on-sale window, starting price, billed artists, and highlights such as age restrictions.
      388 npm
      MIT

    • 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

    • biletall-mcp

      mohammad-abbasi-sh
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables read-only search of Turkish bus and flight tickets on biletall.com, including routes, journeys, prices, price statistics, popular routes, and location lookup through MCP tools.
      MIT

    • b2match-mcp

      barzoj
      A
      license
      A
      quality
      A
      maintenance
      Enables read-only access to B2match event and matchmaking data through tools for events, participants, organisations, opportunities, agenda, sessions, speakers, and authenticated meeting, schedule, conversation, and notification workflows. Supports anonymous public queries and secure local token-based access.
      2
      22
      92 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

    A3.9/5.0

    Scored across 6 tools

    Disambiguation4/5

    trending, search_events, and list_by_category all return featured events, which creates some overlap, but each has a distinct filter axis (featured/starting-soon, keyword+city, category). get_event, list_venues, and venue_events are clearly distinct and the descriptions explicitly explain their boundaries.

    Naming Consistency4/5

    All tools share the biletix_ prefix and snake_case, with verb_noun or verb_resource patterns (search_events, get_event, list_venues, list_by_category). Minor deviations: 'biletix_trending' uses a bare adjective and 'venue_events' drops the verb, but overall predictable.

    Tool Count5/5

    Six tools is a well-scoped set for a read-only event discovery server, with each tool earning its place (featured browsing, search, detail, category, venue lookup, venue events). Nothing feels redundant or padded.

    Completeness3/5

    The browsing lifecycle is mostly covered (list → search → detail → venue drill-down), but search only covers featured SSR listings, not the full catalogue, and there are no date-range or artist-specific filters. Agents wanting non-featured events hit a dead end the descriptions acknowledge.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources