Install the published command from PyPI:
curl -fsSL https://raw.githubusercontent.com/xyTom/coding-tools-mcp/main/scripts/install.sh | bashInstall and start local Streamable HTTP against a workspace:
curl -fsSL https://raw.githubusercontent.com/xyTom/coding-tools-mcp/main/scripts/install.sh \
| bash -s -- --start --workspace /path/to/repoInstall and expose a read-only bearer-token tunnel:
curl -fsSL https://raw.githubusercontent.com/xyTom/coding-tools-mcp/main/scripts/install.sh \
| bash -s -- --tunnel cloudflared --auto-install-tunnel --workspace /path/to/repoOr, from this checkout:
scripts/install.shRun the published package without a persistent install:
uvx coding-tools-mcp --workspace .Use stdio for MCP clients:
uvx coding-tools-mcp --stdio --workspace /path/to/repoWhen working from this checkout instead of a published package, install the runtime in editable mode:
python -m pip install -e ".[dev]"Start Streamable HTTP against a workspace:
coding-tools-mcp --workspace /path/to/repo --host 127.0.0.1 --port 8765Endpoint:
http://127.0.0.1:8765/mcp
Start stdio:
coding-tools-mcp --stdio --workspace /path/to/repoRun the acceptance gate:
make complianceFor local trace debugging:
CODING_TOOLS_MCP_TRACE=1 coding-tools-mcp --workspace /path/to/repoTrace JSON lines are written to stderr.
If the MCP client cannot show permission prompts and you intentionally want permission-gated commands to run:
coding-tools-mcp --dangerously-skip-all-permissions --workspace /path/to/repoUse this only with trusted workspaces and trusted clients. It does not remove workspace path boundaries.