otherapi_key

Humanitix

Humanitix is a not-for-profit ticketing platform that donates 100% of its profits to charity.

Verdict

The Humanitix MCP lets your team query event data from your Humanitix account without leaving Switchy. @mention it to pull event lists, retrieve details for a specific event by ID, or fetch all tags you've applied to events. Most useful for event coordinators who need to check registration status, compare event metadata across campaigns, or generate reports during planning meetings. Requires an API key from your Humanitix dashboard — setup takes about two minutes, but you'll only see events your key has access to.

Common use cases

  • Check event registration counts during standup
  • Compare ticket sales across multiple campaigns
  • Pull event metadata for quarterly reports
  • Audit tags applied to past events
  • Verify event details before sending invites

Integration

Vendor
Humanitix
Category
other
Auth
API_KEY
Tools
3
Composio slug
humanitix

Tools

  • Get Event

    Tool to retrieve detailed information about a specific event. use when you have the eventid and need full metadata.

  • Get Events

    Tool to retrieve a paginated list of events from your humanitix account. use when you need to page through your events after confirming api key validity.

  • Get Tags

    Tool to get all tags associated with your humanitix account. use when you need to list or paginate through tags after setting up your api key.

Setup

Setup guide

  1. 11. Open your Switchy workspace and navigate to Settings > Integrations > MCP Servers. 2. Click 'Add MCP' and select Humanitix from the list. 3. Log into your Humanitix account in a separate tab, go to Settings > API, and generate a new API key. 4. Copy the key and paste it into the API Key field in Switchy, then click 'Connect'. 5. Switchy will validate the key and confirm the connection. 6. Open any Space in your workspace and type '@Humanitix get events' to test — you should see a paginated list of events from your account. 7. If the list appears, the integration is live and ready to use in any Space.

What teammates see: by default, memories from Humanitix are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.

Works well with

Top models

Compatibility data appears once enough Spaces have used this MCP together with a given model.

How Switchy teams use it

Not enough Spaces yet to publish anonymised usage stats (we require ≥ 50 Spaces per week).

Starter prompts

List All Events

@Humanitix get events. Show me the first page of events with their names, dates, and ticket counts.
Open in a Space →

Event Details by ID

@Humanitix get event with ID [paste event ID here]. I need the full details including description, location, and registration status.
Open in a Space →

Review All Tags

@Humanitix get tags. Show me all tags we've used across events so I can standardize our naming.
Open in a Space →

Compare Event Performance

@Humanitix get events. Filter for events in the last quarter and show me ticket sales for each.
Open in a Space →

Pre-Launch Event Check

@Humanitix get event with ID [paste event ID here]. Confirm the ticket types, pricing, and event description are correct before we go live.
Open in a Space →

Example outputs

Illustrative - representative of the model's voice and quality, not literal recordings.

Prompt

@Humanitix list all upcoming events in my account and show me their ticket sales status

Output

Found 4 upcoming events in your Humanitix account: 'Tech Summit 2025' (March 15, 127/200 tickets sold), 'Community Workshop Series' (April 2-9, 43/80 tickets sold across 3 sessions), 'Annual Fundraiser Gala' (May 20, 89/150 tickets sold), and 'Product Launch Webinar' (June 1, 312/500 tickets sold). The Product Launch Webinar is your best performer at 62% capacity. The Community Workshop Series has the lowest uptake so far at 54% across sessions.

Notes

This example uses the Get Events tool to retrieve a paginated list. The response shape depends on your account's event volume—accounts with 50+ events may need follow-up prompts to page through results. Requires a valid API key with read access to event data.

Prompt

@Humanitix pull full details for event ID evt_abc123 including attendee count and revenue breakdown

Output

Event 'Tech Summit 2025' (evt_abc123): Scheduled for March 15, 2025 at Convention Center Downtown. Ticket sales: 127 sold (63.5% capacity), generating $12,065 in gross revenue. Breakdown: 45 Early Bird tickets ($75 each), 62 General Admission ($110 each), 20 VIP passes ($185 each). Event tagged with 'technology', 'networking', 'professional-development'. Registration closes March 10 or when capacity is reached.

Notes

This example demonstrates the Get Event tool's ability to retrieve comprehensive metadata for a single event when you have the event ID. Useful for detailed reporting or when synthesizing event performance data. The tool returns structured data that the AI can parse and summarize—actual field names and nesting may vary by Humanitix's API version.

Prompt

