# Connect your client

> Documentation index: https://exomations.com/llms.txt

Set up Claude Desktop, Claude Code, Cursor, Claude on the web or any other MCP client.

Every client needs the server address `https://exomations.com/api/mcp` and a way to sign in: an API key in a header, or OAuth for clients that cannot send a header. Create the key on the **API Keys** page with `execute` (run flows and read runs) and add `build` if the assistant should also draft flows. Give each client its own key.

| Client | How it signs in | Where the setting goes |
|---|---|---|
| Claude Desktop | API key, through `mcp-remote` | `claude_desktop_config.json` |
| Claude Code | API key, through `mcp-remote` | The `claude mcp add` command |
| Cursor | API key, through `mcp-remote` | Cursor's MCP settings |
| Claude on the web | OAuth (no key to copy) | A custom connector |
| Other clients | API key in a header | The client's own settings |

## Claude Desktop

Add this block to Claude's configuration file, put your key in it, and restart Claude. The file is `~/Library/Application Support/Claude/claude_desktop_config.json` on macOS and `%APPDATA%\Claude\claude_desktop_config.json` on Windows. The API Keys page shows the same block with your address filled in.

claude_desktop_config.json:

```json
{
  "mcpServers": {
    "exomations": {
      "command": "npx",
      "args": [
        "-y", "mcp-remote",
        "https://exomations.com/api/mcp",
        "--header", "X-Api-Key:exo_your_key"
      ]
    }
  }
}
```

## Claude Code

Run this once in a terminal. Everything after `--` is the command that runs the server, so Claude Code passes the header option to `mcp-remote` untouched.

Terminal:

```bash
claude mcp add --transport stdio exomations -- \
  npx -y mcp-remote https://exomations.com/api/mcp --header X-Api-Key:exo_your_key
```

## Cursor

Cursor uses the same server block as Claude Desktop, added in its MCP settings.

MCP settings:

```json
{
  "mcpServers": {
    "exomations": {
      "command": "npx",
      "args": [
        "-y", "mcp-remote",
        "https://exomations.com/api/mcp",
        "--header", "X-Api-Key:exo_your_key"
      ]
    }
  }
}
```

## Claude on the web

Browser-based clients cannot send a custom header, so the server also supports OAuth 2.0. Add the server address as a custom connector; the client discovers the rest and sends you to Exomations to approve. PKCE (S256) is required and clients register themselves. Approval needs a workspace Admin, who allows or declines what the client asked for (`execute`, `build` or both) as a whole. Access tokens last one hour and renew automatically; the connection stays as long as it is used at least once every 30 days, and you can revoke it on the API Keys page.

Server URL:

```text
https://exomations.com/api/mcp
```

## Other clients

Any client that can send a header connects directly with one of these two headers. A key placed in the URL (`?api_key=`) is refused, even when a header is also sent; if a key was ever put in a URL, rotate it. A client without an MCP library can use plain JSON-RPC over HTTPS: the MCP overview shows a complete session in three calls.

Header:

```text
X-Api-Key: exo_your_key
```

Bearer:

```text
Authorization: Bearer exo_your_key
```
