Read Eventzilla events, tickets, orders, attendees and users; open or close ticket sales. Hosted by usefulapi — connect from Claude, Cursor, or any MCP client.
Team and Enterprise: an Owner adds the connector for the organization first.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"eventzilla": {
"url": "https://eventzilla.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"eventzilla": {
"type": "http",
"url": "https://eventzilla.usefulapi.io/mcp"
}
}
}Other MCP clients (Windsurf, Cline, Zed and more): add the URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser. Do not add an Authorization header: see Before you connect.
The login page asks for your Eventzilla API key.
Create it in Eventzilla under Settings → Developers → API Credentials. Your key is used only to call the Eventzilla API on your behalf; it is never shown to anyone.
Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Eventzilla API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
| Tool | Type | What it does |
|---|---|---|
eventzilla_list_events | read | List events List the events in the Eventzilla account: id, title, dates and times, venue, status, tickets sold and total, categories and the public URL. Use the id (and dateid) in the other tools. Filter by status and category name. GET /events. |
eventzilla_get_event | read | Get event One event by id: title, description, dates, time zone, venue, status, tickets sold/total, URL, categories. GET /events/{eventid}. |
eventzilla_list_event_transactions | read | List event transactions List the orders (transactions) of one event: order reference, checkout id, date, amount, number of tickets and status. Read-only. GET /events/{eventid}/transactions. |
eventzilla_list_event_attendees | read | List event attendees List the attendees (registrations) of one event: name, ticket type, barcode, check-in status, order reference and answers to registration questions. The API returns the whole list in one reply (no paging). GET /events/{eventid}/attendees. |
eventzilla_list_ticket_types | read | List ticket types List the ticket types of one event: id, title, price, quantity, sales window and limits, plus its donation ticket options (donation_options). GET /events/{eventid}/tickets. |
eventzilla_list_categories | read | List event categories List the event categories (names to use as the category filter in eventzilla_list_events). GET /categories. |
eventzilla_get_attendee | read | Get attendee One attendee by id: name, ticket type, barcode, check-in status, order reference, registration answers. GET /attendees/{attendeeid}. |
eventzilla_get_transaction | read | Get transaction One transaction (order) by checkout id or order reference number: amount, ticket count, status, event date. Read-only. GET /transactions/{identifier}. |
eventzilla_list_users | read | List organizers List the account's organizer and sub-organizer users: name, company, contact details, time zone, user type. GET /users. |
eventzilla_get_user | read | Get organizer One organizer or sub-organizer by user id. GET /users/{userid}. |
eventzilla_toggle_event_sales | write | Turn ticket sales on or off WRITE: publish (status true) or unpublish (status false) ticket sales of one event. Unpublishing stops attendees from buying tickets on the event page; publishing starts public sales again. Existing orders are not touched and no money moves through this tool. Idempotent. POST /events/togglesales. |
eventzilla_usage_status | Usage status (free-tier meter) Report the caller's current free-tier usage this month: calls used, monthly limit, remaining, and whether the cap is reached. Read-only; does not count against the meter. | |
eventzilla_request_feature | Request a missing feature Tell usefulapi that the user needs something the Eventzilla tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter. | |
eventzilla_upgrade | Upgrade to Pro (unlimited) Subscribe to the Pro plan for UNLIMITED Eventzilla tool calls (the free tier caps monthly usage). Choose monthly ($9/month) or yearly ($90/year — 2 months free) billing. Returns a Stripe Checkout link to open in your browser; after payment your account upgrades automatically. Does not count against the meter. | |
eventzilla_cancel_subscription | Cancel the Pro subscription Cancel the caller's Eventzilla Pro subscription at the end of the paid period (no refund for the current period; unlimited calls continue until then, then the free tier applies). Requires confirm: true. Run eventzilla_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 100 tool calls / month |
| Proper account | $9/mo · $90/yr | Unlimited |
Pro covers this Eventzilla server only. Subscribe with eventzilla_upgrade (it returns a Stripe Checkout link). Cancel any time with eventzilla_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running eventzilla_upgrade before then undoes the cancel. Or write to [email protected].
No. usefulapi is an independent service. It is not affiliated with or endorsed by Eventzilla. The server calls the Eventzilla API with your own Eventzilla access, so it sees only the data that your account can see.
The login page asks for your Eventzilla API key. See Before you connect for where to find it.
No. Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Eventzilla API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the Eventzilla API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in Eventzilla.
Yes, if you approve it. 1 of the 11 Eventzilla tools can create or change data. The other 10 are marked read-only. Most MCP clients ask you to approve a tool call before it runs.
The Free plan gives 100 tool calls / month. Pro costs $9/mo or $90/yr, with unlimited tool calls, for this Eventzilla server only. Run eventzilla_usage_status to see how many calls you used.
Ask the AI to run eventzilla_upgrade: it returns a Stripe Checkout link. To cancel, run eventzilla_cancel_subscription. Pro continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with eventzilla_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, Cursor, VS Code, Windsurf and others.
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.