# WebinarIgnition connector

WebinarIgnition runs a webinar on the host's own WordPress site: invitation and reminder emails,
registration page, live or evergreen room, the offer in the room, and the numbers afterwards
(registrants, show-up rate, funnel, revenue from WooCommerce). This server is the connector
between an AI client and that site. Nothing is written to a site without the host's OK.

This address: https://mcp.webinarignition.com/

## Which address for which client

- Any app that can sign in (OpenChamber, Cursor, VS Code, Claude Code)
  Address: https://mcpapp.webinarignition.com/
  Sign-in: OAuth 2.1 with PKCE, dynamic client registration, loopback redirect
  How: Paste the address in the MCP settings. The client opens its sign-in window, you approve on your own WordPress site, done.
- Claude (web, desktop, app directory)
  Address: https://mcp4claude.webinarignition.com/
  Sign-in: OAuth 2.1 with PKCE
  How: Add it as a custom connector. Claude shows the connect card and repeats the call after you approve.
- ChatGPT
  Address: https://mcp.webinarignition.com/
  Sign-in: none (submitted app)
  How: Install the app from the ChatGPT directory. No address to paste.
- A client that cannot sign in at all (script, n8n, plain HTTP)
  Address: https://mcpapp.webinarignition.com/
  Sign-in: device key
  How: In a chat that is already connected, call wi_create_app_key and paste the key as Authorization: Bearer wi_app_… (90 days, revocable).

## What a client reads here

- https://mcp.webinarignition.com/.well-known/oauth-protected-resource (RFC 9728: which server protects this resource)
- https://mcp.webinarignition.com/.well-known/oauth-authorization-server (RFC 8414: the endpoints)
- https://mcp.webinarignition.com/.well-known/mcp/server-card.json (name, version, tools, whether a sign-in is needed)
- https://mcp.webinarignition.com/docs (setup, tool list, what is stored)
- https://mcp.webinarignition.com/health (version and state, no personal data)

## How the sign-in works

A site tool without a sign-in answers 401 with a WWW-Authenticate header carrying a
resource_metadata pointer. The client opens its sign-in window, the host approves on their own
WordPress site (no password is seen or stored), the client repeats the same call. A client
without a sign-in window carries a key from wi_create_app_key as Authorization: Bearer
wi_app_… (90 days, revoked with wi_revoke_app_key). A wrong or expired key answers 401, never
example numbers.

## The plugin

The connector is the managed way. A WordPress site can also be its own MCP server with the
free plugin: https://wordpress.org/plugins/webinar-ignition/. That server describes itself at
https://YOUR-SITE/llms.txt.

## Product

https://webinarignition.com/