com.webinarignition/mcp
repo:https://github.com/tobias-conrad/webinarignition-mcp
Your webinar numbers in the chat: registrants, leads, attendance, revenue from WordPress.
- transport:
- remote
- credential class:
- self-provisionable
Owner verification
Not yet verified. Verifying proves you control this server and is free, permanently — it never changes a published score.
Start verification →Tools
- wi_answer_product_questionshallow
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/.
- wi_build_webinarshallow
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`).
- wi_check_wordpressshallow
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`.
- wi_connect_wordpressshallow
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`.
- wi_continue_webinarshallow
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 `text`. The reply carries `flow` ({ jetzt, weiter, auch, chips }) with the next choices; on the next call the open `flow.jetzt` goes into `flow_step` and the chosen chip's label into `flow_choice`. A reply with ready=true means the texts can be written next with `wi_write_webinar_texts`.
- wi_create_handoff_linkshallow
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`.
- wi_delete_webinarshallow
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_disconnect_wordpressshallow
Drops the stored connection between this chat and the host's WordPress site. 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`.
- wi_get_connector_statusshallow
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.
- wi_get_session_factsshallow
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`.
- wi_get_setup_planshallow
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.
- wi_list_site_abilitiesshallow
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`.
- wi_start_webinarshallow
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`.
- wi_webinarshallow
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.
- wi_webinar_deleteshallow
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.
- wi_write_webinar_textsshallow
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.
Embed this server’s score
Tool count and median score across every tool in this server’s corpus — honest in a way a single cherry-picked tool’s badge wouldn’t be.
[](https://vouch.tools/servers/70930b71-77f9-4c30-9bba-934b75f6a27a)