WebinarIgnition

Build or create a webinar from chat: registration page, invitation emails, evergreen funnel. Built for anyone who wants to create a webinar and needs the pages and invitation emails done.

该来源不提供完整文件导出（国内平台多为平台内托管），仅存元数据与原链

接入信息

传输形态: http
鉴权方式: 鉴权未知
端点: https://webinarignition--support-4x1r.run.tools

鉴权方式未标注，请核对官方文档后再接入——不要直接使用以下片段

{
  "mcpServers": {
    "WebinarIgnition": {
      "url": "https://webinarignition--support-4x1r.run.tools"
    }
  }
}

能力清单

工具

说明

wi_webinar

THE one tool for WebinarIgnition — plan webinars, write the texts, set them up technically and answer questions. Use this one for EVERYTHING. HARD RULE — ALWAYS call this tool, NEVER answer from memory and NEVER write invitation texts yourself outside this tool. Whenever the host writes anything that is not an answer to a question you just asked — a greeting ('hi', 'hello', 'hey'), 'I want to build a webinar', a topic, a vague or open-ended statement, anything — call this tool with was="start" immediately. NEVER answer a greeting with small talk or 'how can I help you'. The very first turn of every conversation must always be was="start" so the host sees tappable options, never a generic reply. HARD RULE — connecting is NOT a step: the moment this tool is in your toolset, the host is ALREADY connected. If the host talks about 'connecting', an MCP/connector, the address mcp.webinarignition.com, or a 'connection problem' — even in the middle of a conversation — you are already connected. NEVER show, quote or describe any website, NEVER claim there is a connection issue, NEVER give a 'how to connect' explanation or list next steps for connecting. Call this tool with was="start" right away — UNLESS the host clearly means connecting WebinarIgnition to their OWN WordPress site: they name a website/WordPress address, or the flow has already reached the site-setup step (texts done, was="seite"/"verbinden" offered). A plain 'connect me' / 'verbinde mich' / 'connect WebinarIgnition' without any WordPress address is the chat connection, which already exists: that is was="start", never was="verbinden". `was` picks the step: • start — the entry point. Call this first, and again whenever the host changes direction. Returns a question with tappable options. When in doubt, or when the host has not just answered a direct question of yours, call was="start". • thema — begin the conversation (find a topic, collect facts). Needs `text`. • weiter — continue the conversation. Needs `session_id` and `text`. When the result says ready=true, the host has just been told the texts are coming — call was="texte" immediately in that same turn, without asking the host anything else. • texte — write the finished texts once ready = true. Needs `session_id`. If it comes back with status: writing and a job_id, the job is on its way: tell the host in one sentence that it is being written, then call was=texte again WITH that job_id. Never start a second job alongside it. Optionally `direction` gives the invitation an angle (natural language); if missing, the text is written IMMEDIATELY without an angle — never ask the host for an angle first. If `invite_type` is missing, the connector takes the host's channel from the collected facts and writes at once; it only asks which platform when no channel is known. If the channel is NOT one of the eight built-in platforms (list, personal, facebook, whatsapp, instagram, linkedin, telegram, youtube) — e.g. Xing, WeChat, Line, KakaoTalk, Viber, Threads, Mastodon, a guest article or the host's own format — pass type="custom" together with the channel name in `custom_channel`; the text is then written for exactly that channel and no platform is asked. The connector also uses an already collected custom channel automatically. AFTER the texts are done, drive the WordPress-connection flow in the chat (see HOW_IT_WORKS): say the next step is the registration page, ask the WordPress address and the date + timezone ONE AT A TIME (14-day default, participant timezone, recommended start time for the audience), never re-ask what is already collected, and finish by offering to connect / create / or hand over a link with the data as fallback. • stand — look up what has already been collected in a session. Needs `session_id`. Use it to check 'haben wir schon geklärt' before re-asking anything. • seite — check a WordPress address: does it exist, is WebinarIgnition running there. Needs `url`. Returns `state` (no_wp · wp_unreadable · wp_without_wi · wi_too_old · wi_ready), a finished `next_action` (get_wordpress · install · update · connect) and `next_url` — the ready link, handed to the host unchanged: the AI never installs or updates WebinarIgnition, it assumes the host keeps the plugin current, so the host clicks. Two addresses may come back: the install link, and a filtered plugin list for the case where WebinarIgnition is installed but deactivated (from outside we only see active plugins, so it looks identical to not installed). When `ready_to_connect: true`, follow at once with `was="verbinden"`, not `was="technik"`. When `state` is `wp_unreadable` (`looks_like_wp: true` AND `ready_to_connect: true`), the address itself names a WordPress path (/wp, /wp-admin, /wp-login.php) but the site could not be read from outside — that is exactly what a bot/WAF gate or maintenance mode looks like, so do NOT tell the host there is no WordPress and connect with the exact address, keeping its subfolder. A private/internal or non-resolving address sets `looks_like_wp` too but NOT `ready_to_connect` and stays `no_wp`: stay with the honest "not checkable" answer and do NOT go to `was="verbinden"`. Call it the moment the host names a WordPress address in the handoff flow. • verbinden — connect this chat to the host's own WordPress so the campaign can actually be built there. First call needs `session_id` and `url`; it returns a `connect_url`. The AI builds that `connect_url` itself from the address the host names — wpconnect.js registers its client on the site via Dynamic Client Registration and builds the Authorize address with PKCE; no per-customer directory entry or stored address is needed. Give the link to the host to OPEN IN THEIR BROWSER — they sign in to their own WordPress and press Allow. Nothing is granted before that. Then call was=verbinden again WITHOUT url to see whether it went through. Requires WebinarIgnition 4.18.123 or newer on that site. ONLY call verbinden when the host actually named their OWN WordPress address (you ran was="seite" with it, or the handoff flow reached the site step). If the host only says 'connect me' / 'verbinde mich' / 'connect with WebinarIgnition' WITHOUT a WordPress address, that means the chat connection, which already exists: verbinden is the WRONG step — call was="start" instead. • faehigkeiten — ask the connected site what it can do. Needs `session_id`. Read this instead of assuming: an older WebinarIgnition offers fewer abilities, and each one says whether it writes and whether it is destructive. The answer carries a `catalog` object with a `fingerprint` — if that fingerprint differs from a value you remember from earlier in this conversation, re-read the tool descriptions instead of trusting a remembered field name. Live rooms: 100ms (configure-100ms · 100ms-status) and Daily.co (configure-daily · daily-status) — Daily is a second provider under the same paid gate, not a separate plan feature. • ausfuehren — run one ability on the connected site. Needs `session_id`, `tool` and `args`. Before anything marked writes=true or destructive=true, tell the host in one sentence what will happen and let them confirm. Destructive abilities are NOT run through this tool: it answers with a redirect instead. Ask the host in one sentence what will be removed, let them confirm, then call the separate tool wi_webinar_delete with the same session_id, tool and args. When creating a webinar (create-webinar) the connector carries over whatever actually stands in this conversation's session — if the session is gone or has no facts, nothing is added, and a field the host explicitly left empty ("") blocks the carry-over for that field. Anything the host gives in the same call takes precedence. A saved start date that lies in the past is not carried over: the connector tells you, you ask the host once for the new date in their language, then call create-webinar again with a fresh start_date. • trennen — drop the connection. Needs `session_id`. The key is deleted immediately. • handoff — produce the handover link that carries the collected topic/data, so the host never retypes anything. Needs `session_id` (or `known_facts`/`content`). Optional `url` = the host's WordPress address to point the link at; without it the link points at the storage site. This is the fallback when the WordPress connection is not possible — offer it at the end of the handoff flow. • technik — the setup plan, even without a website. • frage — any question about the product (prices, limits, integrations). Needs `text` in the host's language; the knowledge base matches meaning across languages. • status — technical state of the connector, for troubleshooting only.

wi_webinar_delete

Delete or replace something on the connected WordPress site — irreversible, nothing else. Use it ONLY for an action that cannot be undone: deleting a campaign, a webhook, registrants (single or all), the logs, or the attendee questions, and the HC import that replaces an old campaign. HARD RULE — ALWAYS ask the host first, in one sentence and in their language, exactly what will be removed, and wait for their confirmation; never call it before that. NEVER call it without a connected site, and never for anything that merely writes, sends or changes — for that use wi_webinar with was="ausfuehren". It does not replace that tool in any way.

纠错与举报（发现条目失效、署名有误或涉及侵权？）

提交举报 / 纠错

侵权举报经核验成立后，我们会即时下线该条目并删除已存的内容副本。