launch_plan_status — Tethered Trust for builders MCP Tool
launch_plan_status
(launch plan status) is one of 12 tools on the
Tethered Trust for builders
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call launch_plan_status from your client
- Claude Code Tethered Trust for builders launch_plan_status run in your project directory
- Claude Desktop Tethered Trust for builders launch_plan_status ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Tethered Trust for builders launch_plan_status ~/.cursor/mcp.json
- VS Code Tethered Trust for builders launch_plan_status .vscode/mcp.json
- Zed Tethered Trust for builders launch_plan_status ~/.config/zed/settings.json
- Windsurf Tethered Trust for builders launch_plan_status ~/.codeium/windsurf/mcp_config.json
- Cline Tethered Trust for builders launch_plan_status ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Tethered Trust for builders launch_plan_status ~/.gemini/settings.json
- Grok Tethered Trust for builders launch_plan_status .mcp.json (in your project root)
- ChatGPT Tethered Trust for builders launch_plan_status Settings → Connectors → Advanced → Developer mode
- Claude.ai Tethered Trust for builders launch_plan_status Settings → Connectors → Add custom connector
- LangChain Tethered Trust for builders launch_plan_status pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http builders https://tetheredtrust.com/mcp/buildersOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 9 November 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.