Whova MCP Server
Agenda, attendees and announcements for your Whova event.
Barındırılan MCP Sunucusu
npx add-mcp 'https://cotlet.dev/mcp/v1/whova'Claude Code, Codex, Cursor ve daha fazlasına kurulur
Dokümantasyon
Cotlet · Integrations · How it works · Security · For developers · For automation agencies · Blog · API docs · Help center · Changelog · Contact · Pricing · Sign up
Whova API and MCP server: Let your AI agent run your Whova event.
Whova has no public API, no developer docs and no MCP server (checked 24 Oct 2026). Cotlet runs 11 Whova tools hosted, over MCP for agents and REST for scripts.
Bring Whova organizer events and registration data into your agent or event workflow. Connect through MCP or call REST from automation tools and scripts.
- Free 7-day trial, no card
- Unofficial, not affiliated with Whova
- Page: https://cotlet.dev/integrations/whova-api-mcp-server
Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by Whova. Whova is a trademark of its owner. If Whova's own integrations cover what you need, use them first.
What can you automate in Whova?
- Fix the agenda after a change
- Announce changes to attendees
- Email speakers their own slots
- List new registrations
- Add comp and VIP attendees
- Write sponsor recaps
Does Whova have an MCP server or an API?
- The Zapier app has 3 triggers (attendee list changed, order list changed, registration form answered) and 1 action, Create or Update Attendee. Zapier MCP offers the same.
- Native connectors to Eventbrite, Cvent, HubSpot and AMS tools such as MemberClicks only move registrations. The agenda, announcements, speaker email and the report stay in the dashboard.
- No Whova MCP server, CLI or API client on GitHub, and no n8n node.
| What you need | Whova + Zapier | Apify scraper | Cotlet |
|---|---|---|---|
| Read new registrations and attendees | When the list changes | No | Yes, when you ask |
| Move sessions or add new ones | No | No | Yes |
| Announcements and speaker emails | No | No | Yes, after your OK |
| Read the post-event report | No | No | Yes |
| Fixed for you when Whova changes | Yes | By its author | Yes |
Checked 24 Oct 2026. Sources: Whova on Zapier: triggers and actions, Whova: CRM and AMS integrations, other platforms through Zapier, Zapier MCP for Whova, Whova Terms of Use
How does Cotlet connect to Whova?
- Sign in to Whova. Use your own account in its Cotlet Cloud Browser.
- Choose MCP or REST. Connect your agent or create a Cotlet API key.
- Run your workflow. Ask your agent or send an HTTP request.
We never save your Whova password, and no announcement or speaker email goes out before you approve it.
Connect Whova to your agent or workflow
Use MCP with your AI agent, or HTTP requests in n8n, Make, Zapier and scripts. Follow the MCP setup below or jump to the REST guide.
- Enable Whova for agents. Sign up, log in to your Whova organizer account in its Cloud Browser and press Enable for agents.
- Add the Cotlet address. Paste https://cotlet.dev/mcp/v1 into the MCP or connector settings of your agent.
- Sign in or paste a key. Chat apps sign you in to Cotlet; editors and scripts take an API key from the console.
Prefer one connector for all your apps? https://cotlet.dev/mcp/v1 carries Whova and every other app you enabled. Added Whova after connecting? Refresh the connector.
Claude:
Settings > Connectors > Add custom connector
URL: https://cotlet.dev/mcp/v1/connect
Claude Code:
claude mcp add --transport http cotlet-whova \
https://cotlet.dev/mcp/v1 \
--header "Authorization: Bearer $COTLET_API_KEY"
ChatGPT:
Settings > Apps & Connectors > Create
MCP server URL: https://cotlet.dev/mcp/v1/connect
Authentication: OAuth
Cursor:
// ~/.cursor/mcp.json
{
"mcpServers": {
"cotlet-whova": {
"url": "https://cotlet.dev/mcp/v1",
"headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" }
}
}
}
Codex:
# ~/.codex/config.toml
[mcp_servers.cotlet-whova]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"
n8n:
MCP Client Tool (inside an AI Agent)
Transport: HTTP Streamable
URL: https://cotlet.dev/mcp/v1
Auth: Bearer, <your key>
Tool: whova_read
Make, Zapier:
Make: MCP Client > Call a tool
Zapier: MCP Client by Zapier > Run Tool
Server URL: https://cotlet.dev/mcp/v1
Token: <your key>
Tool: whova_write
How to use the Whova REST API
Create your Cotlet API key
Sign in to your Whova organizer account in its Cotlet Cloud Browser and enable the app for agents. Use event IDs from events that account can manage.
Create a Cotlet API key with access to Whova and its read operations. Store it as COTLET_API_KEY in your environment or automation platform's credential store.
Make your first Whova API request
cURL: list_events:
curl "https://cotlet.dev/api/v1/whova/events?status=all" \
-H "Authorization: Bearer $COTLET_API_KEY"
Read events and page event records
A successful REST call puts the tool output in result. This illustrative response excerpt omits call IDs, messages and credit details.
Illustrative response excerpt:
{
"status": "success",
"app": "whova",
"tool": "list_events",
"result": {
"events": [
{
"event_id": "284611",
"name": "Northwind Summit 2026",
"start": "2026-11-21",
"end": "2026-11-23",
"status": "upcoming"
}
]
}
}
Read result.events for organizer event IDs. list_events has no cursor; status=all includes past and upcoming events.
For attendee and registration reads, pass returned next_cursor as cursor until null. Those lists default to 100 records per page, with a maximum of 500.
Keep event and filter inputs unchanged while paging. Preserve event time zones and compare record state as well as IDs when updating a report.
Post-event reports require a finished event and a report already requested under Tools > Report. A report that is not ready should be retried on your configured schedule.
Whova workflows for agents and automations
| Tool | Connect through | Example workflow |
|---|---|---|
| n8n | HTTP Request | Read organizer events and page registrations since your chosen date into a CRM export, remembering handled order IDs. |
| Python or Node.js | REST API | Combine event sessions and speakers into a briefing document, retaining session days, tracks and event time zones. |
| Make | HTTP > Make a request | Read a prepared Sponsors and exhibitors post-event report into a sponsor recap draft in your chosen destination. |
Send Authorization: Bearer <your Cotlet API key> in request headers. You configure the schedule, destination and record comparisons.
Cotlet reads Whova; your workflow steps write to your chosen destination. These HTTP workflows do not require a native Cotlet connector or a prebuilt template.
Python and Node.js can use the same HTTP requests without an AI agent. Keep access keys in credentials, outside shared workflow exports.
The API and MCP reference lists operations and inputs. The REST API guide explains authentication, errors and approvals.
Whova API endpoints and MCP tools
Events and the agenda
Times carry the event time zone. One call moves one session, so a block of four is four calls.
- List events (
list_events, read): Events you can manage as an organizer, with dates and status. - List sessions (
list_sessions, read): Agenda sessions with time, tracks, speakers and description, in agenda order. - Add session (
add_session, write): Add a session to the agenda in Session Manager. - Update session (
update_session, write): Change the time, tracks, speakers or description of an existing session.
Attendees and registrations
Up to 500 a page. Filter by ticket type, audience type or check-in status. Removing an attendee stays in the dashboard.
- List attendees (
list_attendees, read): Attendees of an event with email, company, ticket type, audience type and check-in status. - List registrations (
list_registrations, read): Registration orders with registrant, ticket type and order date, newest first. - Add attendee (
add_attendee, write, asks first): Create or update one attendee by name and email.
Announcements and speakers
Announcements go to every attendee by push and email. Speaker emails come from Whova, not your address.
- Send announcement (
send_announcement, write, asks first): Post an announcement for the attendees of an event. - List speakers (
list_speakers, read): Speakers of an event from the Speaker Center, with their sessions. - Message speakers (
message_speakers, write, asks first): Email all speakers of an event, or the ones you list, through Whova.
Post-event report
Readable once you have requested it under Tools > Report and Whova has released it.
- Get post-event report (
get_post_event_report, read): The post-event report of an event as text sections, available after the event ends.
Inputs, REST path and example response of every tool: https://cotlet.dev/integrations/whova-api-mcp-server#tools
Who can see my Whova session, and how do I revoke it?
- What we store. Your logged-in Whova profile, AES-256-GCM, in Finland. No password.
- What your agent gets. Whova tools only. No cookie, no login.
- What the session sees. What your organizer role sees: attendee emails, orders, the agenda, the report.
- What no tool touches. Ticket prices, payouts, refunds, badges and deleting attendees.
- If Whova logs you out. You get an email with a sign-in link. We never log in for you.
- How to cut access. Disable for agents, reset the browser or delete the key. The next call stops.
A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory (live results).
Approvals, undo and mistakes
- Matches speakers to sessions. From Speaker Center and the agenda, by title.
- Sets some aside. No session on the agenda or no email: listed, not sent.
- Shows one draft. With the number of speakers it will go to.
- Sends after your OK. One email per speaker, only their own sessions.
| Action | Undo |
|---|---|
| Send an announcement | No, push and email go out at once |
| Email speakers | No |
| Add or move a session | Yes, update it or delete it in Whova |
| Add an attendee | Edit with the same tool, remove in Whova |
3 of 11 tools ask first: announcements, speaker emails and new attendees. Agenda edits run straight away, because they reach no one directly and one more call puts the old time back.
MCP call:
{
"name": "send_announcement",
"arguments": {
"event_id": "284611",
"message": "The opening keynote has moved to Hall B. Doors open at 8:45."
}
}
REST:
curl -X POST https://cotlet.dev/api/v1/whova/events/284611/announcements \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"message":"The opening keynote has moved to Hall B. Doors open at 8:45."}'
Tool output:
{
"announcement_id": "ann_90314",
"event_id": "284611",
"status": "sent"
}
REST under /api/v1/whova takes the same tools for a nightly registrations export or a script. A report Whova has not released yet fails with a not-ready error and costs nothing. The tools table lists the REST path of each tool.
How much does the Whova MCP server cost?
About $15 a month for a conference of about 300 attendees in its busiest month, 2,500 credits. Whova bills you separately.
| Job | Calls | Credits |
|---|---|---|
| New registrations since yesterday, daily | 1 × 30 | 300 |
| Move sessions and announce it, weekly | 6 × 4 | 240 |
| Each speaker their own sessions, once | 22 × 1 | 220 |
| Add comp and VIP attendees, weekly | 5 × 4 | 200 |
| Who has not checked in, each event day | 1 × 2 | 20 |
| Sponsor recaps from the post-event report | 2 × 1 | 20 |
| Cloud Browser, 30 days | 1,500 | |
| Total | 2,500 |
- Free 7-day trial, no card
- 10 credits per successful call, MCP or REST
- 50 credits a day for the Cloud Browser
- Packs last 12 months, so one event a year fits one pack
Whova publishes no typical event size. 50,000+ events and 15 million users on its pricing page come to about 300 per event, our example. Attendee count barely moves the bill: one list call holds 500. Dollars at the $29 pack rate.
Whova MCP server on GitHub, Zapier or hosted: which to use
| Option | What it does | Where it stops |
|---|---|---|
| Whova on Zapier | Sends new attendees, orders and registration answers to other apps; creates or updates one attendee. | Nothing for the agenda, announcements, speakers or the report. |
| Whova Event Scraper on Apify | Sessions, speakers, sponsors and exhibitors from public Whova event pages, $0.001 a record, no login. | Public pages only and read only; it never sees your dashboard. |
| Whova's own connectors | Eventbrite, Cvent, RegFox, HubSpot and AMS tools such as MemberClicks sync registrations. | Registrations only. |
| GitHub | No Whova MCP server, CLI or API client; searches return interview take-home projects. | Nothing to run. |
Use Zapier when new registrants should land in a CRM. Use the Apify scraper to collect another event's public agenda. Use Cotlet when an agent should edit your agenda, message attendees and speakers, and read the report in your own account.
Who runs Cotlet
Take Group sp. z o.o. runs Cotlet. It is a software company registered in Poland, EU (VAT PL6342984273), in business since 2019, founded by Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Write to contact@cotlet.dev about the Whova tools.
Whova API and MCP: questions
Can I use the Whova API without an AI agent?
Yes. Call Cotlet's REST API from a script or an HTTP step in n8n, Make or Zapier with your Cotlet key. MCP is the alternative for AI agents; you do not need to connect an agent to use REST.
How do I get access?
Sign up free at https://cotlet.dev, open Whova under Integrations in the console and log in to your Whova organizer account in its Cloud Browser. The free trial starts when you sign up, no card.
How do I connect Whova to ChatGPT or Claude?
Sign up at cotlet.dev, log in to Whova once in its Cloud Browser and add Cotlet to ChatGPT or Claude, following the steps in your console. No API key is needed. ChatGPT and Claude then work in your Whova account through Cotlet, in their phone apps too.
What can ChatGPT do in Whova?
With Cotlet, ChatGPT, Claude and other AI agents handle jobs like these in Whova: update agenda sessions after a schedule change; import a program into the agenda; announce a change to all attendees. You ask in plain words, and anything that reaches other people waits for your OK first.
Do I need Zapier or a special Whova plan?
No. Cotlet works in your own Whova organizer account and does not use the Zapier app. You need an account that can manage the event in the Whova dashboard.
Does Whova have webhooks?
No. Whova sends no webhooks of its own; the three Zapier triggers are the only feed of changes. To catch new registrations, run your agent on a schedule with list_registrations and its since filter.
Can the agent request the post-event report?
No. Request it under Tools > Report in the Whova dashboard and answer Whova's short survey. Once Whova releases it, get_post_event_report reads it section by section.
Is the MCP server different from the REST API?
Only the way in. Both have the same 11 tools, inputs and answers, one API key and one price. Agents use MCP; scripts, cron jobs and HTTP steps use REST.
Is Cotlet affiliated with Whova?
No. Cotlet is independent and not affiliated with Whova.
Give your AI agents your signed-in browser.
Product: Integrations · How it works · Pricing · Security
Resources: Blog · API docs · Help center · Changelog · GitHub
Solutions: For developers · For automation agencies
Company: About · AI info: company facts · Contact
Legal: Terms of service · Privacy policy · Refund policy · Acceptable use · Cookie policy · DPA · Subprocessors
Elsewhere: Status page · Cotlet on GitHub · Cotlet on X · Cotlet on LinkedIn · Cotlet on Product Hunt · Cotlet on Crunchbase · Cotlet on SaaSHub
Cotlet.dev is built by Bart Krawczyk and Jake Slugocki, the founders of Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland. KRS 0000871398, NIP 6342984273, VAT EU: PL6342984273. About us
Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.