WebinarIgnition

Official2 tools

by Tobias-Conrad · JavaScript

Tell it your webinar topic in one sentence — no sign-in. It builds the WordPress webinar.

Model Context Protocol (MCP) Server: com.webinarignition/mcp

The com.webinarignition/mcp MCP server supports building or creating a webinar from chat, covering the components needed for registration and follow-up communications. It includes generation of a registration page, invitation emails, and an evergreen funnel.

🛠️ Key Features

Build or create a webinar from chat
Registration page creation
Invitation emails generation
Evergreen funnel support

🚀 Use Cases

Creating a webinar workflow starting from chat input
Producing registration materials for webinar attendees
Sending invitation emails as part of the webinar setup
Setting up an evergreen funnel for ongoing webinar engagement

⚡ Developer Benefits

Uses a structured webinar creation flow (registration, emails, evergreen funnel)

⚠️ Limitations

No additional tool capabilities, configuration options, or counts were provided in the source data

Captured live from the server via tools/list.

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`. • handoff — returns a handover link carrying the collected data; needs `session_id` (or `known_facts`/`content`), optional `url`. • technik — returns the setup plan without a connected site. • frage — answers a product question (prices, limits, integrations); needs `text`. • status — technical state of the connector. Returns { error, message } when a required field is missing, and { question } when the user has choices to make.

Parameters22

was	string	optional	Which step to run. Defaults to start — the entry point. Only set it when you need a later step.
tool	string	optional	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.
args	object	optional	Only with was=ausfuehren: the arguments for that ability, shaped by its input_schema.
text	string	optional	What the host said (thema · weiter) or the question in the host's language (frage).
session_id	string	optional	From an earlier turn (weiter · texte · stand).
job_id	string	optional	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.
url	string	optional	The WordPress address (seite). With was=handoff: the host's WordPress address to point the handover link at.
content	string	optional	Only with was=handoff: finished text to carry over, if the session alone does not hold it.
rating	integer	optional	Only with was=handoff: the host's rating (1-10), if any.
language	string	optional	The language the host writes in.
known_facts	object	optional	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.
focus	string	optional	Only with was=start: what it should be about.
situation	string	optional	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.
type	string	optional	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.
custom_channel	string	optional	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.
invite_type	string	optional	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.
direction	string	optional	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.
skip_direction	boolean	optional	Only with was=texte: true when the host wants NO special angle — then it generates without an angle.
has_wordpress	boolean	optional	Only with was=start: true when the host already has a WordPress site.
has_wi	boolean	optional	Only with was=start: true when WebinarIgnition is already installed on the host's site.
has_mcp	boolean	optional	Only with was=start: true when the host already uses an MCP/connector — the connector normally sets this itself.
wants	array	optional	Only with was=start: what the host wants, as short keywords (e.g. "thema", "texte", "technik").

Raw schema

{
  "type": "object",
  "properties": {
    "was": {
      "default": "start",
      "description": "Which step to run. Defaults to start — the entry point. Only set it when you need a later step.",
      "type": "string",
      "enum": [
        "start",
        "thema",
        "weiter",
        "texte",
        "stand",
        "seite",
        "verbinden",
        "faehigkeiten",
        "ausfuehren",
        "trennen",
        "handoff",
        "technik",
        "frage",
        "status"
      ]
    },
    "tool": {
      "description": "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"
    },
    "args": {
      "description": "Only with was=ausfuehren: the arguments for that ability, shaped by its input_schema.",
      "type": "object",
      "propertyNames": {
        "type": "string"
      },
      "additionalProperties": {}
    },
    "text": {
      "description": "What the host said (thema · weiter) or the question in the host's language (frage).",
      "type": "string"
    },
    "session_id": {
      "description": "From an earlier turn (weiter · texte · stand).",
      "type": "string"
    },
    "job_id": {
      "description": "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.",
      "type": "string"
    },
    "url": {
      "description": "The WordPress address (seite). With was=handoff: the host's WordPress address to point the handover link at.",
      "type": "string"
    },
    "content": {
      "description": "Only with was=handoff: finished text to carry over, if the session alone does not hold it.",
      "type": "string"
    },
    "rating": {
      "description": "Only with was=handoff: the host's rating (1-10), if any.",
      "type": "integer",
      "minimum": -9007199254740991,
      "maximum": 9007199254740991
    },
    "language": {
      "default": "de",
      "description": "The language the host writes in.",
      "type": "string"
    },
    "known_facts": {
      "description": "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.",
      "type": "object",
      "propertyNames": {
        "type": "string"
      },
      "additionalProperties": {}
    },
    "focus": {
      "description": "Only with was=start: what it should be about.",
      "type": "string",
      "enum": [
        "thema",
        "texte",
        "technik",
        "fragen",
        "alles"
      ]
    },
    "situation": {
      "description": "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.",
      "type": "string"
    },
    "type": {
      "description": "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.",
      "type": "string"
    },
    "custom_channel": {
      "description": "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.",
      "type": "string"
    },
    "invite_type": {
      "description": "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.",
      "type": "string",
      "enum": [
        "list",
        "personal",
        "facebook",
        "whatsapp",
        "instagram",
        "linkedin",
        "telegram",
        "youtube"
      ]
    },
    "direction": {
      "description": "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.",
      "type": "string"
    },
    "skip_direction": {
      "description": "Only with was=texte: true when the host wants NO special angle — then it generates without an angle.",
      "type": "boolean"
    },
    "has_wordpress": {
      "description": "Only with was=start: true when the host already has a WordPress site.",
      "type": "boolean"
    },
    "has_wi": {
      "description": "Only with was=start: true when WebinarIgnition is already installed on the host's site.",
      "type": "boolean"
    },
    "has_mcp": {
      "description": "Only with was=start: true when the host already uses an MCP/connector — the connector normally sets this itself.",
      "type": "boolean"
    },
    "wants": {
      "description": "Only with was=start: what the host wants, as short keywords (e.g. \"thema\", \"texte\", \"technik\").",
      "type": "array",
      "items": {
        "type": "string"
      }
    }
  },
  "$schema": "http://json-schema.org/draft-07/schema#"
}

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.

Parameters3

session_id	string	required	The conversation id from an earlier turn — the session whose WordPress site is connected.
tool	string	required	The destructive ability name exactly as was="faehigkeiten" reported it, e.g. webinarignition_delete_campaign or webinarignition_delete_webhook. Slashes and hyphens are accepted too, but the site publishes underscores.
args	object	optional	The arguments for that ability, shaped by its input_schema.

Raw schema

{
  "type": "object",
  "properties": {
    "session_id": {
      "type": "string",
      "description": "The conversation id from an earlier turn — the session whose WordPress site is connected."
    },
    "tool": {
      "type": "string",
      "description": "The destructive ability name exactly as was=\"faehigkeiten\" reported it, e.g. webinarignition_delete_campaign or webinarignition_delete_webhook. Slashes and hyphens are accepted too, but the site publishes underscores."
    },
    "args": {
      "description": "The arguments for that ability, shaped by its input_schema.",
      "type": "object",
      "propertyNames": {
        "type": "string"
      },
      "additionalProperties": {}
    }
  },
  "required": [
    "session_id",
    "tool"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}

README.md7 KBView on GitHub

WebinarIgnition MCP Server

MCP Badge

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`
mail	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

code

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:

code

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 status
GET /.well-known/mcp/server-card.json — published capability card
GET /openapi.json — HTTP schema

Install

Tools (2)

wi_webinarwi_webinar_delete

Remote endpoint

Streamable HTTP

Hosted server - connect over the network, no local install.

url

https://mcp.webinarignition.com/?src=registry

Add to VS Code Add to Cursor

claude_desktop_config.json

json

{
  "mcpServers": {
    "mcp": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.webinarignition.com/?src=registry"
      ]
    }
  }
}

Desktop config is stdio-only; this bridges via mcp-remote. Native remote: Settings > Connectors.

WebinarIgnition

Model Context Protocol (MCP) Server: com.webinarignition/mcp

🛠️ Key Features

🚀 Use Cases

⚡ Developer Benefits

⚠️ Limitations

wi_webinar

wi_webinar_delete

WebinarIgnition MCP Server

Install

Tools

Connector tools (always available)

Site tools (offered by the connected WordPress site)

What the tools do to your site

Architecture

Connecting

Sources

Health

Links

Install

Remote endpoint

Related servers