Connect an AI assistant (MCP)

eWebinar has an MCP (Model Context Protocol) server, so an AI assistant such as Claude, Cursor or Claude Code can build and edit your webinars for you: settings, scheduling, the registration and thank-you pages, notifications, interactions, chat staffing, tracking scripts, integrations and series — plus the analytics and validation it needs to tell you why something isn't working.

It is a thin layer over the REST API v2. Every tool maps to a documented route and needs the same permission, so anything the assistant can do, you can do with curl. There is nothing to install and no local process to run.

Connect from Claude

In Claude (web, desktop or mobile), open Settings → Connectors, find eWebinar in the directory and click Connect. Claude sends you to eWebinar to sign in, you choose what to allow on the consent screen, and you are back in the chat. Ask it to "create a webinar from my recorded video" and let it lead.

If eWebinar isn't in your directory yet, add it as a custom connector instead: Settings → Connectors → Add custom connector, name it eWebinar and paste the server URL below. Nothing else is needed — the server tells Claude how to sign you in.

https://api.ewebinar.com/mcp

Connect from other assistants

The server speaks Streamable HTTP at the same URL and advertises its OAuth configuration, so any MCP client that supports OAuth connects with the URL alone.

  • Claude Code — in a terminal:claude mcp add --transport http ewebinar https://api.ewebinar.com/mcp
  • Cursor — Settings → MCP → New MCP server, or in .cursor/mcp.json:
    {"mcpServers":
       {"ewebinar": {"type":"http","url":"https://api.ewebinar.com/mcp"}}
     }
  • Anything else — point it at the URL; your client performs the sign-in.

Profile menu → Integrations → REST API in eWebinar generates these snippets for you, already filled in for your account.

What you allow

Signing in is the recommended way to connect. The assistant then acts as you: your name is on every change it makes, and you can withhold individual permissions on the consent screen. Which ones you see depends on your own role — you cannot grant an assistant something you cannot do yourself.

  • Read — see webinars, registrants, conversations and analytics. Always granted.
  • Edit drafts — change draft webinars, pages, notifications and interactions.
  • Publish — make a draft live, and change settings that apply immediately.
  • Integrations — connect and manage the team's integrations.
  • Registrants — read registrants and register attendees.
  • Delete registrants — delete a registrant.

What to expect

  • Drafts are safe. Edits stay on the draft until you publish, and every change is a revision the assistant can show you or revert. A good assistant summarizes what changed and asks before publishing.
  • Some things are live immediately. Moderators and chat staffing, tracking scripts, integrations and team settings are not part of the draft, so changes to those take effect at once. The assistant is told to confirm first.
  • It can tell you why something isn't working. Ask why a webinar isn't getting registrations, or why an email didn't send, and it has the tools and the guidance to work through it.
  • Read-only tools run without asking; anything that publishes, overwrites or deletes asks for confirmation.

Connecting without a browser

For a build, a cron job or a server — anywhere nobody can answer a sign-in prompt — use a team API key instead. Create one under Profile menu → Integrations → REST API, tick the same permissions as above, and send it as a bearer token:

Authorization: Bearer ew_api_...

A key belongs to the team rather than to a person, so changes made with one appear in revision history under the key's name. Keys can be revoked individually, and the secret is shown once. Two things a key cannot do: publish a webinar for the first time (first publish can start billing, so it needs a signed-in person), and call GraphQL — REST v2 and the MCP server are the supported surfaces for machines.

Full reference

The complete tool reference — every tool with the permission it needs, its arguments and the REST route behind it — is in the developer portal at api.ewebinar.com/docs/mcp (sign in with your eWebinar account to read it).

Troubleshooting

  • The client says it can't authenticate. Check the URL is exactly https://api.ewebinar.com/mcp, with no trailing path.
  • A tool returns 403. The connection was not granted that permission. Disconnect and reconnect, ticking the box you left unchecked; for a key, create a replacement with the permission ticked — an existing key cannot be widened.
  • Publishing is refused. If this is the webinar's first publish and it would change your plan, publish it once from the eWebinar dashboard.
  • Reading the whole registrant list returns 429. Ask the assistant to sync what changed since last time rather than the whole list.