Ask your AI assistant about EventPass
Connect Claude, ChatGPT, Gemini, Grok, or Muse to EventPass and work with your events by conversation — sales, payments, attendees, and drafts.
How it works
- Connect — add the EventPass server to your AI assistant using the steps below for your assistant. The server address is
https://eventpass.aicloudconsult.com/api/mcp. - Sign in — your assistant opens EventPass sign-in. Approve the permissions it asks for (it can only see what you approve, and only your own organizations).
- Ask — talk to it like a person. It shows you a preview before doing anything that changes money or sends a message, and only acts after you approve it in the chat.
AI features are off by default and turned on per organization by the EventPass team, for Pro organizations and one-time founding-pilot setups. Writes are a second, separate switch — while they are off, your assistant can read but cannot change anything. You can also turn AI off for a single event from its edit page. If your assistant says AI is off for your organization, contact us to have it enabled. Turning AI off never blocks ticket sales — the public storefront always works.
Try asking
- “How are ticket sales going for my gala?”
- “Who still hasn't paid for the fundraiser?”
- “Create a draft event for our Diwali dinner on November 14.”
Writes always show a preview first — creating or publishing an event, confirming a payment, or sending a broadcast never happens without you approving it in the chat.
Set up your assistant
Pick your assistant below. Every path uses the same server and the same sign-in — you only set it up once.
Claude
Add EventPass as a custom connector in Claude, then ask it about your events in any chat.
In Claude, open Settings → Connectors → Add custom connector, paste the server URL, and sign in with EventPass when asked. Or add it from the command line:
claude mcp add --transport http eventpass https://eventpass.aicloudconsult.com/api/mcp
Claude is the first assistant we support, and the one we test against. It can read your sales and attendees, and — after you approve each preview in the chat — create drafts, publish, confirm payments, and send broadcasts.
ChatGPT
Add EventPass as a custom MCP server in ChatGPT (web), then use it in a chat.
ChatGPT starts read-only for most plans: it can read your sales and attendees, but writes (creating events, confirming payments, sending broadcasts) may not be available on your plan. We do not promise ChatGPT writes until we have verified them on a live account.
In ChatGPT on the web, add a custom MCP server with this URL and sign in with EventPass:
https://eventpass.aicloudconsult.com/api/mcp
Gemini
Add EventPass as a custom app in the Gemini app, or from the Gemini CLI.
The Gemini app path needs a personal Google account, is US-only, and needs Keep Activity turned on — Canadian organizers may be excluded from the app path and should use the CLI instead.
In the Gemini app: Settings → Connected Apps → Custom apps, add the server URL. Or from the command line:
gemini mcp add eventpass https://eventpass.aicloudconsult.com/api/mcp
Grok
Add EventPass as a custom MCP connector in Grok.
In Grok, open grok.com/connectors → New Connector → Custom, paste the server URL, and complete sign-in:
https://eventpass.aicloudconsult.com/api/mcp
Muse
Paste a prompt into Muse, or add the server to Muse Code.
In a Muse chat, paste this prompt:
Connect to my EventPass MCP server at https://eventpass.aicloudconsult.com/api/mcp as a custom connector, using OAuth. It is a remote MCP server over Streamable HTTP; the OAuth resource is https://eventpass.aicloudconsult.com/api/mcp. Sign in with my EventPass account when it asks, approve the permissions, and then list my organizations.
Muse saves it as a reusable connector. Your sign-in goes through Muse's secure prompt, never in the chat. The connection itself was verified on 2026-11-12: Muse's MCP client connected to EventPass, listed all 14 tools, and called a buyer tool and two organizer tools. You still sign in once, and the production server serves the full tool set only after the MCP rollout is deployed.
There is no Settings → Connectors form to use instead — the chat prompt above is the way in for Muse. For Muse Code, add the server to ~/.config/muse/settings.json and run muse mcp login. That path runs on your own machine and was not tested here.
{
"mcpServers": {
"eventpass": {
"url": "https://eventpass.aicloudconsult.com/api/mcp",
"transport": "streamable-http"
}
}
}Other assistants (Cursor, VS Code, Windsurf, Zed)
Anything that speaks MCP over Streamable HTTP can connect with this config.
{
"mcpServers": {
"eventpass": {
"url": "https://eventpass.aicloudconsult.com/api/mcp",
"transport": "streamable-http"
}
}
}What it can do
For buyers public
Anyone can use these — no sign-in needed.
listEventsList upcoming published events with starting prices.getEventFull details for one event: ticket types, availability, program, food vendors.createOrderPlace a ticket order. The buyer pays the organizer directly (e-Transfer, Zelle, or cash).findTicketsFind a buyer's orders and ticket links (needs the exact name + email or phone).
For organizers sign-in
Read your own organizations only, after you sign in and approve.
list_my_organizationsYour organizations, your role in each, and whether AI is enabled for it.list_my_eventsEvents in one of your organizations, newest first, filterable by status.get_sales_summaryConfirmed and pending orders, tickets sold, money collected and outstanding, by payment method.get_attendee_listAttendees for one event: holder, ticket type, check-in status. Paginated, no email/phone.get_pending_paymentsOrders still waiting for payment, oldest first, with contact details so you can follow up.get_checkin_statsIssued, checked-in, expected, and cancelled tickets, per ticket type.
Writes — always previewed first
Every write shows a preview of exactly what would happen and waits for your approval in the chat. Nothing here moves money — confirming a payment only records a manual payment the organizer already received. Writes are off by default per organization and are enabled only by the EventPass team; while they are off, reads keep working and writes are refused.
create_eventCreate a DRAFT event (never publishes). Preview first, then confirm.publish_eventPublish a draft event. Preview shows the date, prices, and plan gate; then confirm.confirm_pending_paymentRecord a manual payment received and confirm the order, issuing its tickets. Records a payment only — it never moves money.send_broadcastEmail every confirmed buyer for an event (max 200 recipients, 3 per hour). Preview the exact text first, then confirm.delete_draft_eventPermanently delete a DRAFT event with zero orders (test-draft cleanup). Preview first, then confirm.
Team sign-in
Manage your team by conversation. Owner/Admin only, and the same guards as the dashboard: only an Owner can grant the Owner role, the Owner can never be changed or removed, and you cannot change or remove yourself. Writes are previewed first, like the event writes above.
list_team_membersTeam members of one organization: name, email, role, and whether each is deactivated. Owner/Admin only.invite_team_memberAdd an existing EventPass user to the team. No new login is created here, and no password is ever taken. Preview first, then confirm.set_team_member_roleChange a team member's role. Only an Owner can grant the Owner role. Preview first, then confirm.deactivate_team_memberDeactivate a member: they lose access, but their record and orders are kept. Preview first, then confirm.reactivate_team_memberReactivate a deactivated member. Preview first, then confirm.remove_team_memberRemove a member permanently: their membership is deleted, their orders stay. Preview first, then confirm.
Your AI activity, visible to you
Every time your assistant does something through EventPass, it is written to your organization's AI activity log — who, which tool, and whether it worked. No attendee details are stored there. See your AI activity.