3,400+ servers built on vurb.ts
Vinkius

Bring Event Planning
to Claude Code

Learn how to connect Cvent to Claude Code and start using 10 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.

MCP Inspector GDPR Free for Subscribers
Get Account DetailsGet Event DetailsList Active EventsList Available VenuesList Event AttendeesList Event SessionsList Event SpeakersList EventsList Registration TypesSearch Events By Filter
Cvent

What is the Cvent MCP Server?

Integrate Cvent, the world's leading event management platform, directly into your AI workflow. Manage your large-scale conferences, meetings, and seminars, track attendee lists, and monitor event sessions using natural language.

What you can do

  • Event Oversight — List and retrieve full details for all your upcoming and past events managed in Cvent.
  • Attendee Management — Quickly access registration lists and individual attendee profiles for specific events.
  • Session & Speaker Tracking — Monitor scheduled sessions and associated speakers across your event portfolio.
  • Venue Discovery — List and explore venues configured in your account for event planning.

How it works

1. Connect the Cvent integration to your AI assistant.
2. Authorize using your Cvent Client ID and Client Secret (found in the Cvent Developer Portal).
3. Manage your event lifecycle through intuitive conversation.

Who is this for?

  • Conference Organizers — Quickly check registration numbers and session details on the go.
  • Event Planners — Access venue and speaker information directly via chat during planning sessions.
  • Operations Teams — Monitor attendee lists and event statuses across large-scale portfolios.

Built-in capabilities (10)

get_account_details

Resolves account identifiers and organizational settings. Interacts with the account configuration boundary. Retrieve metadata for your Cvent account

get_event_details

Resolves event configuration, capacity, and lifecycle status. Touches the granular event planning and operational boundary. Get detailed information for a specific event

list_active_events

Resolves operational event records. Touches the event status management boundary. Quickly list only the events that are currently active

list_available_venues

Resolves venue IDs, names, and address metadata. Touches the venue and logistics boundary. List venues configured in the account

list_event_attendees

Resolves attendee identifiers and registration status. Touches the registration and participant management boundary. List all registered attendees for a specific event

list_event_sessions

Resolves session IDs, titles, and time slots. Touches the agenda and session scheduling boundary. List all sessions scheduled for an event

list_event_speakers

Resolves speaker names and biographies. Interacts with the speaker management and content boundary. List speakers associated with an event

list_events

Resolves event IDs, titles, start/end dates, and current status. Interacts with the core event management boundary. List all events in your Cvent account

list_registration_types

Resolves registration type identifiers and names. Interacts with the registration logic and pricing boundary. List available registration types for an event

search_events_by_filter

Resolves matching event records. Touches the indexed event search boundary. Search for events using a filter string

Why Claude Code?

Claude Code registers Cvent as an MCP server in a single terminal command. Once connected, Claude Code discovers all 10 tools at runtime and can call them headlessly. ideal for CI/CD pipelines, cron jobs, and automated workflows where Cvent data drives decisions without human intervention.

  • Single-command setup: claude mcp add registers the server instantly. no config files to edit or applications to restart

  • Terminal-native workflow means MCP tools integrate seamlessly into shell scripts, CI/CD pipelines, and automated DevOps tasks

  • Claude Code runs headlessly, enabling unattended batch processing using Cvent tools in cron jobs or deployment scripts

  • Built by the same team that created the MCP protocol, ensuring first-class compatibility and the fastest adoption of new protocol features

See it in action

Cvent in Claude Code

AI AgentVinkius
High Security·Kill Switch·Plug and Play
Why Vinkius

Cvent and 3,400+ other MCP servers. One platform. One governance layer.

Teams that connect Cvent to Claude Code through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.

3,400+MCP Servers ready
<40msCold start
60%Token savings
Raw MCP
Vinkius
Server catalogFind and host yourself3,400+ managed
InfrastructureSelf-hostedSandboxed V8 isolates
Credential handlingPlaintext in configVault + runtime injection
Data loss preventionNoneConfigurable DLP policies
Kill switchNoneGlobal instant shutdown
Financial circuit breakersNonePer-server limits + alerts
Audit trailNoneEd25519 signed logs
SIEM log streamingNoneSplunk, Datadog, Webhook
HoneytokensNoneCanary alerts on leak
Custom domainsNot applicableDNS challenge verified
GDPR complianceManual effortAutomated purge + export
Enterprise Security

Why teams choose Vinkius for Cvent in Claude Code

The Cvent MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 10 tools execute in hardened sandboxes optimized for native MCP execution.

Your AI agents in Claude Code only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

Cvent
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

The Vinkius Advantage

How Vinkius secures Cvent for Claude Code

Every tool call from Claude Code to the Cvent MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.

< 40msCold start
Ed25519Signed audit chain
60%Token savings
FAQ

Frequently asked questions

01

How do I get Cvent API credentials?

Log in to the Cvent Developer Portal, create a new application, and you will be provided with a Client ID and Client Secret for OAuth 2.0 authentication.

02

Can I see real-time registration counts?

Yes, you can use the list_event_attendees or get_event_details tools to see the latest registration data and attendee profiles.

03

Is the integration secure for enterprise data?

Absolutely. This integration uses official OAuth 2.0 protocols and only accesses the data exposed via your Cvent API application permissions.

04

How do I add an MCP server to Claude Code?

Run claude mcp add --transport http "" in your terminal. Claude Code registers the server and discovers all tools immediately.

05

Can Claude Code run MCP tools in headless mode?

Yes. Claude Code supports non-interactive execution, making it ideal for scripts, cron jobs, and CI/CD pipelines that need MCP tool access.

06

How do I list all connected MCP servers?

Run claude mcp in your terminal to see all registered servers and their status, or type /mcp inside an active Claude Code session.

07

Command not found: claude

Ensure Claude Code is installed globally: npm install -g @anthropic-ai/claude-code

08

Connection timeout

Check your internet connection and verify the Edge URL is reachable