# Connect Your Editor

Remnus exposes a single remote MCP endpoint that any MCP-compatible editor can connect to:

```
https://www.remnus.com/api/mcp
```

There are two ways to authenticate:

- **OAuth (recommended, token-less)** — point the editor at the URL and approve the consent screen in your browser on first connect. Nothing to copy or paste. Works in editors that run the MCP OAuth 2.1 flow on a `401` (Claude Code, Cursor, VS Code, Zed, Codex, and most other MCP-compatible clients — including Claude Desktop via the `mcp-remote` bridge, see [Getting Started](/wiki/getting-started.md)).
- **Personal access token (PAT)** — mint a scoped token in **AI Agents → Connect editor → Advanced** (workspace owners only), then send it as an `Authorization: Bearer …` header. Works everywhere, including editors that do not yet run the OAuth flow.

> **Always use the `www` host for OAuth.** The apex `remnus.com` redirects to `www.remnus.com`, and some clients reject the resulting resource-indicator mismatch. PAT (header-based) connections follow the redirect fine either way.

## Editor matrix

| Editor | Config location | Auth | One-click |
|---|---|---|---|
| Claude Code | `claude mcp add` command | OAuth · PAT | ✓ |
| Claude Desktop | `claude_desktop_config.json` (via `mcp-remote`) | OAuth · PAT | — |
| Cursor | `~/.cursor/mcp.json` | OAuth · PAT | ✓ deeplink |
| VS Code (Copilot) | MCP settings | OAuth · PAT | ✓ deeplink |
| Codex | `~/.codex/config.toml` | OAuth (`codex mcp login`) · PAT | — |
| **Windsurf** | `~/.codeium/windsurf/mcp_config.json` | PAT | — |
| **Continue** | `~/.continue/config.json` | PAT | — |
| **Antigravity** | `~/.gemini/config/mcp_config.json` | PAT | — |
| **Cline** | `cline_mcp_settings.json` | PAT | — |
| **Zed** | `settings.json` → `context_servers` | OAuth · PAT | — |

