Coding Tools MCP

Run it with whichever toolchain you already have (the server is Python ≥ 3.11 from PyPI; the npm package is a thin launcher that starts it via `uv` or `pipx`): ```bash uvx coding-tools-mcp --stdio --workspace /path/to/repo # Python toolchain npx coding-tools-mcp --stdio --workspace /path/to/repo # Node toolchain ``` Wire it into Claude Desktop, Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, or Cline — the JSON is the same everywhere (swap `uvx` for `npx` if you prefer Node): ```json { "mcpServers": { "coding-tools": { "command": "uvx", "args": ["coding-tools-mcp", "--stdio", "--workspace", "/path/to/repo"] } } } ``` Then ask your client: *"run the test suite and fix the first failure."* Prefer HTTP? Drop `--stdio` and the server speaks Streamable HTTP on `http://127.0.0.1:8765/mcp`. Both protocol eras are served on either transport: MCP `2026-07-28` in full, with `tools` as the only advertised capability, and the handshake era `2025-11-25` with `2025-06-18` compatibility. Neither has sessions. A one-line installer, per-client walkthroughs, and troubleshooting live in [docs/quickstart.md](docs/quickstart.md) and [docs/mcp-client-config.md](docs/mcp-client-config.md).