Use this setup if your client does not support remote HTTP MCP servers, or if you prefer to connect through a local stdio bridge process.
mcp-remote is an open-source tool maintained outside Euno. This example uses [email protected].
With this setup, Cursor launches mcp-remote locally, and mcp-remote connects to the Euno MCP endpoint on Cursor's behalf.
Before using the bridge setup, make sure you have:
access to Euno and at least one assigned persona
Node.js 18+ installed locally so you can run npx
an MCP-compatible client that can launch a local stdio MCP server
mcp-remote)Open Cursor Settings
Go to Tools & Integrations
Add a new MCP server. In the mcp.json file that opens, add:
{
"mcpServers": {
"euno-assistant": {
"command": "npx",
"args": [
"-y",
"[email protected]",
"https://api.app.euno.ai/mcp"
]
}
}
}Save the file
The first time you use Euno MCP, Cursor will prompt you to sign in to Euno in a browser
After sign-in, you can start using Euno MCP in chat through the bridge
This bridge setup uses the same OAuth flow as the direct connection.
Confirm that Node.js version 18 or newer and npx are installed on your machine
Confirm that the mcp-remote entry in mcp.json matches the example above
Save the file and refresh Tools & Integrations
Try the connection again
Remove and re-add the Euno MCP server entry if the issue persists
If the problem continues, contact your Euno team or support team
Last updated