Claude Code, Cursor, VS Code, Codex, Windsurf, Continue, and Antigravity are all walked through step-by-step in the in-app **AI Agents → Connect editor** flow — the first four produce one-click deeplinks or ready commands (OAuth by default); the last three are JSON-config editors, so the flow hands you a ready-to-paste snippet with a PAT already embedded (they don't yet support OAuth). This page additionally covers three editors not built into that flow: **Cline** and **Zed** (file-configured), and **Claude Desktop** (via the `mcp-remote` bridge — see [Getting Started](/wiki/getting-started.md)).

To mint a token for any of the PAT snippets below: open the sidebar **AI Agents** panel → **Connect editor** → expand **Advanced**, pick a workspace and scope (read or write), and copy the generated token. It is shown only once. Only workspace **owners** can mint tokens.

---

## Windsurf

Config file:

- macOS / Linux: `~/.codeium/windsurf/mcp_config.json`
- Windows: `%USERPROFILE%\.codeium\windsurf\mcp_config.json`

Add Remnus under `mcpServers` using `serverUrl` and your token:

```json
{
  "mcpServers": {
    "remnus": {
      "serverUrl": "https://www.remnus.com/api/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_TOKEN_HERE"
      }
    }
  }
}
```

1. Mint a token in **AI Agents → Connect editor → Advanced** and paste it in place of `YOUR_TOKEN_HERE`.
2. In Windsurf, open **Cascade → manage MCP servers** and click **Refresh** to load the new server.
3. Ask Cascade: *"List all pages and databases in my Remnus workspace."*

> Windsurf accepts both `serverUrl` and `url` for remote HTTP servers; `serverUrl` is the documented field. You can keep the token out of the file with variable interpolation — e.g. `"Authorization": "Bearer ${env:REMNUS_TOKEN}"`.

---

## Continue

Config file:

- macOS / Linux: `~/.continue/config.json`
- Windows: `%USERPROFILE%\.continue\config.json`

Add Remnus under `mcpServers`:

```json
{
  "mcpServers": {
    "remnus": {
      "url": "https://www.remnus.com/api/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_TOKEN_HERE"
      }
    }
  }
}
```

1. Mint a token in **AI Agents → Connect editor → Advanced** and paste it in place of `YOUR_TOKEN_HERE`.
2. Reload the config from Continue's settings, or restart your editor.
3. Ask Continue: *"List all pages and databases in my Remnus workspace."*

---

## Antigravity

Config file:

- macOS / Linux: `~/.gemini/config/mcp_config.json`
- Windows: `%USERPROFILE%\.gemini\config\mcp_config.json`

Antigravity uses `serverUrl` instead of `url` for remote HTTP servers:

```json
{
  "mcpServers": {
    "remnus": {
      "serverUrl": "https://www.remnus.com/api/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_TOKEN_HERE"
      }
    }
  }
}
```

1. Mint a token in **AI Agents → Connect editor → Advanced** and paste it in place of `YOUR_TOKEN_HERE`.
2. Reload MCP servers from Antigravity's settings.
3. Ask the agent: *"List all pages and databases in my Remnus workspace."*

---

## Claude Desktop

Claude Desktop doesn't (yet) appear in the in-app **Connect editor** picker, but it connects the same way as any desktop app that reads a `claude_desktop_config.json`-style `mcpServers` config: bridge through [`mcp-remote`](https://www.npmjs.com/package/mcp-remote), which runs the OAuth 2.1 browser flow on first connect.

- macOS: `~/Library/Application Support/Claude/claude_desktop_config.json`
- Windows: `%APPDATA%\Claude\claude_desktop_config.json`

```json
{
  "mcpServers": {
    "remnus": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://www.remnus.com/api/mcp"]
    }
  }
}
```

Restart Claude Desktop. On the first tool call it opens your browser to approve the consent screen — no token to paste. See [Getting Started](/wiki/getting-started.md) for the PAT-based variant.

---

## Cline

Cline runs inside VS Code or Cursor. Open the **MCP Servers** panel (Cline sidebar icon → top-right menu → **MCP Servers**) → **Configure MCP Servers** to edit `cline_mcp_settings.json`:

```json
{
  "mcpServers": {
    "remnus": {
      "type": "streamableHttp",
      "url": "https://www.remnus.com/api/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_TOKEN_HERE"
      }
    }
  }
}
```

1. Mint a token in **AI Agents → Connect editor → Advanced**.
2. Paste it as the `Authorization` header value and save.
3. Cline reloads the server automatically — the **remnus** tools appear in the MCP panel.
4. Ask: *"Use the remnus MCP to list my workspace."*

> **The `type` must be exactly `streamableHttp`** — camelCase, no hyphen. With `streamable-http` or no `type` at all, Cline falls back to SSE and the connection fails with a `405`. You can also add the server from Cline's **Remote Servers** tab instead of editing the JSON by hand.

---

## Zed

Zed calls MCP servers **context servers**. Open `settings.json` (**Cmd/Ctrl + ,**) and add Remnus under `context_servers`.

**OAuth (recommended)** — omit the header and Zed runs the browser sign-in on first use:

```json
{
  "context_servers": {
    "remnus": {
      "url": "https://www.remnus.com/api/mcp"
    }
  }
}
```

**With a token:**

```json
{
  "context_servers": {
    "remnus": {
      "url": "https://www.remnus.com/api/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_TOKEN_HERE"
      }
    }
  }
}
```

1. Add one of the snippets above to `settings.json`.
2. Open the Agent Panel — the **remnus** context server appears. If you used the OAuth form, approve the consent screen in your browser when prompted.
3. Ask the agent: *"List all pages and databases in my Remnus workspace."*

> Requires a recent Zed build with remote (URL-based) context server support. Older versions run stdio servers only — for those, bridge with [`mcp-remote`](https://www.npmjs.com/package/mcp-remote) by setting `"command": "npx"`, `"args": ["-y", "mcp-remote", "https://www.remnus.com/api/mcp"]` instead of `url`.

---

## Any other MCP client

If your tool is not listed, it almost certainly accepts the standard `mcpServers` shape. Point it at the endpoint and add a bearer token if it does not support OAuth:

```json
{
  "mcpServers": {
    "remnus": {
      "url": "https://www.remnus.com/api/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_TOKEN_HERE"
      }
    }
  }
}
```

## Verify

Whatever editor you use, confirm the connection and the context engine with:

> "Use Remnus `prepare_context` for: Analyze this workspace's product and technical context. Return `profile`, `estimatedTokens`, `truncated`, `concepts`, `related`, and `warnings`. Change nothing."

A successful response returns a token-budgeted Context Pack v2 without mutating anything. From there the agent can drill into selected pages and — with a write-scoped token or write consent — create and update content. Smart mode advertises this behavior through MCP session instructions; Strict mode also requires the returned `contextRunId` for actual Remnus mutations. See [Context-First MCP](/wiki/context-first.md), [Authentication](/wiki/authentication.md), and the [Read Tools](/wiki/read-tools.md) / [Write Tools](/wiki/write-tools.md) reference.