Whova MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| COTLET_API_KEY | Yes | Your Cotlet.dev API key, obtained at https://cotlet.dev/app. Set it as the environment variable COTLET_API_KEY (or pass it as a Bearer token in the Authorization header). Required for the stdio/local server; without it a tool call answers: "Set COTLET_API_KEY. Get a key at https://cotlet.dev/app". |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Whova through Cotlet.dev. Call whova_guide first. Set COTLET_API_KEY (https://cotlet.dev/app).
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| whova_guideA | How to work in Whova (manage event agendas, attendees, registrations, announcements, speaker messages and post-event reports): its screens and the sign-in link. Call this first. |
| whova_statusA | Check that your Cotlet.dev account and Whova are ready: account, credits and Whova connection. |
| whova_openB | Open a Whova page in your signed-in Cloud Browser (default https://whova.com) to work with manage event agendas, attendees, registrations, announcements, speaker messages and post-event reports. |
| whova_readA | Read the current Whova page: its text and numbered buttons, links and fields. |
| whova_clickB | Click a numbered element on the current Whova page. |
| whova_typeB | Type text into a numbered field on the current Whova page. |
| whova_closeA | Close the Whova browser session when the work is done, so credits stop running. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool maps to a clearly distinct step in a browser-automation workflow: onboarding (whova_guide), readiness check (whova_status), session lifecycle (whova_open/whova_close), and page interaction (whova_read/whova_click/whova_type). The guide vs. status distinction is spelled out explicitly, so misselection is unlikely.
Every tool uses the same 'whova_' prefix followed by a short, single verb (guide, status, open, read, click, type, close). The pattern is uniform and predictable throughout.
Seven tools is a tight, well-scoped set for a browser-driven event-management assistant; each one covers an indispensable primitive (session start/stop, read, click, type) plus orientation and health-check helpers. Nothing appears redundant.
The surface covers the core loop of open → read → click/type → close, which is enough to drive most Whova workflows. However, common browser operations like navigating to a specific URL, scrolling, selecting from dropdowns, or waiting for page load are absent, forcing agents to approximate them via click/type.