Problem
On systems where the python executable is not available (common on Linux/macOS where only python3 is in PATH), the MCP server fails to connect when using the configuration commands shown in the README.
For example, running:
claude mcp add -s user istat -- python -m istat_mcp_server --cwd /path/to/istat_mcp_server
results in Failed to connect because python is not found.
Solution
Use python3 explicitly, or point directly to the virtual environment's Python executable:
claude mcp add -s user istat -- python3 -m istat_mcp_server --cwd /path/to/istat_mcp_server
Or, if python3 is also not in PATH (e.g. when using a virtual environment):
claude mcp add -s user istat -- /path/to/istat_mcp_server/.venv/bin/python3 -m istat_mcp_server --cwd /path/to/istat_mcp_server
Environment
- OS: Linux (WSL2)
python not available in PATH, only python3
Notes
The README already has a note suggesting to replace python with python3 if needed, but the primary examples use python which may confuse users. Updating the examples to use python3 by default would improve the out-of-the-box experience on most modern Linux/macOS systems.
Problem
On systems where the
pythonexecutable is not available (common on Linux/macOS where onlypython3is in PATH), the MCP server fails to connect when using the configuration commands shown in the README.For example, running:
results in
Failed to connectbecausepythonis not found.Solution
Use
python3explicitly, or point directly to the virtual environment's Python executable:Or, if
python3is also not in PATH (e.g. when using a virtual environment):Environment
pythonnot available in PATH, onlypython3Notes
The README already has a note suggesting to replace
pythonwithpython3if needed, but the primary examples usepythonwhich may confuse users. Updating the examples to usepython3by default would improve the out-of-the-box experience on most modern Linux/macOS systems.