Connect to ManyMeet with an API Key
API keys give you programmatic access to ManyMeet's MCP server. Use them for automations, CI/CD pipelines, or when your AI tool doesn't support OAuth.
For interactive use with Claude Desktop or Cowork, OAuth is easier.
Step 1: Generate your API key
- Log in to your ManyMeet account.
- Go to your Profile settings.
- Under Agent Access, click Generate API Key.
- Copy the key immediately — it is shown only once.
Your key looks like: mm_aBcDeFgHiJkLmNoPqRsTuVwXyZ...
Keep it secret. Anyone with this key has read access to your webinar data.
Step 2: Connect your tool
Claude Code
claude mcp add --transport http manymeet https://app.getmanymeet.com/mcp/ \
--header "Authorization: Bearer mm_your_key_here"
Project config file (.mcp.json)
For sharing with a team (keys via environment variable):
{
"mcpServers": {
"manymeet": {
"type": "http",
"url": "https://app.getmanymeet.com/mcp/",
"headers": {
"Authorization": "Bearer ${MANYMEET_API_KEY}"
}
}
}
}
Set the environment variable before starting your tool:
export MANYMEET_API_KEY=mm_your_key_here
Direct HTTP (any language)
ManyMeet's MCP endpoint accepts standard HTTP POST with JSON-RPC:
curl -X POST https://app.getmanymeet.com/mcp/ \
-H "Content-Type: application/json" \
-H "Authorization: Bearer mm_your_key_here" \
-H "Accept: application/json, text/event-stream" \
-d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-03-26","capabilities":{},"clientInfo":{"name":"my-app","version":"1.0"}}}'
What the key gives you access to
API keys provide read-only access to all hosts your account can see:
- Host configurations and integration status
- Webinar settings, email schedules, registration rules
- Run details, Zoom links, attendance data
- Analytics: funnels, timelines, drop-off curves
- Recording transcripts and chat logs
- Registrant journeys across webinars
Revoking a key
Go to Profile > Agent Access and click Revoke. The key stops working immediately. You can generate a new one at any time.
Security notes
- Keys do not expire, but can be revoked at any time.
- Store keys in environment variables or secret managers — never commit them to version control.
- One key per account. Revoking a key invalidates it everywhere it was used.
- API keys provide the same access scope as your account's role (observer, admin, or owner).