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