Cvent MCP connector
Connect Cvent to Elaichi and ask Claude, ChatGPT or Cursor about appointments, attendees, admission items and account user groups, with each person working inside their own Cvent access and 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.
How to connect
How to connect Cvent to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Cvent once
-
Open Connections, choose Add connection, and pick Cvent.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste a Cvent API key. One person generates a token in Cvent 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.
Cvent 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.
Cvent 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.
Cvent 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 Cvent 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 Cvent through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Events
Book attendee meetings before the doors open
Ask which appointment times and locations are still open for an event, then book the meeting in Cvent without leaving the chat.
-
Sales
Find out who wants to meet you
Pull the meeting interests and appointment attendees for an event so reps know who asked for time with the team before they arrive.
-
Operations
Move or cancel an appointment on the day
When a speaker runs late or a room changes, update the appointment in Cvent or remove it, and the schedule stays accurate.
-
Registration
Check what admission items an event offers
List the admission items set up for an event and the filters behind them, so the desk can answer attendee questions on the spot.
-
IT admin
Keep Cvent account user groups current
Create a user group, add or remove a person, or rename a group, with every change recorded against whoever asked for it.
-
Marketing
Summarize appointment activity across an event
Ask for the appointments booked at an event, grouped by type or location, to see which sessions and meeting formats drew the most interest.
Try asking
- “Which appointment slots are still open for the Chicago summit tomorrow?”
- “Book a 2pm meeting with Acme at the Hall B lounge.”
- “Who has asked to meet our sales team at this event?”
Compare
Elaichi vs Zapier MCP vs Composio for Cvent
All three can connect Cvent 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 Cvent tools | Allow or restrict single Cvent 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 Cvent 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, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
AI tools
Cvent tools for your AI agents
351 tools are ready to call through Elaichi's MCP endpoint the moment you connect Cvent, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Showing 250 of 351 Cvent tools here. Connect Cvent and call search_tools or tools/list over the MCP endpoint for the complete set.
See it in Elaichi
What connecting Cvent gets you
6 screens from the product, each doing one job for your Cvent account.
The agent
Ask about Cvent appointments in plain language.
Get answers from live Cvent appointments, attendees and admission items, no report to run.
- appointments
- attendees
- admission items
- user groups
Ask Elaichi to work across your apps.
Which appointment slots are still open for the Chicago summit tomorrow?
Book a 2pm meeting with Acme at the Hall B lounge.
Who has asked to meet our sales team at this event?
Also runs in Claude, ChatGPT or Cursor
MCP clients
One governed endpoint for Claude, ChatGPT and Cursor.
Connect Cvent once and every MCP client uses it, with no SDK and no shared key.
Copy the endpoint
Tool catalog
351 Cvent tools, ready with no custom code.
Appointments, attendees, admission items and user groups, covered without an engineer building anything.
- List all Cvent account user groups
- Create a Cvent account user group
- Get single Cvent account user group by ID
- Update a Cvent account user group by ID
Toolboxes
Every team gets its own Cvent toolbox.
Events, sales and IT each see the Cvent tools their work needs.
- Events
- Sales
- Marketing
- Registration
Shared connections
Teammates use Cvent without touching the API key.
One person connects Cvent, shares it with teams, and nobody else sees a credential.
- Events EMEA
- Field marketing
- Sales
- Registration desk
Audit log
Every Cvent action is logged with a name.
Who booked, moved or canceled which appointment, answered from one append-only log.
- When
- Who
- What happened
- Type
Launching 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 starts the work, a person approves.
New Cvent appointments are fetched, grouped, drafted into a digest, approved, then posted back.
Cvent digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch appointments
Cvent
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
Cvent
Queued
Collections and dashboards
Cvent health numbers, computed with no model.
Appointments created over 14 days, broken down by team, refreshed on a schedule.
Cvent health
Refreshed 4 minutes ago · every 15 minutes · from the appointments collection
Appointments
1,284 ↓ 12%
Attendees
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Appointments created
Last 14 days
By team
Share of activity
Events EMEA 34%
Field marketing 27%
Sales 21%
Registration desk 18%
FAQ
Frequently asked questions
How do I connect Cvent to Claude?
Two steps. In Elaichi, choose Cvent and paste in a Cvent API key; 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. Sign in to Elaichi when asked and Cvent appears in Claude.
Does Cvent work with ChatGPT and Cursor as well as Claude?
Yes. Once Cvent 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 Cvent once and every client picks it up.
What can an AI agent actually do with my Cvent data?
It can look up the appointments, attendees, available times and locations for a Cvent event, book, move or cancel an appointment, show the meeting interests people submitted, list the admission items for an event, and manage account user groups. Short, concrete asks such as "open slots for Thursday afternoon" work better than long paragraphs.
Does connecting Cvent give the AI access to everything in my Cvent account?
No. Every call runs inside the access of the person who connected Cvent, so the agent sees the events, appointments and user groups that person can see and nothing more. Elaichi can narrow that further with roles and restrictions, and it can never widen it beyond what Cvent itself allows.
Can I stop an agent from deleting or changing things in Cvent?
Yes. Restrictions in Elaichi apply per action, so you can allow reading Cvent appointments and attendees while blocking deleting appointments or editing user groups. A restricted action is never advertised to Claude, ChatGPT or Cursor, so no prompt can reach it.
What happens to a Cvent connection when someone leaves?
Offboarding the person in Elaichi ends their access to Cvent through every client at once. A Cvent connection shared with a team keeps working for everyone else. If you want Cvent gone entirely, disconnect it once in Elaichi and it disappears from Claude, ChatGPT, Cursor and every other client.
Does the Cvent MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Cvent 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 Cvent?
Yes. Both let Claude, ChatGPT or Cursor use Cvent. 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 Cvent call.
How is Elaichi different from Composio for Cvent?
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 Cvent: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Cvent 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.