get_started_as_streamer — GingerLive MCP Prompt

get_started_as_streamer 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 get_started_as_streamer from your client

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

Other prompts on this server

• plan_livestream_campaign

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.