About WebinarIgnition
WebinarIgnition is an MCP server for planning and operating webinars with a WordPress site running WebinarIgnition. AI clients can draft webinar materials without a site, then connect one to manage registration pages, live rooms, funnels and related site functions.
Key features
- 01Plan webinars and draft invitation materials
- 02Create registration pages and webinar funnels
- 03Manage webinars and connected site settings
- 04Access leads, email and reporting tools
- 05Confirm site changes before execution
Use cases
- 01Draft a webinar title and invitation emails
- 02Set up a registration page and live room
- 03Review webinar leads and funnel reports
- 04Manage WooCommerce offers during webinars
MCP support
The hosted Streamable HTTP MCP server exposes webinar planning tools and, after connecting a WordPress site running WebinarIgnition, tools provided by that site. Site changes require confirmation; the server endpoint requires no authentication.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://mcp.webinarignition.com/?src=registryclaude mcp add --transport http com-webinarignition https://mcp.webinarignition.com/?src=registry{"mcpServers":{"com-webinarignition":{"type":"http","url":"https://mcp.webinarignition.com/?src=registry"}}}Open in Cursor{"servers":{"com-webinarignition":{"type":"http","url":"https://mcp.webinarignition.com/?src=registry"}}}Open in VS Code{"mcpServers":{"com-webinarignition":{"type":"http","url":"https://mcp.webinarignition.com/?src=registry"}}}{"mcpServers":{"com-webinarignition":{"serverUrl":"https://mcp.webinarignition.com/?src=registry"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
2| Parameter | Type | Required | Description |
|---|---|---|---|
| url | string | No | The WordPress address (seite). With was=handoff: the host's WordPress address to point the handover link at. |
| was | enum | No | Which step to run. Defaults to start — the entry point. Only set it when you need a later step.start | thema | weiter | texte | stand | seite | verbinden | faehigkeiten | ausfuehren | trennen | handoff | technik | frage | status |
| args | object | No | Only with was=ausfuehren: the arguments for that ability, shaped by its input_schema. |
| text | string | No | What the host said (thema · weiter) or the question in the host's language (frage). |
| tool | string | No | Only with was=ausfuehren: the ability name exactly as was=faehigkeiten reported it, e.g. webinarignition_create_webinar. Slashes and hyphens are accepted too, but the site publishes underscores. |
| type | string | No | Only with was=texte: invites (default), starter, or custom. custom = the invitation is for a channel that is NOT one of the eight built-in platforms — pass the channel name in custom_channel. A channel outside the eight built-ins is written as custom, not as one of the eight. |
| focus | enum | No | Only with was=start: what it should be about.thema | texte | technik | fragen | alles |
| wants | array | No | Only with was=start: what the host wants, as short keywords (e.g. "thema", "texte", "technik"). |
| has_wi | boolean | No | Only with was=start: true when WebinarIgnition is already installed on the host's site. |
| job_id | string | No | Only with was=texte: the job number from an earlier call, to check whether the texts are ready. Without job_id a new job is started; only one text job runs at a time. |
| rating | integer | No | Only with was=handoff: the host's rating (1-10), if any. |
| content | string | No | Only with was=handoff: finished text to carry over, if the session alone does not hold it. |
| has_mcp | boolean | No | Only with was=start: true when the host already uses an MCP/connector — the connector normally sets this itself. |
| language | string | No | The language the host writes in. |
| direction | string | No | Optional with was=texte: the angle/framing of the invitation (natural language), e.g. 'Zeitersparnis und Skalierung ohne neue Mitarbeiter' for an agency. If missing, the invitation is written at once without a special angle. |
| situation | string | No | Only with was=start or was=thema: what the host just said, in their own words. On was=start this also starts a real conversation (seeded with known_facts) instead of only showing the menu — use it when the host already wrote something about their webinar. |
| session_id | string | No | From an earlier turn (weiter · texte · stand). |
| invite_type | enum | No | Only with was=texte, when the invitation is for a specific platform: list = email list, personal = personal message, facebook = Facebook post, whatsapp = WhatsApp status, instagram = Instagram post, linkedin = LinkedIn post, telegram = Telegram channel, youtube = YouTube post.list | personal | facebook | whatsapp | instagram | linkedin | telegram | youtube |
| known_facts | object | No | Everything you already know — send it every turn so nothing is lost on a restart. On the FIRST call (was=start or was=thema) this is how a chat/assistant hands over what it already learned about the host (topic, audience, offer, style/tone) instead of making them repeat it. |
| has_wordpress | boolean | No | Only with was=start: true when the host already has a WordPress site. |
| custom_channel | string | No | Only with was=texte and type="custom": the exact name of the channel or format the invitation is for when it is not one of the eight built-in platforms — e.g. Xing, WeChat, Line, KakaoTalk, Viber, Threads, Mastodon, a guest article, or the host's own format. The text is then written for exactly this channel, not for a built-in platform. |
| skip_direction | boolean | No | Only with was=texte: true when the host wants NO special angle — then it generates without an angle. |
Details
From the project READMEWebinarIgnition MCP Server
Build and run WordPress webinars from a chat. One MCP server that puts WebinarIgnition inside any AI assistant — Claude, ChatGPT, Cursor and any MCP-capable client.
- Endpoint:
https://mcp.webinarignition.com/?src=registry - Transport: Streamable HTTP, MCP protocol 2025-06-18 (JSON-RPC 2.0)
- Auth: none. No sign-in, no API key, no install.
- Website: https://webinarignition.com
About this repository. This is the public source mirror of the hosted WebinarIgnition MCP server (
https://mcp.webinarignition.com). Two internal modules are intentionally not part of the mirror — the live-pricing reader and the product knowledge service — so the supported way to use the server is the hosted endpoint above. Everything else (MCP transport, funnel session engine, WordPress connection flow, outbound channel) is included.
Install
Remote MCP server (Streamable HTTP, no auth): https://mcp.webinarignition.com/?src=registry.
Agents: see llms-install.md for the exact steps.
Tools
mcp.so and other directories read this section. Listed below is what the connector exposes, and beneath it what the connected WordPress site offers.
Connector tools (always available)
| Tool | What it does | Kind |
|---|---|---|
wi_webinar | Plan, write and set up a webinar from a chat: topic, title, invitation emails, reminders, registration page, live room, evergreen funnel. Also answers product questions. Selects the step with was. | write |
wi_webinar_delete | Delete or replace something on the connected WordPress site. Irreversible. | destructive |
wi_webinar is a single entry point with guided steps (was): start (entry),
thema (topic), weiter (continue), texte (write the texts), seite (build the page),
verbinden (connect a WordPress site), faehigkeiten (what the site can do),
ausfuehren (run a site ability), fragen (product questions), alles, ready.
Site tools (offered by the connected WordPress site)
Once a WordPress site is connected, the connector exposes 71 tools across 11 areas. They are read live from the site, so the list always matches the installed version.
| Area | Count | Examples |
|---|---|---|
| webinar | 15 | wi_list_webinars, wi_get_webinar, wi_create_webinar, wi_funnel_stats, wi_run_preflight |
| config | 14 | wi_configure_webinar, wi_woo_offer_in_room, wi_configure_100ms, wi_configure_daily, wi_write_invite_texts |
| control | 10 | wi_master_switch, wi_room_switch, wi_list_questions, wi_answer_question, wi_get_prompter |
| gutenberg | 6 | wi_reg_page_blocks, wi_reg_page_edit, wi_media_search, wi_repair_registration_pages |
| 6 | wi_get_emails, wi_check_mail, wi_send_test_email, wi_resend_renotifications | |
| webhook | 6 | wi_list_webhooks, wi_upsert_webhook, wi_send_test_webhook, wi_read_webhook_history |
| leads | 5 | wi_list_leads, wi_export_leads, wi_import_leads_csv |
| colors | 3 | wi_get_colors, wi_update_colors, wi_sample_brand_colors |
| autoresponder | 2 | wi_set_autoresponder, wi_test_autoresponder |
| settings | 2 | wi_list_settings, wi_list_step_types |
| report | 2 | wi_list_report_types, wi_get_reports |
What the tools do to your site
Every site tool is labelled, so an assistant — and you — can tell them apart before anything runs:
- 28 read-only — lists, checks and reports. Nothing is touched.
(
wi_list_webinars,wi_get_webinar,wi_funnel_stats,wi_check_mail,wi_run_preflight, …) - 35 change something — creating, editing, publishing, sending. Each one is confirmed first.
(
wi_create_webinar,wi_configure_webinar,wi_set_autoresponder,wi_master_switch,wi_woo_offer_in_room, …) - 8 delete or reset — irreversible.
(
wi_delete_campaign,wi_delete_lead,wi_delete_all_leads,wi_reset_funnel,wi_delete_logs,wi_delete_webhook,wi_delete_all_questions,wi_import_hc_campaign)
Nothing changes on your site without your OK. A tool in the control scope requires
explicit confirmation; the host may grant it once when connecting, otherwise it is asked
on every call. Every write is snapshotted and audited.
Architecture
AI client (Claude / ChatGPT / Cursor / …)
│
└── WebinarIgnition MCP Server https://mcp.webinarignition.com
│
├── writes and reads webinars (connector, no site needed)
│
└── connected WordPress site → the real webinar, on your own hosting
Two doors exist by design, and both are optional:
- Connector only — plan the webinar, write the title, invitation emails and reminders, produce the registration copy. Works with no WordPress at all.
- Connected site — connect a WordPress site that runs WebinarIgnition, and the assistant builds the real thing: registration page, live room, evergreen schedule, WooCommerce offer in the room.
Connecting
Add the URL in your assistant's MCP settings:
https://mcp.webinarignition.com/?src=registry
In Claude: Settings → Connectors → Add custom connector, paste the URL, leave everything else as it is, save. Then open a new chat and write: "Build me a webinar for freelancers."
Works the same in Cursor, Claude Code, ChatGPT and any other assistant that speaks MCP.
The WordPress side is connected from inside the plugin (WebinarIgnition → AI connection), which returns a link the host opens in the browser to approve. No inbound access to the WordPress site is required — it polls the connector, so it also works behind a firewall or on shared hosting.
Sources
Directories list their own endpoint URL with an attribution parameter:
| Source | URL |
|---|---|
| MCP Registry | https://mcp.webinarignition.com/?src=registry |
| Smithery | https://mcp.webinarignition.com/?src=smithery |
| mcp.so | https://mcp.webinarignition.com/?src=mcpso |
| Glama | https://mcp.webinarignition.com/?src=glama |
| mcpbeat | https://mcp.webinarignition.com/?src=mcpbeat |
| ChatGPT app | https://mcp.webinarignition.com/?src=chatgpt |
| Claude connector | https://mcp.webinarignition.com/?src=claude |
Health
GET /health— service statusGET /.well-known/mcp/server-card.json— published capability cardGET /openapi.json— HTTP schema
Links
- Plugin on WordPress.org: https://wordpress.org/plugins/webinar-ignition/
- Product site: https://webinarignition.com
- AI Webinar Writer (no install): https://webinarignition.com/ai-webinar-writer/
- Agent & API guide: https://webinarignition.com/llms.txt
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.