@Webinar MCP Server for WordPress, also WooCommerce, Email Automation
Basic information
Transport
streamable-http
Authentication
Check provider docs
Category
AI & Agents
Author
Webinar MCP Server for WordPress, also WooCommerce, Email Automation
Submitted by
Tobias Conrad
WordPress MCP integration for authorized site, WooCommerce and email-automation workflows.
https://mcp.webinarignition.com/?src=mcpsoclaude mcp add webinar-mcp-server-for-wordpress-also-woocommerce-email-automation --transport http https://mcp.webinarignition.com/?src=mcpsoReads 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`.
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`.
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.
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/.
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.
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`.
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`.
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.
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`.
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`.
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`; optional `url` removes the memory of that address even when this chat no longer holds the connection.
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. Needs `session_id`. Optional `args` overrides single fields (e.g. a different `start_date`).
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`.
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.
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.
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.
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.
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.
WordPress MCP integration for authorized site, WooCommerce and email-automation workflows.
Add https://mcp.webinarignition.com/?src=mcpso as a remote HTTP connection in an MCP-compatible client.
wi_get_session_facts — Reads what the current webinar session has collected so far — topic, audience, date, textswi_list_site_abilities — Lists the abilities the connected WordPress site offers, with their arguments and whetherwi_get_connector_status — Reads the technical state of the WebinarIgnition connector: version, protocol, which WordPwi_answer_product_question — Answers a question about WebinarIgnition — price, limits, integrations, whether it fits —The Webinar MCP Server for WordPress, also WooCommerce, Email Automation remote MCP server is a hosted Model Context Protocol endpoint at https://mcp.webinarignition.com/?src=mcpso, so AI assistants can connect to it without installing or running anything locally.
Add the endpoint https://mcp.webinarignition.com/?src=mcpso to any MCP-compatible client such as Claude Code, Cursor, or VS Code. The setup snippets on this page configure each client in one step.
Authentication requirements for Webinar MCP Server for WordPress, also WooCommerce, Email Automation have not been confirmed in this listing. Check the provider’s documentation before connecting.
Webinar MCP Server for WordPress, also WooCommerce, Email Automation exposes a streamable-http endpoint, the transport used by remote MCP servers and supported by all major MCP clients.
CVE prioritization using exploitation signals, plus agent heartbeat monitoring and state capsules. Some tools use API-key or x402 access.
AdaptlyPost: Schedule and publish social posts to Instagram, TikTok, YouTube, X, Facebook, LinkedIn, Pinterest, Threads, and Bluesky from any MCP client.
%20-%20Sarah%20Xu.svg){kind=icon}
Ideate, create, and deliver with Adobe pro tools
Pharmaceutical drug & clinical trial intelligence
Check one exact Gold Coast or Brisbane City property address. Free address/coverage check and short summary; paid structured Agent JSON adds available building, street and surrounding context, with Brisbane routed journe
Comments