🔑Advanced API Key Setup

Use this setup if interactive OAuth sign-in is not available, or if you prefer manual API key and header configuration.

In this setup, you provide your Euno API key and connection headers directly in the MCP configuration.

Cursor Manual Setup

1. Open Cursor Settings

2. Go to Tools & Integrations

3. Add a new MCP server. In the mcp.json file that opens, add:

   {
     "mcpServers": {
       "euno-assistant": {
         "type": "http",
         "url": "https://api.app.euno.ai/mcp",
         "headers": {
           "x-api-key": "<API_KEY>",
           "x-account-id": "<ACCOUNT_ID>"
         }
       }
     }
   }

4. Replace <API_KEY> with your Euno API key and <ACCOUNT_ID> with the account this client should use

5. Save the file

If your setup includes a specific persona identifier, add it inside headers:

"headers": {
  "x-api-key": "<API_KEY>",
  "x-account-id": "<ACCOUNT_ID>",
  "x-euno-persona": "<PERSONA_ID>"
}

Bridge-Based Manual Setup

If your client uses a local stdio bridge and you also need API-key authentication, pass the same headers through mcp-remote instead of adding them directly in Cursor:

{
  "mcpServers": {
    "euno-assistant": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote@0.1.37",
        "https://api.app.euno.ai/mcp",
        "--header",
        "x-api-key: <API_KEY>",
        "--header",
        "x-account-id: <ACCOUNT_ID>",
        "--header",
        "x-euno-persona: content_maintainer"
      ]
    }
  }
}

Replace <API_KEY> and <ACCOUNT_ID> with your details. The x-euno-persona header is optional. If you omit it, Euno uses your default persona for the account when one is configured. If you include it, replace content_maintainer with a valid persona role name for your account. content_maintainer and contributor are example values.