Connect Cline to a remote MCP server
Cline reaches your tunnel over Streamable HTTP and accepts the standard
mcpServers block verbatim.
The config entry
Section titled “The config entry”{ "mcpServers": { "notes-via-tunnel": { "url": "https://notes--acme.mcppipe.dev/mcp" } }}Where the config file lives
Section titled “Where the config file lives”Cline ships as a VS Code extension, so its settings live under the extension’s global storage rather than anywhere obvious:
<config dir>/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.jsonwhere <config dir> is:
| OS | Path |
|---|---|
| Windows | %APPDATA% |
| macOS | ~/Library/Application Support |
| Linux | ~/.config (or $XDG_CONFIG_HOME) |
The path is the same shape on every platform once anchored on the config directory.
Auto-detect
Section titled “Auto-detect”mcppipe up with no arguments scans that path along with the other clients, so
a server already configured in Cline can be exposed without retyping it. See
what it finds with mcppipe detect --json.
IP allowlist
Section titled “IP allowlist”Cline runs inside your editor, on your machine, so the relevant allowlist entry is your own egress IP.
See also
Section titled “See also”- Client compatibility — the full matrix
- VS Code — different file, different key
- CLI reference