Bizzabo MCP connector
The Bizzabo connector brings events, sessions, speakers, contacts and accounts to Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent, so each person can ask about and update their events inside their own Bizzabo access, with every action logged.
- App credentials
- Free 14-day trial
- No credit card
Which speaker tasks are still open for the summit?
Working in Bizzabo with Elaichi
-
List all Bizzabo events
-
Get single Bizzabo event by ID
-
List all Bizzabo event templates
How to connect Bizzabo to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
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 Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
Use --scope project instead to share it with the repository through .mcp.json.
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. 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.
Bizzabo MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
4
Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
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.
What teams do with Bizzabo through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Bizzabo is logged.
-
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”
What connecting Bizzabo gets you
6 screens from Elaichi, each doing one job for your Bizzabo account.
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, Cursor or Microsoft Copilot
The agent
Ask about your events in plain language.
Sessions, speakers and contacts answered from live Bizzabo records, not last week's export.
Copy the endpoint
AI apps
One endpoint puts Bizzabo in every client.
Claude, ChatGPT, Cursor and Microsoft Copilot connect over OAuth, with no SDK and no shared API key.
Tool catalog
53 Bizzabo tools, ready without any code.
Events, sessions, speakers, contacts and accounts, covered before anyone writes a line.
Toolboxes
Each team gets its own Bizzabo toolbox.
Content works on sessions, sales on accounts, and neither sees the other's tools.
Shared connections
Share one Bizzabo connection, never the key.
Teammates work through the connection while the API key stays with whoever connected it.
Audit log
Every Bizzabo action names who did it.
When, who, what happened and which session or contact, in one append-only log.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Workflows, collections and live dashboards come with the Black plan.
Bizzabo digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
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 Jake Morgan
Approve Deny -
Post the digest
Bizzabo
Queued
Workflows
A schedule runs the speaker chase for you.
Open speaker tasks are fetched, grouped, drafted into a digest, approved, then posted to Bizzabo.
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%
Collections and dashboards
Bizzabo health, computed without asking a model.
Four metrics, fourteen days of events created and a team breakdown, refreshed on schedule.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Bizzabo
All three can connect Bizzabo 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.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Bizzabo tools | Allow or restrict single Bizzabo 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 Bizzabo 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 | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
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.
Questions, answered
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, Microsoft Copilot, 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 restricting deleting a session or removing a contact. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT or any other client cannot run it, whatever the prompt says.
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, Microsoft Copilot 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, Microsoft Copilot, 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 Bizzabo?
Yes. Both let Claude, ChatGPT or Cursor use Bizzabo. 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 Bizzabo call.
How is Elaichi different from Composio for Bizzabo?
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 Bizzabo: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Bizzabo in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot