build_my_webinar — WebinarIgnition MCP Prompt

build_my_webinar is one of 4 prompts on the WebinarIgnition MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke build_my_webinar from your client

• Claude Code WebinarIgnition Prompt/build_my_webinar run in your project directory
• Claude Desktop WebinarIgnition Prompt/build_my_webinar ~/Library/Application Support/Claude/claude_desktop_config.json
• Cursor WebinarIgnition Prompt/build_my_webinar ~/.cursor/mcp.json
• VS Code WebinarIgnition Prompt/build_my_webinar .vscode/mcp.json
• Zed WebinarIgnition Prompt/build_my_webinar ~/.config/zed/settings.json
• Windsurf WebinarIgnition Prompt/build_my_webinar ~/.codeium/windsurf/mcp_config.json
• Cline WebinarIgnition Prompt/build_my_webinar ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
• Gemini CLI WebinarIgnition Prompt/build_my_webinar ~/.gemini/settings.json
• Grok WebinarIgnition Prompt/build_my_webinar .mcp.json (in your project root)
• ChatGPT WebinarIgnition Prompt/build_my_webinar Settings → Connectors → Advanced → Developer mode
• Claude.ai WebinarIgnition Prompt/build_my_webinar Settings → Connectors → Add custom connector
• LangChain WebinarIgnition Prompt/build_my_webinar pip install langchain-mcp-adapters

Other prompts on this server

• find_my_topic
• can_webinarignition_do_this
• write_my_invitation

WebinarIgnition also offers 3 resources — data you attach as context, where a prompt is something you run.

Read from the server itself, by connecting to it and calling prompts/list on 25 September 2026. A listing does not declare its prompts, so asking is the only way to know them, and this is what the server actually offers rather than what its listing claims. Names only are stored; connect the server for each prompt's arguments.