Ash-AI MCP and Cursor

My MCP config in Cursor:
{
"mcpServers": {
"tidewave": {
"command": "/Users/foo/mcp-proxy",
"args": [
"http://localhost:4000/tidewave/mcp"
]
},
"ash": {
"command": "/Users/foo/mcp-proxy",
"args": [
"http://localhost:4000/mcp/ash_ai"
]
}
}
}
{
"mcpServers": {
"tidewave": {
"command": "/Users/foo/mcp-proxy",
"args": [
"http://localhost:4000/tidewave/mcp"
]
},
"ash": {
"command": "/Users/foo/mcp-proxy",
"args": [
"http://localhost:4000/mcp/ash_ai"
]
}
}
}
When I enable the MCP server in Cursor, the output from my Ash app run via mix phx.server outputs the following endlessly: ``` [info] POST /mcp/ash_ai [debug] Processing with AshAi.Mcp.Router Parameters: %{"id" => "init", "jsonrpc" => "2.0", "method" => "initialize", "params" => %{"capabilities" => %{}, "clientInfo" => %{"name" => "test", "version" => "0.1.0"}, "protocolVersion" => "2025-03-26"}} Pipelines: [:mcp] [info] Sent 401 in 580µs [debug] Phoenix.Router halted in :mcp/2
Solution:
``` "ash_dev": { "command": "npx", "args": ["mcp-remote@0.1.5", "http://localhost:4000/mcp/ash"] }...
Jump to solution
3 Replies
ZachDaniel
ZachDaniel5mo ago
I believe in the docs we recommend a specific proxy mcp-remote
"ash_dev": {
"command": {
"path": "npx",
"args": ["mcp-remote@0.1.5", "http://localhost:4000/mcp/ash"],
"env": {}
},
"settings": {}
},
"ash_dev": {
"command": {
"path": "npx",
"args": ["mcp-remote@0.1.5", "http://localhost:4000/mcp/ash"],
"env": {}
},
"settings": {}
},
Terris
TerrisOP5mo ago
sweet I wonder if that works with tidewave too I'm reading the github readmes. Maybe I need to stop doing that.
Solution
Terris
Terris5mo ago
"ash_dev": {
"command": "npx",
"args": ["mcp-remote@0.1.5", "http://localhost:4000/mcp/ash"]
}
"ash_dev": {
"command": "npx",
"args": ["mcp-remote@0.1.5", "http://localhost:4000/mcp/ash"]
}

Did you find this page helpful?