Connect Continue.dev to a remote MCP server

Continue.dev reaches your tunnel over Streamable HTTP, and keeps its MCP servers under a nested experimental key rather than the flat mcpServers block most clients use.

The config entry

{
  "experimental": {
    "modelContextProtocolServers": {
      "notes-via-tunnel": {
        "url": "https://notes--acme.mcppipe.dev/mcp"
      }
    }
  }
}

mcppipe up prints the generic mcpServers block, so for Continue.dev you need to move the map under experimental.modelContextProtocolServers — the inner server entry itself is unchanged.

Where the config file lives

OS	Path
macOS / Linux	~/.continue/config.json
Windows	%USERPROFILE%\.continue\config.json

Auto-detect

mcppipe up with no arguments reads that file and understands the experimental.modelContextProtocolServers shape, so servers you already have configured in Continue.dev are found without retyping. Check with:

mcppipe detect --json

Note

Continue.dev keeps this under experimental, which means the key can move as the project evolves. If auto-detect stops finding your servers after a Continue.dev upgrade, check whether the key was renamed, and point mcppipe at the file explicitly with --config ~/.continue/config.json in the meantime.

IP allowlist

Continue.dev runs in your editor on your machine, so the relevant allowlist entry is your own egress IP.

See also

• Client compatibility — the full matrix
• CLI reference — --config, detect