Whova MCP Server
Related Servers
Alternatives to Whova MCP Server
No user-submitted related servers found.
Related Servers
- 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.-
- 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
- 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
- AlicenseAqualityBmaintenanceEnables connecting over 1,000 apps once, self-hosted and with encrypted credentials, so that Claude, Codex, Cursor, Copilot and dozens of other AI agents can call their APIs as MCP tools. Agents authenticate with per-agent tokens to get ready-made tools for every connected app, including app-specific actions like searching mail or sending messages.1118 npm5MIT
- AlicenseNot gradedqualityBmaintenanceProvides a single MCP server endpoint that lets AI agents connect to many real third-party services through OAuth, with user approvals, activity logs, scoped read/write grants, and one-tap access removal.AGPL 3.0
- 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.-
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.