Connect

8 clients · secrets stay placeholders

JSON (mcpServers)Claude CodeCodexOpenCodeCursorVS CodeGemini CLIGoose

{
  "mcpServers": {
    "webinarignition": {
      "type": "http",
      "url": "https://mcp.webinarignition.com/?src=registry"
    }
  }
}

claude mcp add --transport http webinarignition https://mcp.webinarignition.com/?src=registry

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

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "webinarignition": {
      "type": "remote",
      "url": "https://mcp.webinarignition.com/?src=registry",
      "enabled": true
    }
  }
}

{
  "mcpServers": {
    "webinarignition": {
      "type": "http",
      "url": "https://mcp.webinarignition.com/?src=registry"
    }
  },
  "deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=webinarignition&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vbWNwLndlYmluYXJpZ25pdGlvbi5jb20vP3NyYz1yZWdpc3RyeSJ9"
}

{
  "servers": {
    "webinarignition": {
      "type": "http",
      "url": "https://mcp.webinarignition.com/?src=registry"
    }
  }
}

{
  "mcpServers": {
    "webinarignition": {
      "httpUrl": "https://mcp.webinarignition.com/?src=registry"
    }
  }
}

extensions:
  "webinarignition":
    enabled: true
    name: "webinarignition"
    type: streamable_http
    uri: "https://mcp.webinarignition.com/?src=registry"
    timeout: 300

Quality 75 / 100good

protocol75 · weight 25

warn
protocol.modernnewest supported version is 2025-11-25; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
n/a
protocol.statelessonly applies to 2026-07-28 servers
pass
protocol.transportstreamable HTTP
n/a
protocol.list_ttlonly applies to 2026-07-28 servers

authorizationn/a · weight 15

n/a
auth.prm, auth.as_metadata, auth.cimdno remote uses OAuth
n/a
auth.secret_in_urlno templated URL

tool hygiene100 · weight 30

pass
tools.descriptionsevery tool has a description
pass
tools.description_lengthdescriptions are concise
pass
tools.schemasevery tool has an object input schema
pass
tools.annotations14 of 14 tools declare readOnlyHint or destructiveHint
pass
tools.directory_hintsevery tool declares readOnlyHint, destructiveHint, idempotentHint and openWorldHint
pass
tools.token_costabout 3,588 tokens to load every tool
pass
tools.api_dumptools are not a one-to-one API dump

stability25 · weight 15

warn
stability.changes23 tool changes in 30 days
fail
stability.rug_pull2 tools kept their name but changed most of their description in 30 days; review before trusting them

dependenciesn/a · weight 15

n/a
deps.known_vulns, deps.mcp_sdk_version, deps.resolvableno npm or PyPI package

14 tools, about 3,588 tokens to load them all · tool set f2f8d6a0b72e · tools last changed 2026-10-19 · checked 2026-10-19 10:52 UTC

Tool changes

2026-10-19wi_webinarremoved
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.
2026-10-19wi_webinar_deleteremoved
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.
2026-10-19wi_delete_webinaradded
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.
2026-10-19wi_create_handoff_linkadded
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`.
2026-10-19wi_build_webinaradded
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`).
2026-10-19wi_disconnect_wordpressadded
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`.
2026-10-19wi_connect_wordpressadded
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`.
2026-10-19wi_check_wordpressadded
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`.
2026-10-19wi_write_webinar_textsadded
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.
2026-10-19wi_continue_webinaradded
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`.

Showing the latest 10. Full history: list_changes · trend: quality JSON.

Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.

Trust 96 / 100

provenance85

liveness100

freshness100

hygiene100

+repository +dns-namespace +website +reachable +uptime-99% +updated-0d-ago

Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.

Endpoints

remote	auth	reachable	uptime 30d	p50	protocol	last ok
`https://mcp.webinarignition.com/?src=registry` streamable-http	none	yes	99%	369 ms	2025-11-25	2026-10-19

Tools (14)

`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/.
`wi_build_webinar`	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_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`.
`wi_connect_wordpress`	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_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 `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_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`.
`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.
`wi_disconnect_wordpress`destructive	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_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.
`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`.
`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.
`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`.
`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`.
`wi_write_webinar_texts`	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.

Schemas: list_tools.

Similar MCP servers

Official server.json

{
  "name": "com.webinarignition/mcp",
  "icons": [
    {
      "src": "https://raw.githubusercontent.com/Tobias-Conrad/webinarignition-mcp/main/assets/wi-mcp-icon-400.png",
      "sizes": [
        "400x400"
      ],
      "mimeType": "image/png"
    }
  ],
  "title": "WebinarIgnition",
  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
  "remotes": [
    {
      "url": "https://mcp.webinarignition.com/?src=registry",
      "type": "streamable-http"
    }
  ],
  "version": "1.6.0",
  "repository": {
    "id": "1403627600",
    "url": "https://github.com/Tobias-Conrad/webinarignition-mcp",
    "source": "github"
  },
  "websiteUrl": "https://webinarignition.com",
  "description": "Your webinar numbers in the chat: registrants, leads, attendance, revenue from WordPress."
}