Bring Virtual Events
to Claude Desktop
Learn how to connect HeySummit 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 HeySummit MCP Server?
Connect your HeySummit account to any AI agent and take full control of your online event management and summit workflows through natural conversation.
What you can do
- Event Orchestration — List and manage multiple online summits and retrieve detailed event metadata
- Attendee Management — Register new participants and track existing attendee lists to keep your audience engaged
- Content Organization — Manage event talks, categories, and speaker profiles programmatically to maintain a perfect schedule
- Speaker Coordination — Retrieve detailed speaker information and bios to automate professional event promotion
- Real-time Monitoring — Check registration status and event progress directly through your agent for instant reporting
How it works
1. Subscribe to this server
2. Retrieve your API Key from the HeySummit Event Setup dashboard (API Settings)
3. Start managing your online summits from Claude, Cursor, or any MCP client
No more manual attendee tracking or schedule updates through complex web forms. Your AI acts as your dedicated event coordinator.
Who is this for?
- Event Organizers — scale attendee management and speaker coordination for large-scale online summits
- Marketing Teams — automate lead registration and track event performance through natural language queries
- Community Managers — keep your members updated on event schedules and speaker lineups without leaving your workspace
Built-in capabilities (12)
Register a new attendee
Get event details
Get account information
Get speaker details
Get talk details
List event attendees
List event categories
List all events
List event speakers
List event talks
List event tickets
Update an existing event
Why Claude Desktop?
Claude Desktop is the definitive way to connect HeySummit 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
HeySummit in Claude Desktop
HeySummit and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect HeySummit 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 HeySummit in Claude Desktop
The HeySummit 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
HeySummit for Claude Desktop
Every tool call from Claude Desktop to the HeySummit MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Where do I find the Event ID for a specific summit?
You can use the list_events tool to retrieve a list of all summits in your account. Each entry will include its unique numeric ID and name.
Can the agent handle speaker details and bios?
Yes! The list_speakers tool allows your agent to fetch professional profiles, bios, and social links for all speakers associated with an event.
How do I register a new attendee programmatically?
Use the create_attendee tool by providing the event_id, email, and name. The agent will confirm the registration status immediately.
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.
