Whova MCP Server
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Whova MCP Server List the Whova events I can manage and their agendas."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Whova API and MCP server for ChatGPT and Claude
Whova has no public API documentation or official MCP server according to the live Cotlet.dev integration page (checked 24 October 2026). Cotlet.dev connects ChatGPT, Claude and other AI agents to your own Whova organizer account through a hosted MCP server with 11 workflow tools. Announcements, speaker emails and attendee additions ask for approval by default.
What you can ask
List the Whova events I can manage.
Read the agenda and draft a revised schedule after a speaker change.
List new registrations since yesterday and include every page of results.
Show attendees who have not checked in.
Draft an announcement about the room change and ask me before sending.
Read the Sponsors and exhibitors section of the released post-event report.
Related MCP server: OWA Exchange MCP Server
Connect in 2 minutes
Get your API key at https://cotlet.dev/app and export it as COTLET_API_KEY.
ChatGPT
Settings > Apps & Connectors > Create. Use https://cotlet.dev/mcp/v1/connect with OAuth.
Claude
Settings > Connectors > Add custom connector. Use https://cotlet.dev/mcp/v1/connect.
Claude Code
claude mcp add --transport http cotlet https://cotlet.dev/mcp/v1 --header "Authorization: Bearer $COTLET_API_KEY"Cursor
Copy .cursor/mcp.json from this repo into your project:
{
"mcpServers": {
"cotlet": {
"url": "https://cotlet.dev/mcp/v1",
"headers": {
"Authorization": "Bearer ${COTLET_API_KEY}"
}
}
}
}Run it locally (stdio)
This repo is a real MCP server. It speaks MCP over stdio, lists its Whova tools without any key, and forwards every tool call to the hosted Cotlet.dev server. The hosted URL above stays the recommended way. Use this when your client only starts local servers.
Clone this repository and run python3 whova_agent.py serve with COTLET_API_KEY set.
Or with Docker:
docker build -t whova-mcp .
docker run -i --rm -e COTLET_API_KEY whova-mcpThe local server exposes seven browser helper tools, distinct from the 11 hosted workflow tools described on the live page.
Local tools: whova_guide, whova_status, whova_open, whova_read, whova_click, whova_type, whova_close. Without COTLET_API_KEY a tool call answers: "Set COTLET_API_KEY. Get a key at https://cotlet.dev/app".
Command line
Python 3.10+, nothing else to install. Run from this repo:
export COTLET_API_KEY="your-key"
python3 whova_agent.py connect # ready config for Claude Code, Cursor, ChatGPT
python3 whova_agent.py status # is Whova ready in your Cotlet.dev account
python3 whova_agent.py guide # Whova screens and sign-in link
python3 whova_agent.py read # open Whova, read the page, close the browser
python3 whova_agent.py tools # list Cotlet.dev tools
python3 whova_agent.py serve # start the stdio MCP server (same as no argument)Questions from Whova users
Does Whova have an official API or MCP server?
The live Cotlet.dev page, checked 24 October 2026, reports no public API documentation or official MCP server. Cotlet.dev provides an independent hosted connection to your own organizer account.
Which account do I need?
Use your own Whova organizer account with permission to manage the event. Sign in through its Cotlet Cloud Browser and enable Whova for agents.
Which changes ask for approval?
Announcements, speaker emails and attendee additions ask for approval by default. Agenda edits run directly. Approval settings can be changed per tool.
Can an agent request my post-event report?
Request it under Tools > Report in Whova first. Once Whova releases it, Cotlet.dev can read its sections.
Is this an official Whova integration?
No. Cotlet.dev is independent and is not affiliated with Whova.
Live integration
Whova tools and connection guide
Start free: https://cotlet.dev/signup?app=whova&utm_source=github&utm_medium=readme&utm_campaign=whova
Available Tools
7 toolswhova_clickB
Click a numbered element on the current Whova page.
Inputs: element (required).
whova_closeA
Close the Whova browser session when the work is done, so credits stop running.
Inputs: no named parameters.
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.
Inputs: task.
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.
Inputs: url.
whova_readA
Read the current Whova page: its text and numbered buttons, links and fields.
Inputs: element.
whova_statusA
Check that your Cotlet.dev account and Whova are ready: account, credits and Whova connection.
Inputs: no named parameters.
whova_typeB
Type text into a numbered field on the current Whova page.
Inputs: text (required), element (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Related MCP Connectors
Connect any AI agent to 1,000+ apps and 27,000+ actions through one remote MCP server (OAuth).
MCP server for your apps' tools and custom tools, plus hosted AI agents and approval-gated workflows
MCP server connecting AI agents to 100+ apps (Gmail, Slack, Notion, GitHub) via one-click OAuth.
Unified MCP Server is a remote MCP connector for AI agents and vertical AI products that provides access to 22,000+ authorized SaaS tools across 400+ integrations and 24 categories directly inside LLMs (Claude, GPT, Gemini, Cohere). Tools operate only on explicitly authorized customer connections, enabling agents to safely read and write against live third-party systems.
Related MCP Servers
- AlicenseAqualityCmaintenanceEnables creating and managing events on RealEvents, including listing public events, registering attendees, and updating event details, all from MCP-compatible AI assistants.674 npm1MIT
- AlicenseAqualityCmaintenanceMCP server for any Microsoft Exchange / OWA deployment. Gives LLM agents access to email, calendar, directory search, folders, availability, and meeting analytics via 30 tools.3050 PyPI12MIT
- FlicenseNot gradedqualityDmaintenanceMCP server to read and write events on chouseisan.com (Chouseisan), a Japanese scheduling tool, using unofficial HTTP protocol. Enables creating events, fetching schedules, and managing responses via AI agents or CLI.-
- FlicenseNot gradedqualityCmaintenanceAn OAuth-secured remote MCP server (22 tools) that lets Claude, ChatGPT, and Codex search All-In Summit attendee profiles, explore the live agenda, check sessions and meetings, detect scheduling conflicts, and export a calendar. Account-changing actions are only prepared for review, with the user confirming each request in the browser before any event API call is made.-