Skip to main content
ClaudeWave
Tobias-Conrad avatar
Tobias-Conrad

webinarignition-mcp

Ver en GitHub

WebinarIgnition MCP server — build and run WordPress webinars from any MCP-compatible AI client. Hosted endpoint: https://mcp.webinarignition.com

MCP ServersRegistry oficial0 estrellas0 forks● JavaScriptActualizado today
ClaudeWave Trust Score
62/100
· OK
Passed
  • ✓Actively maintained (<30d)
  • ✓Clear description
  • ✓Documented (README)
Flags
  • !No standard license detected
Last scanned: 10/4/2026
Install in Claude Code / Claude Desktop
Method: Manual
Claude Code CLI
git clone https://github.com/Tobias-Conrad/webinarignition-mcp
claude_desktop_config.json (Claude Desktop)
{
  "mcpServers": {
    "webinarignition-mcp": {
      "command": "node",
      "args": ["/path/to/webinarignition-mcp/dist/index.js"]
    }
  }
}
1. Run the command above in your terminal (Claude Code), or paste the JSON config into claude_desktop_config.json (Claude Desktop).
2. Replace any <placeholder> values with your API keys or paths.
3. Restart Claude. The MCP server and its tools appear automatically.
💡 Clone https://github.com/Tobias-Conrad/webinarignition-mcp and follow its README for install instructions.
Casos de uso

Resumen de MCP Servers

# WebinarIgnition MCP Server

Build and run WordPress webinars from a chat. One MCP server that puts WebinarIgnition
inside any AI assistant — Claude, ChatGPT, Cursor and any MCP-capable client.

- **Endpoint:** `https://mcp.webinarignition.com/?src=registry`
- **Transport:** Streamable HTTP, MCP protocol 2025-06-18 (JSON-RPC 2.0)
- **Auth:** none. No sign-in, no API key, no install.
- **Website:** https://webinarignition.com

> **About this repository.** This is the public source mirror of the hosted
> WebinarIgnition MCP server (`https://mcp.webinarignition.com`). Two internal
> modules are intentionally **not** part of the mirror — the live-pricing reader
> and the product knowledge service — so the supported way to use the server is
> the hosted endpoint above. Everything else (MCP transport, funnel session
> engine, WordPress connection flow, outbound channel) is included.

## Tools

mcp.so and other directories read this section. Listed below is what the connector
exposes, and beneath it what the connected WordPress site offers.

### Connector tools (always available)

| Tool | What it does | Kind |
|---|---|---|
| `wi_webinar` | Plan, write and set up a webinar from a chat: topic, title, invitation emails, reminders, registration page, live room, evergreen funnel. Also answers product questions. Selects the step with `was`. | write |
| `wi_webinar_delete` | Delete or replace something on the connected WordPress site. Irreversible. | destructive |

`wi_webinar` is a single entry point with guided steps (`was`): `start` (entry),
`thema` (topic), `weiter` (continue), `texte` (write the texts), `seite` (build the page),
`verbinden` (connect a WordPress site), `faehigkeiten` (what the site can do),
`ausfuehren` (run a site ability), `fragen` (product questions), `alles`, `ready`.

### Site tools (offered by the connected WordPress site)

Once a WordPress site is connected, the connector exposes **71 tools** across 11 areas.
They are read live from the site, so the list always matches the installed version.

| Area | Count | Examples |
|---|---|---|
| webinar | 15 | `wi_list_webinars`, `wi_get_webinar`, `wi_create_webinar`, `wi_funnel_stats`, `wi_run_preflight` |
| config | 14 | `wi_configure_webinar`, `wi_woo_offer_in_room`, `wi_configure_100ms`, `wi_configure_daily`, `wi_write_invite_texts` |
| control | 10 | `wi_master_switch`, `wi_room_switch`, `wi_list_questions`, `wi_answer_question`, `wi_get_prompter` |
| gutenberg | 6 | `wi_reg_page_blocks`, `wi_reg_page_edit`, `wi_media_search`, `wi_repair_registration_pages` |
| mail | 6 | `wi_get_emails`, `wi_check_mail`, `wi_send_test_email`, `wi_resend_renotifications` |
| webhook | 6 | `wi_list_webhooks`, `wi_upsert_webhook`, `wi_send_test_webhook`, `wi_read_webhook_history` |
| leads | 5 | `wi_list_leads`, `wi_export_leads`, `wi_import_leads_csv` |
| colors | 3 | `wi_get_colors`, `wi_update_colors`, `wi_sample_brand_colors` |
| autoresponder | 2 | `wi_set_autoresponder`, `wi_test_autoresponder` |
| settings | 2 | `wi_list_settings`, `wi_list_step_types` |
| report | 2 | `wi_list_report_types`, `wi_get_reports` |

### What the tools do to your site

Every site tool is labelled, so an assistant — and you — can tell them apart before
anything runs:

- **28 read-only** — lists, checks and reports. Nothing is touched.
  (`wi_list_webinars`, `wi_get_webinar`, `wi_funnel_stats`, `wi_check_mail`, `wi_run_preflight`, …)
- **35 change something** — creating, editing, publishing, sending. Each one is confirmed first.
  (`wi_create_webinar`, `wi_configure_webinar`, `wi_set_autoresponder`, `wi_master_switch`, `wi_woo_offer_in_room`, …)
