plan_livestream_campaign — GingerLive MCP Prompt

plan_livestream_campaign is one of 2 prompts on the GingerLive MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke plan_livestream_campaign from your client

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

Other prompts on this server

• get_started_as_streamer

GingerLive 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 24 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.