
WebinarIgnition
Tell it your webinar topic in one sentence — no sign-in.
What it can do
What data it sees
Do you need an account
No: the server works without sign-in
Tell it your webinar topic in one sentence — no sign-in. It builds the WordPress webinar.
How to connect
How to connect WebinarIgnition to Claude
The server address to paste into Claude settings:
https://mcp.webinarignition.com/?src=registry
- Open Claude (claude.ai or the desktop app).
- Go to Settings → Connectors.
- Click Add custom connector.
- Paste the server address copied below into Remote MCP server URL and click Add.
- In a chat, click + → Connectors and switch the new connector on.
Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.
Authorization
After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.
How to connect WebinarIgnition to ChatGPT
The server address to paste into ChatGPT settings:
https://mcp.webinarignition.com/?src=registry
- Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
- Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
- Open Settings → Connectors and click Create.
- Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
- Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
- In a new chat open + → Apps/Connectors and enable the connector.
OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.
Authorization
On first use ChatGPT opens the service's sign-in window. Sign in and approve access.
How to connect WebinarIgnition to Cursor
The server address to paste into Cursor settings:
https://mcp.webinarignition.com/?src=registry
Fastest: click Open in Cursor below and confirm the prompt.
Manually:
- In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
- Paste the JSON copied below into
~/.cursor/mcp.json(per project:.cursor/mcp.jsonin the repo root). - Save the file. The server appears in the MCP list; authorize it there if asked.
Authorization
If the service needs sign-in, an authorize button appears next to the server in the MCP list.
Server tool list (2)
Raw names from tools/list. Only developers need these.
| wi_webinar | Tell it the webinar topic in one sentence — no sign-in, no setup. It picks the topic, produces the title, the invitation emails, the reminders and the registration page, and prepares the live, automated or evergreen room on the user's own WordPress site. Already have material — a website, a PDF, a flyer, a profile, a ChatGPT conversation with the topic and the host's own style? Send it with the first call as `known_facts` (facts and tone) and, for a web address, as the source the tool reads itself; the host then does not have to start from zero. Files and images are turned into text by you, the assistant — the tool reads web addresses only. `was` selects the step: • start — entry point; returns a question with tappable options. • thema — starts a conversation from the user's text; needs `text`. • weiter — continues a conversation; needs `session_id` and `text`. A result with ready=true means the texts can be written next with was=texte. • texte — writes the finished texts for a ready session; needs `session_id`. Optional: `job_id` to poll a running job, `direction` for an angle, `skip_direction`, `invite_type` (list, personal, facebook, whatsapp, instagram, linkedin, telegram, youtube), or type="custom" with `custom_channel` for any other channel. • stand — returns what the session has collected so far; needs `session_id`. • seite — checks a WordPress address for WebinarIgnition; needs `url`; returns state, next_action and next_url. • verbinden — connects the chat to the user's own WordPress; the first call needs `session_id` and `url` and returns a connect_url that the user opens in their own browser; a later call without `url` reports whether it went through. • faehigkeiten — lists the abilities of the connected site; needs `session_id`. • ausfuehren — runs one ability on the connected site; needs `session_id`, `tool` and `args`. Destructive abilities are not run here; the answer points to wi_webinar_delete. • trennen — drops the connection; needs `session_id`. • |
| wi_webinar_delete | Delete or replace something on the connected WordPress site — irreversible. Runs only an ability that is verified as destructive: delete a campaign, a webhook, registrants (single or all), the logs, the attendee questions, or the HC import that replaces a campaign. Writes abilities are not run here; use wi_webinar with was="ausfuehren" for those. Needs `session_id` and `tool`, optional `args`. Returns JSON. |