Skip to main content
Glama
kevinnz

humanitix-mcp

by kevinnz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to humanitix-mcp

No user-submitted related servers found.

    Related Servers

    • eventbrite-mcp

      chrischall
      A
      license
      A
      quality
      A
      maintenance
      Read-only MCP server for accessing Eventbrite tickets, orders, organizer data, and public event search (including undocumented consumer search via browser bridge).
      31
      574 npm
      MIT

    • humaans-mcp

      ptorsten
      A
      license
      B
      quality
      D
      maintenance
      Read-only MCP server for the Humaans HRIS API, providing tools to query people, reporting chains, compensation, time away, and more.
      33
      MIT

    • hit-mcp

      DevpeakAB
      A
      license
      A
      quality
      D
      maintenance
      Read-only MCP server for the HIT ticket management system that lists queues, searches/fetches ticket details, and lists ticket templates.
      4
      10 npm
      1
      MIT

    • TryBooking MCP Server

      marek-knappe
      F
      license
      B
      quality
      D
      maintenance
      An MCP server that wraps the TryBooking Reporting API, enabling AI assistants like Claude to query bookings, events, sales reports, and attendance scans.
      15
      -

    • 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.9/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool targets a clearly distinct resource and action (list vs get for events, orders, tickets), and the analytics tools (check-in count, sales summary) are unambiguous. There is no meaningful overlap between any pair of tools.

    Naming Consistency4/5

    Nearly all tools follow a consistent humanitix_verb_noun pattern (list_events, get_order, list_tickets). The only deviation is sales_summary, which is a noun phrase without a verb, but the shared prefix keeps the set predictable.

    Tool Count5/5

    Nine tools is well-scoped for an event/ticketing read API, with each tool earning its place across events, dates, orders, tickets, and analytics.

    Completeness4/5

    The surface covers the core read lifecycle: events, event dates, orders, tickets, check-in totals, and sales aggregation. Only minor gaps exist (e.g. no single event-date fetch), which agents can work around via the list tool.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources