Who is this for?
Users who copied an MCP config but the client cannot start the command.
Config path and example
Terminal PATH and MCP client config
{
"mcpServers": {
"filesystem": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-filesystem", "./"]
}
}
}Installation steps
Identify the runtime
Look at the first word of the command: npx, uvx, docker, python, node, or bunx.
Run the command in terminal
If it fails in terminal, install the missing runtime before editing MCP config.
npx -y @modelcontextprotocol/server-filesystem ./Use an absolute path if needed
Some clients do not inherit your shell PATH. Use the full executable path when needed.
Restart the client
After fixing PATH or installing the runtime, fully restart Cursor, Claude, VS Code, or Codex.
Common setup issues
Node.js missing
Install Node.js LTS to use npx-based MCP servers.
Docker not running
Start Docker Desktop before using docker-based MCP servers.
FAQ
Why does it work in terminal but not in the app?
GUI apps may not inherit the same PATH as your terminal.
Should I use absolute paths?
Use absolute paths when the client cannot find the executable.