build_exit_pack — ExitProof MCP Tool
build_exit_pack
(build exit pack) is one of 5 tools on the
ExitProof
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call build_exit_pack from your client
- Claude Code ExitProof build_exit_pack run in your project directory
- Claude Desktop ExitProof build_exit_pack ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor ExitProof build_exit_pack ~/.cursor/mcp.json
- VS Code ExitProof build_exit_pack .vscode/mcp.json
- Zed ExitProof build_exit_pack ~/.config/zed/settings.json
- Windsurf ExitProof build_exit_pack ~/.codeium/windsurf/mcp_config.json
- Cline ExitProof build_exit_pack ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI ExitProof build_exit_pack ~/.gemini/settings.json
- Grok ExitProof build_exit_pack .mcp.json (in your project root)
- ChatGPT ExitProof build_exit_pack Settings → Connectors → Advanced → Developer mode
- Claude.ai ExitProof build_exit_pack Settings → Connectors → Add custom connector
- LangChain ExitProof build_exit_pack pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http exitproof https://exitproof.davisvillelabs.com/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 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.