Connect Your AI Assistant to ManyMeet
ManyMeet has a built-in MCP server that lets AI assistants like Claude read your webinar data, analyze attendance, and help you optimize your events.
This guide shows how to connect using OAuth — the recommended method for Claude Desktop, ChatGPT, Gemini, GitHub Copilot, and similar apps. If you need programmatic access (automation, CI/CD), see Connect with an API Key instead.
For step-by-step screenshots of each app, see the visual walkthrough.
Connection details
- MCP server URL:
https://app.getmanymeet.com/mcp/ - Authentication: OAuth 2.0 with dynamic discovery (RFC 8414 + RFC 9728)
- Transport: Streamable HTTP
Most AI assistants auto-detect the OAuth endpoints — just enter the URL and the app handles the rest.
What you need
- A ManyMeet account
- An AI assistant that supports MCP — Claude Desktop, Claude Cowork, Claude Code, Cursor, Windsurf, or similar
How to connect
The steps below use Claude Desktop as an example, but the process is similar for all apps. For app-specific instructions with screenshots, see the visual walkthrough for Claude, ChatGPT, Gemini, Microsoft Copilot, and GitHub Copilot.
- Open your AI assistant's settings.
- Look for Connections, MCP Servers, or Integrations.
- Add a new connection with the URL:
https://app.getmanymeet.com/mcp/ - Your browser will open with a ManyMeet login page.
- Enter your email. ManyMeet will send you a login link (the same way you normally log in).
- Click the link in your email. The connection completes automatically.
That's it. Your AI assistant now has read access to your webinar data.
Claude Code (terminal)
Run this command:
claude mcp add --transport http manymeet https://app.getmanymeet.com/mcp/
Then authenticate with /mcp in Claude Code. Your browser will open for the same login flow described above.
What your AI assistant can see
Once connected, your AI assistant has read-only access to:
- Hosts — which hosts you have access to and their configuration
- Webinars — topics, schedules, email sequences, registration settings
- Runs — scheduled and completed webinar sessions, Zoom meeting details
- Registrations — who registered, attended, or missed
- Analytics — attendance funnels, drop-off curves, minute-by-minute timelines
- Recordings — transcripts and chat logs
- Registrant journeys — a person's full history across your webinars
Your assistant cannot make changes to your account or webinars through this connection (write access will be available in a future update).
What to try first
Once connected, try asking your AI assistant:
- "Which hosts do I have access to?"
- "Show me the webinars for [host name]"
- "What was the attendance rate for my last webinar run?"
- "Analyze the drop-off pattern for run #12"
- "Show me the full journey for jane@example.com"
Disconnecting
To disconnect, remove the ManyMeet connection from your AI assistant's settings. This revokes the access token immediately.
Troubleshooting
- Login email not arriving? Check your spam folder. The email comes from the same address as your regular ManyMeet login links.
- Connection expired? ManyMeet tokens refresh automatically. If your session expires, your AI assistant will prompt you to re-authenticate.
- "Authorization failed"? The login link may have expired (10 minutes). Try connecting again from your AI assistant.