Webinar MCP Server for WordPress, also WooCommerce, Email Automation

Measured conclusion: Deep-tested. L2 outcome: tools_ok.

WordPress MCP integration for authorized site, WooCommerce and email-automation workflows.

Add to your agent

Copy this into your MCP client config:

{
  "mcpServers": {
    "Webinar MCP Server for WordPress, also WooCommerce, Email Automation": {
      "url": "https://mcp.webinarignition.com/?src=mcpso",
      "transport": "streamable-http"
    }
  }
}

Measured tools (19)

• wi_get_session_facts read-only

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

  Parameters:

  • session_id — string — From an earlier turn (weiter · texte · stand).

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• wi_list_site_abilities read-only

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

  Parameters:

  • session_id — string — From an earlier turn (weiter · texte · stand).

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• wi_get_connector_status read-only

  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.

  Parameters:

  • session_id — string — From an earlier turn (weiter · texte · stand).

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• wi_answer_product_question read-only

  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/.

  Parameters:

  • text — string — What the host said (thema · weiter) or the question in the host's language (frage).
  • language — string — The language the host writes in.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• wi_get_setup_plan read-only

  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.

  Parameters:

  • has_wi — boolean — true when WebinarIgnition is already installed on the host's site.
  • has_mcp — boolean — true when the host already uses an MCP/connector — the connector normally sets this itself.
  • language — string — The language the host writes in.
  • session_id — string — From an earlier turn (weiter · texte · stand).
  • has_wordpress — boolean — true when the host already has a WordPress site. Reist als Fluss-Signal mit: ohne es gilt der Standardweg (der Host hat vermutlich WordPress). Mit false wird der Verbinden-Schritt in der Strecke uebersprungen.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• 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`.

  Parameters:

  • focus — string — what it should be about.
  • has_wi — boolean — true when WebinarIgnition is already installed on the host's site.
  • language — string — The language the host writes in.
  • situation — string — Only with this call or this call: what the host just said, in their own words. On this call 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.
  • known_facts — object — Everything you already know — send it every turn so nothing is lost on a restart. On the FIRST call (this call or this call) 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 — true when the host already has a WordPress site. Reist als Fluss-Signal mit: ohne es gilt der Standardweg (der Host hat vermutlich WordPress). Mit false wird der Verbinden-Schritt in der Strecke uebersprungen.

  Hints: read-only no · destructive no · idempotent no · open-world yes

• 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`.

  Parameters:

  • text — string — What the host said (thema · weiter) or the question in the host's language (frage).
  • language — string — The language the host writes in.
  • flow_step — string — the flow step that was open in the previous answer — copy it from the returned `flow.jetzt`. It tells the server where the conversation stands so it does not have to guess.
  • session_id — string — From an earlier turn (weiter · texte · stand).
  • flow_choice — string — which chip the host tapped, EXACTLY as its label read in the returned `flow.chips` (or the label of an own option). The server advances the flow from this.
  • known_facts — object — Everything you already know — send it every turn so nothing is lost on a restart. On the FIRST call (this call or this call) 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.
  • flow_strecke — string — the route (Strecke) that runs — copy it from the returned `flow.strecke`. It tells the server which route to follow so it does not fall back to the default.

  Hints: read-only no · destructive no · idempotent no · open-world yes

• 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.

  Parameters:

  • type — string — 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.
  • job_id — string — 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.
  • language — string — The language the host writes in.
  • direction — string — Optional with this call: 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.
  • session_id — string — From an earlier turn (weiter · texte · stand).
  • invite_type — string — Only with this call, 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.
  • custom_channel — string — Only with this call 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 — true when the host wants NO special angle — then it generates without an angle.

  Hints: read-only no · destructive no · idempotent no · open-world yes

• wi_check_wordpress read-only

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

  Parameters:

  • url — string — The WordPress address (seite). With was=handoff: the host's WordPress address to point the handover link at.
  • session_id — string — From an earlier turn (weiter · texte · stand).

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• 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`.

  Parameters:

  • url — string — The WordPress address (seite). With was=handoff: the host's WordPress address to point the handover link at.
  • session_id — string — From an earlier turn (weiter · texte · stand).

  Hints: read-only no · destructive no · idempotent no · open-world yes

• wi_disconnect_wordpress destructive

  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.

  Parameters:

  • session_id — string — From an earlier turn (weiter · texte · stand).

  Hints: read-only no · destructive yes · idempotent yes · open-world yes

• 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`).

  Parameters:

  • args — object — the arguments for that ability, shaped by its input_schema.
  • language — string — The language the host writes in.
  • session_id — string — From an earlier turn (weiter · texte · stand).

  Hints: read-only no · destructive no · idempotent no · open-world yes

• wi_get_build_status read-only

  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.

  Parameters:

  • session_id — string — From an earlier turn (weiter · texte · stand).
  • campaign_id — integer — The webinar (campaign) id. Leave it out when this chat just built one.

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• 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`.

  Parameters:

  • url — string — The WordPress address (seite). With this call: the host's WordPress address to point the handover link at.
  • rating — integer — the host's rating (1-10), if any.
  • content — string — finished text to carry over, if the session alone does not hold it.
  • session_id — string — From an earlier turn (weiter · texte · stand).

  Hints: read-only no · destructive no · idempotent no · open-world yes

• wi_delete_webinar destructive

  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.

  Parameters:

  • args — object — the arguments for that ability, shaped by its input_schema.
  • session_id — string — From an earlier turn (weiter · texte · stand).

  Hints: read-only no · destructive yes · idempotent no · open-world yes

• wi_list_webinar_leads_registrants read-only

  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.

  Parameters:

  • limit — integer — How many registrants to return, 1-200. Default 50.
  • session_id — string — From an earlier turn (weiter · texte · stand).
  • webinar_id — integer — The webinar (campaign) id. Leave it out when the session already built one.

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• wi_get_webinar_attendance_stats read-only

  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.

  Parameters:

  • utm — string — Filter the numbers by one UTM value, e.g. a source such as facebook.
  • session_id — string — From an earlier turn (weiter · texte · stand).
  • webinar_id — integer — The webinar (campaign) id. Leave it out when the session already built one.

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• wi_get_webinar_funnel_conversion_stats read-only

  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.

  Parameters:

  • all — boolean — true compares all webinars and ranks them by volume.
  • utm — string — Filter the whole funnel by one UTM value, e.g. a source such as facebook.
  • session_id — string — From an earlier turn (weiter · texte · stand).
  • webinar_id — integer — The webinar (campaign) id. Leave it out to rank all webinars of the host.

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• wi_get_webinar_revenue_woocommerce read-only

  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.

  Parameters:

  • session_id — string — From an earlier turn (weiter · texte · stand).
  • webinar_id — integer — The webinar (campaign) id. Leave it out to read all webinars.

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

Measured by MCPYP probing. Untested fields are omitted, never estimated. Listing is always free; MCPYP never proxies calls or stores user tokens.