bye_planning — DraftCall MCP Prompt

bye_planning is one of 3 prompts on the DraftCall MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke bye_planning from your client

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

Other prompts on this server

• start_sit
• draft_pick

DraftCall also offers 1 resource — 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.