@Humanitix show me all tags in my account, then identify which events use the 'fundraising' tag and calculate total revenue from those events

Output

Your Humanitix account has 12 tags: 'fundraising', 'technology', 'community', 'workshop', 'webinar', 'networking', 'professional-development', 'arts', 'charity', 'education', 'sports', 'family'. Cross-referencing events: 2 events use the 'fundraising' tag—'Annual Fundraiser Gala' ($16,465 revenue, 89 tickets sold) and 'Charity Auction Night' ($8,920 revenue, 34 tickets sold). Combined fundraising revenue: $25,385 across 123 attendees.

Notes

This example chains two tools (Get Tags + Get Events) and applies AI reasoning to synthesize insights. Demonstrates how Switchy can combine MCP data retrieval with analysis. Performance depends on the number of events in your account—large catalogs may require pagination. The revenue calculation assumes the AI can access ticket pricing from event metadata.

Use-case deep-dives

Nonprofit event attendance tracking

When Humanitix MCP makes sense for small event teams

A three-person nonprofit running quarterly fundraisers needs to pull attendance data into Slack threads without logging into the Humanitix dashboard every time. The Get Events tool pages through your event list, and Get Event fetches full metadata for a specific session—enough to answer "how many RSVPs for the gala?" in a shared chat. This works if you run fewer than 20 events per quarter and your team already uses Switchy for donor comms. If you're running 50+ events or need complex segmentation by tag, you'll hit the pagination ceiling fast and want a dedicated BI tool instead. For small teams where event data lives in conversation, this MCP closes the loop without adding another login.

Community manager event prep

Pulling event rosters into team planning threads

A two-person community team runs monthly meetups and needs to check registration counts before finalizing venue size. The Get Events tool surfaces your upcoming schedule, and Get Event grabs the attendee snapshot for a specific meetup—all inside the Switchy workspace where you're already coordinating with your venue contact. This MCP saves the tab-switching if your event volume is under 10 per month and you don't need custom reporting. Once you cross into weekly events or multi-city schedules, the three-tool scope gets limiting and you'll want Humanitix's native dashboard or a Zapier pipeline. For lean teams where event logistics are part of the daily chat flow, this keeps the context in one place.

Volunteer coordinator tag-based filtering

When Get Tags helps segment volunteer event types

A volunteer coordinator managing five recurring programs (food bank, tutoring, park cleanups) tags each event type in Humanitix and needs to quickly list "all tutoring sessions this month" without opening the web app. The Get Tags tool surfaces your tag taxonomy, and Get Events lets you filter by those tags in a Switchy thread while you're messaging volunteers. This workflow clicks if you have a stable tag structure and fewer than 15 active event types. If your tagging changes weekly or you need cross-tag analytics, the MCP's read-only scope won't support it and you'll need a spreadsheet export. For coordinators who live in chat and run predictable event calendars, this MCP brings the roster into the conversation.

Frequently asked

What does the Humanitix MCP do in Switchy?

It pulls event data from your Humanitix ticketing account into Switchy's AI workspace. You can query event details, list all upcoming events with pagination, and retrieve tags you've assigned to events. The MCP doesn't create or modify events — it's read-only access to your event catalog and metadata.

Do I need admin access to connect Humanitix?

You need an API key from Humanitix, which typically requires account owner or admin permissions to generate. The key authenticates all requests, so whoever connects it in Switchy will expose their account's event data to the team. Check your Humanitix account settings to confirm you can create API keys before starting setup.

Can the Humanitix MCP create events or manage ticket sales?

No. It only reads event information — you can't create events, edit details, or process ticket transactions through this MCP. If you need to update an event or check real-time sales, you'll still use the Humanitix dashboard directly. This integration is for surfacing event data in AI conversations, not replacing your ticketing workflow.

How is this different from just logging into Humanitix?

The MCP lets your team ask natural-language questions about events without opening the Humanitix dashboard. Instead of manually searching for an event ID or filtering by tag, you ask Switchy and it queries the API. It's faster for cross-referencing event data with other tools in your workspace, but you lose the visual calendar and sales analytics.

Who on the team should connect the Humanitix account?

Whoever manages your event listings and has API key access. Since the MCP exposes all events and tags to anyone in the Switchy workspace, connect it only if your team already shares event data internally. If you run private or draft events, consider whether you want those visible to the entire workspace before connecting.

Data last verified 607 hours ago.Sources aggregated hourly to weekly. See docs/architecture/model-directory.md.