Event Management
Bizzabo MCP connector
The Bizzabo connector brings events, sessions, speakers, contacts and accounts to Claude, ChatGPT, Cursor and the Elaichi Agent, so each person can ask about and update their events inside their own Bizzabo access, with every action logged.
-
How it connects. Connects with an API key. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
53 tools
How to connect
How to connect Bizzabo to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Bizzabo once
-
Open Connections, choose Add connection, and pick Bizzabo.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste a Bizzabo API key. One person generates a token in Bizzabo and pastes it once. Everyone else works through Share with, and never sees it.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Bizzabo MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Bizzabo MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
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.
Bizzabo MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect Bizzabo to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with Bizzabo through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Events
Set up the next event from a template
Ask for the event templates in Bizzabo, create the new event from the one that fits, and check its goals are in place before anyone starts building the agenda.
-
Content
Build the agenda one session at a time
Create sessions for a track, pull up any session by name, and remove the ones that fell through, without opening the agenda builder.
-
Speaker relations
Chase speaker tasks before the deadline
See which speaker tasks are still open, approve the bios and headshots that came in, decline what needs another pass, and invite the speakers who have not been asked yet.
-
Marketing
Clean up contacts after a campaign
Add the contacts that came through a partner list, fix a misspelled name or email, and pull a contact's record while a colleague is still on the phone.
-
Sales
See which accounts show up at your events
List the accounts and contacts in Bizzabo and ask which companies are represented at an upcoming event before planning meetings on site.
-
Operations
Publish speakers and attach recorded talks
Set a speaker's visibility once their bio is approved and attach the pre-recorded video to a session ahead of the virtual day.
Try asking
- “Which speaker tasks are still open for the summit?”
- “Create a session called Opening keynote on day one of the summit”
- “List the accounts with contacts registered for next month's event”
AI tools
Bizzabo tools for your AI agents
53 tools are ready to call through Elaichi's MCP endpoint the moment you connect Bizzabo, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
See it in Elaichi
What connecting Bizzabo gets you
6 screens from the product, each doing one job for your Bizzabo account.
The agent
Ask about your events in plain language.
Sessions, speakers and contacts answered from live Bizzabo records, not last week's export.
- events
- sessions
- speakers
- contacts
Ask Elaichi to work across your apps.
Which speaker tasks are still open for the summit?
Create a session called Opening keynote on day one of the summit
List the accounts with contacts registered for next month's event
Also runs in Claude, ChatGPT or Cursor
MCP clients
One endpoint puts Bizzabo in every client.
Claude, ChatGPT and Cursor connect over OAuth, with no SDK and no shared API key.
ElaichiMCP clientsClaude
ChatGPT
Cursor
Copy the endpoint
Tool catalog
53 Bizzabo tools, ready without any code.
Events, sessions, speakers, contacts and accounts, covered before anyone writes a line.
- List all Bizzabo events
- Get single Bizzabo event by ID
- Create a Bizzabo event
- List all Bizzabo event templates
ElaichiToolsToolboxes
Each team gets its own Bizzabo toolbox.
Content works on sessions, sales on accounts, and neither sees the other's tools.
- Events
- Content
- Speaker relations
- Marketing
ElaichiToolboxesShared connections
Share one Bizzabo connection, never the key.
Teammates work through the connection while the API key stays with whoever connected it.
- Global events
- Field marketing
- Content
- Speaker relations
ElaichiConnectionsAudit log
Every Bizzabo action names who did it.
When, who, what happened and which session or contact, in one append-only log.
- When
- Who
- What happened
- Type
ElaichiAudit logLaunching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule runs the speaker chase for you.
Open speaker tasks are fetched, grouped, drafted into a digest, approved, then posted to Bizzabo.
Bizzabo digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch events
Bizzabo
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
Bizzabo
Queued
Collections and dashboards
Bizzabo health, computed without asking a model.
Four metrics, fourteen days of events created and a team breakdown, refreshed on schedule.
Bizzabo health
Refreshed 4 minutes ago · every 15 minutes · from the events collection
Events
1,284 ↓ 12%
Sessions
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Events created
Last 14 days
By team
Share of activity
Global events 34%
Field marketing 27%
Content 21%
Speaker relations 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect Bizzabo to Claude?
Connect Bizzabo in Elaichi first, then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Bizzabo connects with an API key, so the sign-in step is pasting a key from your Bizzabo account into Elaichi. There is no OAuth application to register and no client ID or secret to generate.
Does Bizzabo work with ChatGPT and Cursor as well as Claude?
Yes. Once Bizzabo is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. You connect Bizzabo once and every client picks it up.
What can an AI agent actually do with my Bizzabo data?
With Bizzabo connected, an agent can list your events and create a new one from a template, build and remove sessions, and attach a pre-recorded video to a session. It can look up speakers, invite them, set their visibility, and approve or decline their outstanding tasks. It can also add, update or remove contacts and list the accounts behind them. Short, concrete asks such as "which speaker tasks are still open for the summit" work better than long sentences.
Does connecting Bizzabo give the AI access to every event and contact?
No. Every call to Bizzabo runs as the person who signed in, so an agent sees only the events, sessions, speakers and contacts that person can already reach in Bizzabo. Elaichi can narrow that access further with roles and restrictions, and it can never widen it.
Can I stop an agent from deleting or changing things in Bizzabo?
Yes. Restrictions in Elaichi work per action, so you can allow reading events and sessions in Bizzabo while blocking deleting a session or removing a contact. A restricted action is never advertised to Claude, ChatGPT or any other client, so no prompt can reach it.
What happens to a Bizzabo connection when someone leaves?
Offboarding a person in Elaichi ends their access to Bizzabo at once, in every client they used. A shared Bizzabo connection keeps working for everyone else on the team. If you want Bizzabo gone entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client at the same time.
Does the Bizzabo MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Bizzabo 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.
Put Bizzabo in front of your team
14 days on Gold, no credit card. Connect it once and pick what each team can call.
- Works with
-
and any other MCP client, or the Elaichi Agent.
- When the trial ends
- Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.