docs: add instructions for defining path in claude desktop (#8269)

* initial-content

* project-name

* coder-review
This commit is contained in:
Mendon Kissling 2025-05-29 16:58:51 -04:00 committed by GitHub
commit d9037dfb3d
No known key found for this signature in database
GPG key ID: B5690EEEBB952194

View file

@ -300,3 +300,50 @@ You can use the ngrok console output to monitor requests for your project's endp
```
16:35:48.566 EDT GET /api/v1/mcp/project/fdbc12af-0dd4-43dc-b9ce-c324d1ce5cd1 200 OK
```
## Troubleshooting MCP server
If Claude for Desktop is not using your server's tools correctly, you may need to explicitly define the path to your local `uvx` or `npx` executable file in the `claude_desktop_config.json` configuration file.
1. To find your UVX path, run `which uvx`.
To find your NPX path, run `which npx`.
2. Copy the path, and then replace `PATH_TO_UVX` or `PATH_TO_NPX` in your `claude_desktop_config.json` file.
<Tabs>
<TabItem value="uvx" label="uvx" default>
```json
{
"mcpServers": {
"PROJECT_NAME": {
"command": "PATH_TO_UVX",
"args": [
"mcp-proxy",
"http://LANGFLOW_SERVER_ADDRESS/api/v1/mcp/project/PROJECT_ID/sse"
]
}
}
}
```
</TabItem>
<TabItem value="npx" label="npx">
```json
{
"mcpServers": {
"PROJECT_NAME": {
"command": "PATH_TO_NPX",
"args": [
"-y",
"supergateway",
"--sse",
"http://LANGFLOW_SERVER_ADDRESS/api/v1/mcp/project/PROJECT_ID/sse"
]
}
}
}
```
</TabItem>
</Tabs>