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
      Not graded
      quality
      C
      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.
      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
      B
      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.5/5.0

    Scored across 31 tools

    Disambiguation4/5

    Most tools have a clear resource-and-scope target (venue, order, attendee, ticket class), and the descriptions are careful about organizer vs attendee vs public views. The main risk is eb_event vs eb_event_details and the multiple order/attendee list variants, which could cause misselection if an agent skims names.

    Naming Consistency4/5

    The eb_ prefix is used everywhere, and singular nouns (eb_event, eb_order) vs plural nouns (eb_event_attendees, eb_org_orders) reliably distinguish single-get from list operations. A few one-offs like eb_resolve_place, eb_search_events, eb_healthcheck, and eb_event_details break the pure resource-noun pattern but remain readable.

    Tool Count2/5

    At 31 tools this surface is heavy; it exceeds the 25-tool threshold and will consume meaningful agent context. The breadth is defensible for Eventbrite's read domain, but several list/get variants could likely be consolidated.

    Completeness3/5

    Read coverage is extensive: events, venues, organizers, orders, attendees, ticket classes, questions, discounts, webhooks, reports, and public search are all represented. However, there are no create/update/delete operations, no attendee check-in mutations, and no webhook registration, which are notable gaps for a full Eventbrite lifecycle.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive

    Resources