Connect Windsurf to a remote MCP server

Windsurf reaches your tunnel over Streamable HTTP at its public URL, and accepts the standard mcpServers block verbatim.

The config entry

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

This is exactly what mcppipe up prints — no re-nesting needed, unlike VS Code.

Where the config file lives

OS	Path
macOS / Linux	~/.codeium/windsurf/mcp_config.json
Windows	%USERPROFILE%\.codeium\windsurf\mcp_config.json

The path sits under .codeium rather than .windsurf — Windsurf is Codeium’s editor, and the config lives under the parent product’s directory. This is the single path mcppipe scans for Windsurf; there is no alternate location.

Auto-detect

mcppipe up with no arguments reads that file along with the other clients’ configs, so a server you already have set up in Windsurf can be exposed without retyping its command. Inspect what it finds with:

mcppipe detect --json

IP allowlist

Windsurf runs on your machine, so the relevant allowlist entry is your own egress IP, not a vendor’s range.

See also

• Client compatibility — the full matrix
• CLI reference
• Quickstart