Skip to main content
Glama
chrischall

eventbrite-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to eventbrite-mcp

No user-submitted related servers found.

    Related Servers

    • humanitix-mcp

      kevinnz
      A
      license
      A
      quality
      B
      maintenance
      A read-only MCP server for the Humanitix Public API that exposes nine tools to list events, fetch event details, list orders/tickets, check-in counts, and sales summaries.
      9
      MIT

    • @guedder/mcp

      guedder
      F
      license
      Not graded
      quality
      B
      maintenance
      Readonly MCP server for the Guedder API v3, enabling operational tasks like listing events, searching tickets, and managing purchases via Streamable HTTP or stdio.
      -

    • Eventbrite MCP Server

      mcpflow
      A
      license
      A
      quality
      D
      maintenance
      This is a Model Context Protocol (MCP) server that provides tools for interacting with the Eventbrite API. It allows AI assistants to search for events, get event details, retrieve venue information, and more.
      4
      18 npm
      MIT

    • Eventbrite MCP Server

      marek-knappe
      F
      license
      Not graded
      quality
      D
      maintenance
      Full MCP server for the Eventbrite API with 73 tools to manage events, attendees, orders, tickets, venues, discounts, reports, webhooks, and more.
      -
    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.6/5.0

    Scored across 31 tools

    Disambiguation4/5

    Most tools are cleanly scoped by resource and side (organizer vs attendee vs public), and list/get pairs like eb_ticket_classes/eb_ticket_class are clearly distinct. The main overlap is eb_event vs eb_event_details, which both fetch an event by id and could be confused. The various event-list tools (org/organizer/venue/series) are well differentiated by their descriptions.

    Naming Consistency4/5

    Names follow a predictable eb_ prefix plus snake_case noun or verb_noun pattern (eb_org_events, eb_search_events, eb_resolve_place, eb_event_description). Minor deviations like eb_healthcheck (single joined word) and eb_me break the strict snake_case convention slightly. Overall the set reads consistently.

    Tool Count3/5

    At 31 tools the surface is heavy and sits above the comfortable 3-15 range. The domain (events, orders, attendees, venues, organizers, webhooks, reports, search) is genuinely broad, so most tools target distinct resources, but several read operations could plausibly be consolidated. Count is justified by scope yet on the bulky side.

    Completeness3/5

    Read/query coverage is strong across events, orders, attendees, venues, organizers, series, webhooks, discounts, ticket groups, reports, search, and reference data. However the surface is almost entirely read-only — no create/update/delete for events, orders, or check-in operations — leaving notable lifecycle gaps. These missing write operations will limit agent workflows beyond discovery and analytics.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive

    Resources