WebinarIgnition MCP Server

by webinarignition Your server? Claim it

answering

WebinarIgnition is answering right now. Last checked 5 min ago. It exposes 19 tools. Last commit 22 Oct 2026.

Webinar leads, registrants and revenue from WordPress and WooCommerce, in the chat.

Uptime history 32 days of history · worst day 99%

32 days agonow

98.9%

Uptime 24h

180 of 182 checks

Tools

read from the server

354 ms

Response time

average over 24h

Stars

last commit 22 Oct 2026

What changed 142

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 26 September 2026. No other catalogue keeps this.

26 Oct a tool changed version4 times that day

26 Oct 2 tools changed the parameters they ask for wi_check_wordpress, wi_get_connector_status

26 Oct a tool description was rewritten wi_get_connector_status

25 Oct a tool changed version10 times that day

25 Oct 3 tool descriptions were rewritten wi_connect_wordpress_woocommerce_site, wi_create_webinar_registration_page, wi_disconnect_wordpress

25 Oct 2 tools changed the parameters they ask for wi_connect_wordpress_woocommerce_site, wi_disconnect_wordpress

25 Oct a tool appeared wi_get_build_status

24 Oct a tool changed version20 times that day

24 Oct 3 tool descriptions were rewritten4 times that day wi_connect_wordpress_woocommerce_site, wi_continue_webinar, wi_disconnect_wordpress

24 Oct 3 tools changed the parameters they ask for4 times that day wi_connect_wordpress_woocommerce_site, wi_disconnect_wordpress, wi_get_setup_plan

and 124 more, back to 26 September 2026

What the code does

We read the source, 3 h ago · tools taken from the live server · rules 995398eba69f

Evidence

Things with no honest explanation: a promise that contradicts the code, code that runs at install time while hiding what it does, data leaving the machine.

Claims read-only, but ships mutating tools wi_webinar_delete

заявлено «только чтение», но есть wi_webinar_delete

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

We found things in this code

Code changes quietly between releases, and nobody reads the diff of a dependency. We do, on every release — watch WebinarIgnition and you get told the day something new turns up.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 5 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add mcp --transport http https://mcp.webinarignition.com

Settings → Connectors → Add custom connector, then paste this address

https://mcp.webinarignition.com

~/.codex/config.toml

[mcp_servers.mcp]
url = "https://mcp.webinarignition.com"

.cursor/mcp.json

