plan_launch — Highwire MCP Prompt
plan_launch
is one of 4 prompts on the
Highwire
MCP server. Connect the server and it appears in your client, ready to invoke.
by client
How to invoke plan_launch from your client
- Claude Code Highwire Prompt/plan_launch run in your project directory
- Claude Desktop Highwire Prompt/plan_launch ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Highwire Prompt/plan_launch ~/.cursor/mcp.json
- VS Code Highwire Prompt/plan_launch .vscode/mcp.json
- Zed Highwire Prompt/plan_launch ~/.config/zed/settings.json
- Windsurf Highwire Prompt/plan_launch ~/.codeium/windsurf/mcp_config.json
- Cline Highwire Prompt/plan_launch ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Highwire Prompt/plan_launch ~/.gemini/settings.json
- Grok Highwire Prompt/plan_launch .mcp.json (in your project root)
- ChatGPT Highwire Prompt/plan_launch Settings → Connectors → Advanced → Developer mode
- Claude.ai Highwire Prompt/plan_launch Settings → Connectors → Add custom connector
- LangChain Highwire Prompt/plan_launch pip install langchain-mcp-adapters
Other prompts on this server
Highwire 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 6 November 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.