Skip to main content
Glama
mcpflow

Eventbrite MCP Server

by mcpflow
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

Related Servers

Alternatives to Eventbrite MCP Server

No user-submitted related servers found.

    Related Servers

    • eventos MCP Server

      bsj-m-takigawa
      F
      license
      Not graded
      quality
      D
      maintenance
      MCP server for eventos event management platform, enabling AI assistants to manage events and tickets via API integration. Supports authentication, ticket CRUD operations, and listing with pagination.
      1
      -

    • MCP API Server

      fikri2992
      A
      license
      A
      quality
      D
      maintenance
      A Model Context Protocol server that enables AI assistants to make HTTP requests (GET, POST, PUT, DELETE) to external APIs through standardized MCP tools.
      4
      2
      MIT

    • untappd-mcp-server

      darrenjrobinson
      A
      license
      B
      quality
      B
      maintenance
      A Model Context Protocol (MCP) server that exposes the Untappd API as tools for AI agents. Enables searching venues, breweries, and beers, checking what's on tap via recent check-in feeds, and looking up user activity.
      27
      38 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.
      -

    • MCP Global Events

      Nickfx9
      F
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that dynamically sources global technology events, communities, and niche networking mixers from Luma, Eventbrite, Meetup, and fallback search sources, enabling event discovery and community finding via natural language.
      -
    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.7/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool targets a distinct resource: searching events, retrieving a specific event, listing categories, and fetching venue details. There is no overlap in purpose, so an agent can easily select the correct tool.

    Naming Consistency5/5

    All tool names follow a clear verb_noun pattern (search_events, get_event, get_categories, get_venue). The consistency makes the toolset predictable and easy to navigate.

    Tool Count5/5

    With only 4 tools, the server is tightly scoped for read-only event discovery. Each tool serves a clear, necessary function and the count feels appropriate for the domain.

    Completeness4/5

    The toolset covers the core read operations for events, categories, and venues. It lacks a few potentially useful endpoints like searching venues or getting organizers, but for the apparent purpose of event discovery, it is nearly complete.

    Maintenance

    ActivityInactive
    ResponsivenessSyncing

    Resources