{
  "mcpServers": {
    "mcp": {
      "url": "https://mcp.webinarignition.com"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "mcp": {
      "type": "http",
      "url": "https://mcp.webinarignition.com"
    }
  }
}

This server publishes 1 more address. The block above uses the one we reach during checks; the full list is under Endpoints below, and the author may intend a particular one for your client.

Available tools 19

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

webinar

wi_create_webinar_registration_page

Builds the webinar on the connected WordPress site: it creates the campaign with the facts the session has collected — title, date, room type — and returns the registration and room links. Side effect: it creates real content on the host's site: a campaign with its registration page and its room. It answers within seconds with status `laeuft` and a progress card while the pages are still being built: show that card, then call wi_get_build_status about every 10 seconds until fertig is true. Do not call this tool a second time for the same webinar and do not write any text yourself. Needs `session_id`. Optional `args` overrides single fields (e.g. a different `start_date`).

wi_delete_webinar

Deletes the webinar that belongs to this session from the connected WordPress site — irreversible, it cannot be undone: the campaign and everything attached to it are gone. Needs `session_id`; optional `args` names the campaign when the session holds more than one.

wi_get_webinar_attendance_stats

Reads how many people registered, how many came live, how many stayed long enough to see the offer and how many watched the replay — with the show-up rate. Read-only, changes nothing. Use it when the host asks how many showed up, what the show-up rate is, whether the reminders worked, or who watched the replay. Do not use it for money or per-person data. Rates are only reported when at least 20 people were in the earlier step; below that the answer says so instead of inventing a percentage. Without a connected site the answer carries example numbers (sample: true) and the next step.

wi_get_webinar_funnel_conversion_stats

Reads the whole funnel of a webinar — unique visitors, registrations, live attendance, watched enough, offer shown, offer clicked, replay, purchased — with the step-to-step conversion rates, a ranking across the host's webinars and one sentence saying which step to fix first. Read-only, changes nothing. Use it when the host asks how the funnel converts, where people drop off, how the webinar compares to the others, or what to improve. Do not use it for single registrants (that is wi_list_webinar_leads_registrants) or for money in currency (that is wi_get_webinar_revenue_woocommerce). Rates need at least 20 people in the earlier step, otherwise the answer says 'not enough data' instead of a percentage. Without a connected site the answer carries example numbers (sample: true) and the next step.

wi_get_webinar_revenue_woocommerce

Reads what a webinar earned: paid orders and the amount per currency, open orders, refunds — and which offer tier (product) sold how often and for how much. Read-only, changes nothing. Money comes from the host's own shop (WooCommerce or any other shop connected to the site), never from estimates. Use it when the host asks what the webinar earned, which package sold, or where the upsell from tier to tier breaks. Do not use it for per-person spending (that is wi_list_webinar_leads_registrants) and never add two currencies together — each line stays separate. Without a connected site the answer carries example numbers (sample: true) and the next step.

wi_list_webinar_leads_registrants

Reads the registrant list of one webinar: name, email, signup time, attended, watched replay, purchased, UTM source, and what each registrant spent. Read-only, it changes nothing. Data comes only from the WordPress site this chat is connected to, the site the host approved, never from another site. Personal data is returned only when the host's licence includes the registrant export (export_leads). Without that licence the site answers with the code license_required and no personal data, plus a plain explanation of which plan includes the feature. Use it when the host asks who registered, how many leads came in, whom to follow up, or what a single lead bought. Do not use it for aggregate numbers (that is wi_get_webinar_funnel_conversion_stats), for deleting data or for exporting a file. Without a connected site the answer carries example numbers marked sample: true, from a static demo file that contains no real person.

wi_write_webinar_invitation_emails

Writes the finished webinar texts for a session that is ready: title, invitation email, reminders and the registration copy. Side effect: it starts a text-generation job on the connector (about a minute) and stores the result in the session; nothing is published to a WordPress site and no email is sent to anyone. Needs `session_id`. A second call with the returned `job_id` reads the job's state until the texts are there. Optional: `invite_type` for one of the eight built-in channels, `type="custom"` with `custom_channel` for any other channel, `direction` for an angle or `skip_direction` for none.

answer

wi_answer_product_question

Answers a question about WebinarIgnition — price, limits, integrations, whether it fits — from the connector's verified knowledge base. Read-only: no session is created, no site is touched, nothing is changed. The answer comes only from that base: when it holds no matching entry, the response says so and carries the canonical product address https://webinarignition.com/.

build

wi_get_build_status

Reads how far the build of the webinar on the connected site has come: one card with a bar, a percentage, the step running right now and an honest remaining time, plus `fertig` and the registration and room links once it is done. Read-only, it changes nothing on the site. Call it about every 10 seconds and show the card to the host until `fertig` is true, so they see it moving. Never write or invent texts yourself and never build the webinar a second time: the build is already running. Needs `session_id`; optional `campaign_id` when the session built more than one webinar.

connect

wi_connect_wordpress_woocommerce_site

Connects this chat to the host's own WordPress site. Side effect: it creates a connect link that the host must open and approve in their own browser — until they do, nothing is connected; no password is seen or stored. Needs `session_id` and `url`.

connector

wi_get_connector_status

Reads the technical state of the WebinarIgnition connector: version, protocol, which WordPress site is connected, whether the connection is healthy. Read-only, needs no input and changes nothing. `session_id` is optional: the connection belongs to the signed-in person, so any id of this conversation finds it, and with no id the answer still reports the connected site.

continue

wi_continue_webinar

Continues an open webinar conversation by exactly one turn: pass what the host said as `text` and get the reply with the next tappable choices. Side effect: the answer is stored in the conversation state (facts, flow position) for `session_id`; nothing is written to a WordPress site and nothing is sent to anyone. Needs `session_id` and either `text` or a chip: when the host taps one of `flow.chips`, pass the open `flow.jetzt` as `flow_step`, the chip's `label` as `flow_choice` AND the same label as `text`; then one call is enough. When the host types freely, pass their words as `text`. The reply carries `flow` ({ jetzt, weiter, auch, chips }) with the next choices. A reply with ready=true means the texts can be written next with `wi_write_webinar_invitation_emails`.

disconnect

wi_disconnect_wordpress

Drops the stored connection between this chat and the host's WordPress site, and also forgets that this site was ever connected (so a later chat does not offer it again). Material loss / hard to reverse: the connection has to be approved again in the host's own browser before anything else can run. The site itself stays untouched. Needs `session_id`. It ends only what belongs to this chat and its signed-in owner.

handoff

wi_create_handoff_link

Returns a link that carries everything collected so far into the WebinarIgnition dashboard, so the host can finish there. Side effect: it only creates a link with the session data in it; nothing is written to a WordPress site and nothing is sent to anyone. Needs `session_id` (or `content`), optional `url` and `rating`.

session

wi_get_session_facts

Reads what the current webinar session has collected so far — topic, audience, date, texts state. Read-only: no session is created, no site is touched, nothing is written. The session already holds what it was told, so nothing in it has to be asked again. Needs `session_id`.

setup

wi_get_setup_plan

Returns the step-by-step setup plan for the host's WordPress site — what has to be installed, what to click, what the room needs — without touching the site. Read-only. Optional `session_id` adds what the session already knows.

site

wi_list_site_abilities

Lists the abilities the connected WordPress site offers, with their arguments and whether they are read-only, write or destructive. Read-only: it reads a list from the site and changes nothing. Needs `session_id`.

start

wi_start_webinar

Starts a new webinar in WebinarIgnition and returns the first question with tappable options — no sign-in, no setup. Side effect: it creates a new webinar session on the connector and returns a `session_id`; nothing is written to a WordPress site, nothing is published and no email is sent. `situation` takes the host's own words, `known_facts` what is already known (topic, audience, offer, tone); with either, the conversation opens at that point instead of an empty menu. The reply carries a `session_id` for `wi_continue_webinar`.

wordpress

wi_check_wordpress

Checks whether a WordPress address runs WebinarIgnition and in which state: not installed, installed but too old, or ready. Side effect: none — it reads the address over HTTPS and changes nothing. Needs `url`.

Tools removed

Tools this server used to expose. Anything built against them stopped working on the day they went.

wi_webinar

removed 19 Oct 2026

wi_webinar_delete

removed 19 Oct 2026

wi_build_webinar

removed 20 Oct 2026

wi_connect_wordpress

removed 20 Oct 2026

wi_write_webinar_texts

removed 20 Oct 2026

Endpoints

URL	Transport	State	Latency	Checked
https://mcp.webinarignition.com	streamable-http	answering	219 ms	5 min ago
https://mcp.webinarignition.com/?src=registry	streamable-http	answering	184 ms	5 min ago

Alternatives to WebinarIgnition

same job, measured the same way

Wpagent MCP

by wpagent

Manage WordPress & WooCommerce from any MCP client — 58 tools over a signed REST API.

15 installs/wk local only

WordPress & WooCommerce MCP (MFPro)

by mjfutera

Manage WordPress blogs and WooCommerce shops from Claude, ChatGPT, Cursor and other MCP apps.

answering

Respira WordPress MCP

by respira

WordPress MCP with native page-builder editing, full-page creation, and WooCommerce tools.

2 496 installs/wk local only

WPBay

by wpbay

Search and compare WordPress plugins, themes and WooCommerce extensions on WPBay.

3 tools answering

Woocommerce MCP

by wppoland

Read-only MCP server for WordPress + WooCommerce products, orders, sales, and posts.

19 installs/wk local only

Heartly Deals — Live Flash Sales (Shopify & WooCommerce)

by heartly

Live flash-sale inventory from verified Shopify and WooCommerce merchants worldwide.

3 tools answering

Woo Revenue Incident Graph

by tytutueh13-sudo

Check WooCommerce checkout-change risk using public evidence and privacy-safe store signals.

4 tools answering

Woocommerce

by pipeworx-io

WooCommerce MCP Pack — wraps the WooCommerce REST API v3

47 tools answering

WebinarIgnition — questions

Answers built from our own checks of this server.

What can WebinarIgnition do?

It exposes 19 tools, read directly from the server on our last check. Among them: wi_answer_product_question, wi_check_wordpress, wi_connect_wordpress_woocommerce_site, wi_continue_webinar, wi_create_handoff_link, wi_create_webinar_registration_page and 13 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is WebinarIgnition working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 180 of 182 checks got a reply (98.9%), average response time 354 ms. The bar chart above shows every period we have measured.

Did WebinarIgnition ever remove tools?

Yes. wi_webinar, wi_webinar_delete, wi_build_webinar, wi_connect_wordpress and 1 more are no longer exposed — we recorded the date each one disappeared. A tool vanishing usually means a breaking change for anything that depended on it.

How do I connect WebinarIgnition?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does WebinarIgnition need an API key?

No. WebinarIgnition completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 19 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is WebinarIgnition?

It answers our handshake in 354 ms on average, which is faster than 43% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is WebinarIgnition open source?

The code is open source: it is published under the MIT licence, written in JavaScript, 0 stars on GitHub and 1 open issue. The licence covers the code in the repository, not the hosted service at mcp.webinarignition.com, which runs on its operator's own terms.