# Eventzilla MCP connector

Connect Eventzilla to Elaichi and Claude, ChatGPT, Cursor or any MCP client can list your events, check attendees in, manage ticket types and review orders and transactions, each person inside their own Eventzilla access.

Source: https://elaichi.ai/connectors/eventzilla/

## Facts

| | |
| --- | --- |
| Application | Eventzilla |
| Category | Event Management |
| AI tools | 20 |
| Authentication | Connects with an API key |
| Bring your own OAuth app | No |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once Eventzilla is connected

- List attendees for Saturday's gala who haven't checked in yet
- Create an early bird ticket type for the spring conference
- Show this week's transactions for the product launch event

## Connect Eventzilla in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick Eventzilla.
2. Optionally set Share with, then press Connect.
3. Paste an Eventzilla API key. One person generates a token in Eventzilla and pastes it once. Everyone else works through Share with, and never sees it.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Eventzilla tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## Eventzilla MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
4. Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

## Eventzilla MCP connector for ChatGPT

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
3. Leave Authentication on OAuth, then tick the risk acknowledgement.
4. Press Create, then sign in and approve.

Works on the web today. The plugin directory lives at chatgpt.com/plugins.

## Eventzilla MCP connector for Cursor

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## Connect Eventzilla to any MCP client

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Only Read is granted by default, which is not enough to call a Eventzilla tool. Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Grant Read and Run tools. Think hard before granting Delete, which reaches into connected apps and cannot be undone.

## What teams do with Eventzilla through Elaichi

### Open ticket sales when the venue confirms

Events. Ask the agent to turn sales on for the autumn conference the moment the contract is signed, and turn them off again when the room is full.

### Check attendees in at the door

Registration desk. Type a name, see the matching Eventzilla attendee and their order, and mark them checked in without leaving the conversation.

### Add an early bird ticket type

Marketing. Create a new ticket type with its price and quantity, then raise the price or extend the cap later with a single ask.

### Cancel or confirm an order on request

Support. When a registrant writes in, find their Eventzilla order, confirm it if payment landed or cancel it if they cannot attend.

### Place a complimentary order for a speaker

Operations. Create a checkout order for the keynote speaker, fill in their details, prepare it and confirm it so a ticket lands in their inbox.

### Reconcile transactions after the event closes

Finance. Pull every transaction for the product launch, check a single payment against the bank statement and summarize the total before the books close.

## Elaichi vs Zapier MCP vs Composio for Eventzilla

All three can connect Eventzilla to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

| What to check | Elaichi | Zapier MCP | Composio |
| --- | --- | --- | --- |
| Where the AI connects | One address for the whole organization. Endpoint: https://api.elaichi.ai/mcp | A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Eventzilla tools | Allow or restrict single Eventzilla tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Eventzilla call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | $15 per user per month. | 2 tasks per successful call. | Billed per tool call. |

