WebinarIgnition MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| wi_webinarA | Plan, write and set up a webinar from a chat, and answer questions about WebinarIgnition. It picks a 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. Needs no sign-in. Returns JSON.
|
| wi_webinar_deleteA | 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 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| build_my_webinar | Build a complete webinar — topic, title, invitation emails and registration page. |
| find_my_topic | Not sure what to talk about? Find a webinar topic your audience is already looking for. |
| can_webinarignition_do_this | Ask anything about WebinarIgnition — integrations, limits, pricing, or whether it fits what you need. |
| write_my_invitation | I already have a topic — write my invitation email and title. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Which interface to use | Which existing WordPress interface handles which job — and where an AI cannot edit (Elementor, Divi, Thrive). |
| What WebinarIgnition solves | Verified answers: integrations, webhooks, limits, licences, video sources, page builders, when it is not the right tool. |
| How WebinarIgnition works | What WebinarIgnition does, who you are building for, and how to run the conversation. |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: wi_webinar handles all non-destructive planning, setup, connection, and ability execution, while wi_webinar_delete is explicitly restricted to destructive deletion/replacement abilities. The boundary is reinforced by the description of wi_webinar, which points to wi_webinar_delete for destructive operations.
Both tools share a consistent 'wi_webinar' prefix, which ties them to the domain. However, the main tool is named as a bare noun (wi_webinar) rather than following a verb_noun pattern like its counterpart (wi_webinar_delete), a minor deviation from ideal consistency.
With only two tools for a broad domain (webinar planning, writing, WordPress connection, ability execution, deletion, Q&A, handoff), the surface feels thin. While consolidating many actions into a single parameterized tool is a valid design choice, the low count borders on under-provisioned.
The tools cover the full lifecycle: planning, content generation, site connection, running non-destructive abilities, destructive deletion/replacement, handoff, and technical status. Minor gaps exist (e.g., no explicit list or update tools, though abilities likely fill these), but the core workflows are well represented.