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