Sources: Zapier MCP [docs](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### How do I connect Eventzilla to Claude?

Two steps. In Elaichi, pick Eventzilla and paste in your Eventzilla API key from your account settings, there is no OAuth application to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude signs you in through Elaichi and Eventzilla is ready.

### Does Eventzilla work with ChatGPT and Cursor as well as Claude?

Yes. Once Eventzilla is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, the Elaichi Agent and any other MCP client. You connect Eventzilla once and every client picks it up.

### What can an AI agent actually do with my Eventzilla data?

It can list your Eventzilla events and their categories, open or close ticket sales, create and update ticket types, and look up any attendee or check them in at the door. It can also create, prepare and confirm checkout orders, cancel or confirm existing orders, and pull transactions for an event. Short, concrete asks such as "check in Maria Lopez for the gala" work better than long paragraphs.

### Does connecting Eventzilla give the AI access to my whole Eventzilla account?

No. Every call runs as the person who signed in, so the agent can only reach the Eventzilla events, attendees and orders that person already has access to. Elaichi can narrow that further, for example to read only or to specific actions, but it can never widen it beyond what Eventzilla itself allows that person.

### Can my team share one Eventzilla connection?

Yes. One organizer connects Eventzilla in Elaichi and shares the connection with a team, and nobody else ever sees or handles the API key. Each teammate still signs in to Elaichi as themselves, so the audit log records who checked an attendee in or canceled an order.

### Can I stop an agent from canceling orders or changing ticket types in Eventzilla?

Yes. Restrictions in Elaichi apply per action, so you can allow reading Eventzilla events and attendees while blocking order cancellation or ticket type changes. A restricted action is never advertised to Claude, ChatGPT or any other client, so no prompt, however worded, can reach it.

### What happens to an Eventzilla connection when someone leaves?

Offboarding that person in Elaichi ends their access to Eventzilla through every client at once. If they shared an Eventzilla connection with a team, the connection keeps working for everyone else. Disconnecting Eventzilla once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client at the same time.

### Does the Eventzilla MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Eventzilla is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

### Is Elaichi an alternative to Zapier MCP for Eventzilla?

Yes. Both let Claude, ChatGPT or Cursor use Eventzilla. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Eventzilla call.

### How is Elaichi different from Composio for Eventzilla?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Eventzilla: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

## All 20 Eventzilla tools

Every tool below is callable through https://api.elaichi.ai/mcp once Eventzilla is connected, subject to the toolbox it is in and the restrictions on the caller.

- **Get single Eventzilla event by ID** (Get). Get a single Eventzilla event by id. Returns: id, title, description, currency, start_date, start_time, end_date, end_time, dateid (needed for checkout), time_zone, tickets_sold, tickets_total, status, url, logo_url, venue, categories. Required: id.

- **List all Eventzilla events** (List). List events in the Eventzilla account, optionally filtered by status (live, draft, unpublished, completed) or category. Returns event records with id, title, description, currency, start_date, start_time, end_date, end_time, dateid, time_zone, tickets_sold, tickets_total, status, url, venue and categories. Paginate with limit and offset.

- **Eventzilla events togglesales** (Action). Turn ticket sales on or off for an Eventzilla event (publish or unpublish sales). Returns: eventstatus. Required: event_id, status.

- **List all Eventzilla event categories** (List). List the event categories available for the authenticated Eventzilla account. Returns each category as a record with its category name (e.g. Business, Conferences, Networking, Training).
- **Create a Eventzilla event ticket type** (Create). Create a free ticket type for an Eventzilla event with its name, description, quantity, sales window, per-order limits and visibility. Returns the created ticket type with ticket_type_id and the submitted fields. Required: event_id and all ticket type fields except additional_instructions and unlock_code.

- **List all Eventzilla event ticket types** (List). List the ticket types (and donation options) configured for an Eventzilla event. Returns ticket type records with id, title, description, price, quantity_total, tickets sold, sales start/end dates and times, limits, visibility and box-office flags. Required: event_id.

- **Update a Eventzilla event ticket type by ID** (Update). Update a free ticket type of an Eventzilla event. All ticket type fields must be sent again except additional_instructions and unlock_code. Returns the updated ticket type. Required: event_id, id (the ticket type id).

- **Eventzilla event orders cancel** (Cancel). Cancel a pending or completed order for an Eventzilla event, recording the organizer's comments. Returns: ordercancel (status message). Required: event_id, checkout_id, comments.

- **Eventzilla event orders confirm** (Action). Confirm a pending order for an Eventzilla event (for example an offline or pay-later order), optionally emailing the buyer. Returns: orderconfirm (status message). Required: event_id, checkout_id, comments.

- **Eventzilla checkout orders confirm** (Action). Confirm an Eventzilla checkout order after it has been filled, setting its payment status and optionally emailing the confirmation. Returns the order with checkout_id, transaction_ref, totals, transaction_status, confirmation_email_sent and currency. Required: event_id, event_date_id, checkout_id, payment_status.

- **Create a Eventzilla checkout order** (Create). Start an Eventzilla checkout order by reserving ticket types and quantities for an event date, optionally with a discount code. Returns the order with checkout_id, transaction_ref, totals, currency and the reserved tickets (ticket_price_id per ticket). Next call fill, then confirm. Required: event_id, event_date_id, ticket_types.

- **Eventzilla checkout orders fill** (Action). Fill an Eventzilla checkout order with the buyer details, the attendee details and question answers for each reserved ticket, and the chosen payment option. Returns the order with checkout_id, transaction_ref, totals and tickets. Required: event_id, event_date_id, checkout_id, payment_id, buyerdetails, tickets.

- **Eventzilla checkout orders prepare** (Action). Prepare a checkout for an Eventzilla event date: returns the ticket types on sale with prices, limits and availability, the registration questions, payment options, and whether discounts and tax apply. Call this first, then create, fill and confirm the order. Required: event_id, date_id.

- **Eventzilla attendees checkin** (Action). Check an attendee in to an Eventzilla event by ticket barcode, or revert a check-in. Returns the attendee's first_name, last_name, eventtitle, orderref, email and the resulting status. Required: barcode, eventcheckin.

- **Get single Eventzilla attendee by ID** (Get). Get a single Eventzilla attendee by id, including ticket, order and check-in details. Returns: id, first_name, last_name, email, ticket_type, bar_code, is_attended, transaction_ref, transaction_status, event_id, title, buyer names, promo_code, questions. Required: id.

- **List all Eventzilla attendees** (List). List attendees of an Eventzilla event with their ticket, order and check-in details. Returns attendee records with id, first_name, last_name, email, ticket_type, bar_code, is_attended, transaction_ref, transaction_status, transaction_date, transaction_amount, buyer names, promo_code and question answers. Required: event_id.

- **List all Eventzilla event transactions** (List). List Eventzilla transactions for a specific event. Returns: transaction_ref, checkout_id, transaction_date, transaction_amount, tickets_in_transaction, event_date, transaction_status, user_id, event_id, title, email, buyer_first_name, buyer_last_name, promo_code, payment_type, comments, transaction_tax, transaction_discount, eventzilla_fee. Required: event_id. Max 100 per page.
- **Get single Eventzilla transaction by ID** (Get). Get a single Eventzilla transaction by its checkout ID or order reference number. Returns: transaction_ref, refno, checkout_id, transaction_date, transaction_amount, transaction_total, transaction_tax, transaction_discount, eventzilla_fee, currency, transaction_status, tickets_in_transaction, tickets, event_date, event_id, title, user_id, email, buyer_first_name, buyer_last_name, promo_code,…
- **Get single Eventzilla user by ID** (Get). Get details of a specific Eventzilla user by id. Returns the user object including id, username, first_name, last_name, email, timezone, and user_type. Required: id (user/organizer identifier).
- **List all Eventzilla users** (List). List Eventzilla users (organizers and sub-organizers). Returns an array of user records with id, username, first_name, last_name, email, and user_type.