How WebinarIgnition works — WebinarIgnition MCP Resource

How WebinarIgnition works is one of 3 resources on the WebinarIgnition MCP server. Connect the server and your client can attach it as context.

by client

How to attach How WebinarIgnition works from your client

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

Other resources on this server

• Which interface to use
• What WebinarIgnition solves

WebinarIgnition also offers 4 prompts — things you invoke, where a resource is context you attach.

Read from the server itself, by connecting to it and calling resources/list on 25 September 2026. A listing does not declare its resources, 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 resource's type and contents.