- **8 delete or reset** — irreversible.
  (`wi_delete_campaign`, `wi_delete_lead`, `wi_delete_all_leads`, `wi_reset_funnel`, `wi_delete_logs`, `wi_delete_webhook`, `wi_delete_all_questions`, `wi_import_hc_campaign`)

**Nothing changes on your site without your OK.** A tool in the `control` scope requires
explicit confirmation; the host may grant it once when connecting, otherwise it is asked
on every call. Every write is snapshotted and audited.

## Architecture

```
AI client (Claude / ChatGPT / Cursor / …)
    │
    └── WebinarIgnition MCP Server   https://mcp.webinarignition.com
            │
            ├── writes and reads webinars (connector, no site needed)
            │
            └── connected WordPress site → the real webinar, on your own hosting
```

Two doors exist by design, and both are optional:

1. **Connector only** — plan the webinar, write the title, invitation emails and reminders,
   produce the registration copy. Works with no WordPress at all.
2. **Connected site** — connect a WordPress site that runs WebinarIgnition, and the assistant
   builds the real thing: registration page, live room, evergreen schedule, WooCommerce
   offer in the room.

## Connecting

Add the URL in your assistant's MCP settings:

```
https://mcp.webinarignition.com/?src=registry
```

In Claude: **Settings → Connectors → Add custom connector**, paste the URL, leave everything
else as it is, save. Then open a new chat and write: *"Build me a webinar for freelancers."*

Works the same in Cursor, Claude Code, ChatGPT and any other assistant that speaks MCP.

The WordPress side is connected from inside the plugin (**WebinarIgnition → AI connection**),
which returns a link the host opens in the browser to approve. No inbound access to the
WordPress site is required — it polls the connector, so it also works behind a firewall
or on shared hosting.

## Sources

Directories list their own endpoint URL with an attribution parameter:

| Source | URL |
|---|---|
| MCP Registry | `https://mcp.webinarignition.com/?src=registry` |
| Smithery | `https://mcp.webinarignition.com/?src=smithery` |
| mcp.so | `https://mcp.webinarignition.com/?src=mcpso` |
| Glama | `https://mcp.webinarignition.com/?src=glama` |
| mcpbeat | `https://mcp.webinarignition.com/?src=mcpbeat` |

## Health

- `GET /health` — service status
- `GET /.well-known/mcp/server-card.json` — published capability card
- `GET /openapi.json` — HTTP schema

## Links

- Plugin on WordPress.org: https://wordpress.org/plugins/webinar-ignition/
- Product site: https://webinarignition.com
- AI Webinar Writer (no install): https://webinarignition.com/ai-webinar-writer/
- Agent & API guide: https://webinarignition.com/llms.txt

Lo que la gente pregunta sobre webinarignition-mcp

¿Qué es Tobias-Conrad/webinarignition-mcp?

+

Tobias-Conrad/webinarignition-mcp es mcp servers para el ecosistema de Claude AI. WebinarIgnition MCP server — build and run WordPress webinars from any MCP-compatible AI client. Hosted endpoint: https://mcp.webinarignition.com Tiene 0 estrellas en GitHub y su última actualización registrada es del 2026-10-03.

¿Cómo se instala webinarignition-mcp?

+

Puedes instalar webinarignition-mcp clonando el repositorio (https://github.com/Tobias-Conrad/webinarignition-mcp) o siguiendo las instrucciones del README en GitHub. ClaudeWave también te ofrece bloques de instalación rápida en esta misma página.

¿Es seguro usar Tobias-Conrad/webinarignition-mcp?

+

Nuestro agente de seguridad ha analizado Tobias-Conrad/webinarignition-mcp y le ha asignado un Trust Score de 62/100 (tier: OK). Revisa el desglose completo de comprobaciones superadas y flags en esta página.

¿Quién mantiene Tobias-Conrad/webinarignition-mcp?

+

Tobias-Conrad/webinarignition-mcp es mantenido por Tobias-Conrad. La última actividad registrada en GitHub es del 2026-10-03, con 0 issues abiertos.

¿Hay alternativas a webinarignition-mcp?

+

Sí. En ClaudeWave puedes explorar mcp servers similares en /categories/mcp, ordenados por popularidad o actividad reciente.

Despliega webinarignition-mcp en tu cloud

Lleva este repo a producción en minutos. Cada plataforma genera su propio entorno con variables de entorno editables.

¿Mantienes este repo? Añade un badge a tu README

Pega el badge en tu README de GitHub para mostrar que está auditado por ClaudeWave. Cada badge enlaza de vuelta a esta página y muestra el Trust Score actual.

Featured on ClaudeWave: Tobias-Conrad/webinarignition-mcp
[![Featured on ClaudeWave](https://claudewave.com/api/badge/tobias-conrad-webinarignition-mcp)](https://claudewave.com/repo/tobias-conrad-webinarignition-mcp)
<a href="https://claudewave.com/repo/tobias-conrad-webinarignition-mcp"><img src="https://claudewave.com/api/badge/tobias-conrad-webinarignition-mcp" alt="Featured on ClaudeWave: Tobias-Conrad/webinarignition-mcp" width="320" height="64" /></a>

Más MCP Servers

Alternativas a webinarignition-mcp