Bring Webinars
to Claude Desktop
Learn how to connect ON24 to Claude Desktop and start using 12 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the ON24 MCP Server?
Connect your ON24 account to any AI agent and take full control of your digital event orchestration and audience engagement through natural conversation. ON24 is the leading platform for webinars and virtual environments, and this integration allows you to retrieve webinar metadata, manage attendee registrations, and analyze participation intelligence directly from your chat interface.
What you can do
- Webinar & Event Orchestration — List all managed webinars and retrieve detailed event metadata programmatically to ensure your digital marketing calendar is always synchronized.
- Registrant Lifecycle Management — Enroll new attendees and monitor registration lists directly from the AI interface to track campaign reach and conversion.
- Audience & Participation Intelligence — Access and monitor attendee analytics and elite-level engagement metadata via natural language to drive better event ROI.
- Hub & Experience Control — List your organization's hubs and target experiences using simple AI commands to maintain a clear overview of your digital presence.
- Operational Monitoring — Track system responses and manage survey metadata to ensure your attendee feedback loops are always optimized.
How it works
1. Subscribe to this server
2. Enter your ON24 Client ID, Access Token Key, and Access Token Secret from your integration settings
3. Start managing your virtual events from Claude, Cursor, or any MCP-compatible client
No more manual logging into dashboards to check registration counts. Your AI acts as a dedicated event manager or digital marketing coordinator.
Who is this for?
- Event Marketers — quickly retrieve registration summaries and monitor attendee engagement without switching apps.
- Demand Generation Teams — automate the retrieval of lead metadata and track conversion from digital events via natural conversation.
- Developers — integrate real-time webinar data and attendee analytics directly within the chat.
Built-in capabilities (12)
Create a new webinar
Check account status
Get attendee engagement data
Get high-level Elite analytics
Get webinar details
List recently deleted events
List Engagement Hubs
List webinar registrants
List survey answers
List Target experiences
List all webinars
Register a participant for a webinar
Why Claude Desktop?
Claude Desktop is the definitive way to connect ON24 to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 12 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.
- —
Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available
- —
Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface
- —
Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions
- —
Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network
ON24 in Claude Desktop
ON24 and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect ON24 to Claude Desktop 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.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for ON24 in Claude Desktop
The ON24 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 12 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Claude Desktop 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.
* 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
How Vinkius secures
ON24 for Claude Desktop
Every tool call from Claude Desktop to the ON24 MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can my AI automatically find the registration count for a specific webinar?
Yes! Use the get_webinar tool with the Event ID. Your agent will respond with complete metadata for the webinar, including total registrants and event status in seconds.
How do I find my ON24 Client ID and Tokens?
Log into ON24, navigate to Platform Tools > Integrations > API Tokens, and click 'Provision a New API Access Token'. You will find your Client ID, Token Key, and Token Secret there.
Does this work with EU data centers?
This integration currently targets the primary ON24 API (api.on24.com). For EU-hosted accounts requiring api.eu.on24.com, ensure your Client ID is associated with the global integration gateway.
How does Claude Desktop discover MCP tools?
When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.
What happens if the MCP server is temporarily unavailable?
Claude Desktop handles disconnections gracefully. if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.
Can I connect multiple MCP servers simultaneously?
Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.
Is there a limit on the number of tools per server?
Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.
Does Claude Desktop support Streamable HTTP transport?
Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL. Claude auto-negotiates the transport protocol.
Server not appearing after restart
Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).
Authentication error
Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.
Tools not showing in chat
Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting. wait a few seconds.