Environment:
OS: Windows 11
Python: 3.14
code-review-graph: installed via pip install code-review-graph
Claude Code: v2.1.86
Bug:
Running code-review-graph install --platform claude generates this .mcp.json:
{
"mcpServers": {
"code-review-graph": {
"command": "uvx",
"args": ["code-review-graph", "serve"],
"type": "stdio"
}
}
}
This hardcodes uvx as the command, which fails for users who installed via pip rather than uv. The MCP server shows as failed in Claude Code, even though code-review-graph serve works perfectly when called directly.
Workaround:
Manually editing .mcp.json to use the direct command fixes it:
{
"mcpServers": {
"code-review-graph": {
"command": "code-review-graph",
"args": ["serve"],
"type": "stdio"
}
}
}
Expected behavior
The install command should detect how the package was installed and generate the appropriate config. If installed via pip, it should use "command": "code-review-graph" directly. If installed via uv/uvx, use "command": "uvx".
Alternatively, always default to "command": "code-review-graph" since it works regardless of installation method.
Environment:
OS: Windows 11
Python: 3.14
code-review-graph: installed via pip install code-review-graph
Claude Code: v2.1.86
Bug:
Running code-review-graph install --platform claude generates this .mcp.json:
This hardcodes uvx as the command, which fails for users who installed via pip rather than uv. The MCP server shows as failed in Claude Code, even though code-review-graph serve works perfectly when called directly.
Workaround:
Manually editing .mcp.json to use the direct command fixes it:
Expected behavior
The install command should detect how the package was installed and generate the appropriate config. If installed via pip, it should use "command": "code-review-graph" directly. If installed via uv/uvx, use "command": "uvx".
Alternatively, always default to "command": "code-review-graph" since it works regardless of installation method.