humanitix-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HUMANITIX_API_KEY | Yes | Your Humanitix API key. | |
| HUMANITIX_BASE_URL | No | The base URL for the Humanitix API. | https://api.humanitix.com |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| humanitix_list_eventsA | List Humanitix events accessible to the configured API key. Returns trimmed event summaries by default; set raw=true to receive the full Humanitix payload. Results are paginated and capped at max_items (default 500). Use in_future_only=true to retrieve only events whose end date is in the future, or provide an ISO 8601 datetime via since. |
| humanitix_get_eventA | Fetch a single Humanitix event by its event identifier. Returns the trimmed event by default; set raw=true for the full payload. |
| humanitix_list_event_datesA | List the event dates (sessions) belonging to a Humanitix event. Event dates are required identifiers for orders, tickets, and check-in tools. Returns a projection of each date with its id, name, and start/end times. |
| humanitix_list_ordersA | List orders for a specific Humanitix event and event date. The event_id identifies the event; event_date_id identifies its specific date and can be obtained from humanitix_list_event_dates. Returns trimmed orders by default; set raw=true for full payloads. |
| humanitix_get_orderA | Fetch a single order by its event identifier and order identifier. Returns a trimmed order by default; set raw=true for the full payload. |
| humanitix_list_ticketsA | List tickets for a specific Humanitix event and event date. The event_id identifies the event; event_date_id identifies its specific date and can be obtained from humanitix_list_event_dates. Optionally filter by ticket status. Returns trimmed tickets by default; set raw=true for full payloads. |
| humanitix_get_ticketA | Fetch a single ticket by its event identifier and ticket identifier. Returns a trimmed ticket by default; set raw=true for the full payload. |
| humanitix_get_check_in_countA | Get check-in totals for a Humanitix event and event date. The event_id identifies the event; event_date_id identifies its specific date and can be obtained from humanitix_list_event_dates. Warning: the /check-in-count endpoint is BETA and its response shape may change. Returns trimmed counts by default; set raw=true for the full payload. |
| humanitix_sales_summaryA | Build a sales summary for a Humanitix event and event date by aggregating tickets. Reports sold/complete counts, cancelled counts, gross revenue (when price data is available), and capacity utilisation (when a trustworthy capacity value is present). The event_id identifies the event; event_date_id identifies its specific date and can be obtained from humanitix_list_event_dates. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
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.
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.
Nine tools is well-scoped for an event/ticketing read API, with each tool earning its place across events, dates, orders, tickets, and analytics.
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.