Skip to content
mcppipe

Connect Zed to a remote MCP server

Zed reaches your tunnel over Streamable HTTP. It calls MCP servers context servers, and its config key follows that naming — so the standard mcpServers block does not apply here.

The config entry

Section titled “The config entry”
{
  "context_servers": {
    "notes-via-tunnel": {
      "url": "https://notes--acme.mcppipe.dev/mcp"
    }
  }
}

mcppipe up prints the generic mcpServers block; for Zed, rename the outer key to context_servers.

Where the config file lives

Section titled “Where the config file lives”
OSPath
macOS~/Library/Application Support/zed/settings.json
Linux~/.config/zed/settings.json (or $XDG_CONFIG_HOME/zed/…)
Windows%APPDATA%\zed\settings.json

This is Zed’s main settings file, not a separate MCP file — the context_servers map sits alongside your editor settings.

Auto-detect

Section titled “Auto-detect”

mcppipe up with no arguments reads that file and recognises the context_servers key, so a context server already configured in Zed can be exposed without retyping it:

Terminal window
mcppipe detect --json

Comments and trailing commas in settings.json are stripped before parsing, so an annotated settings file does not defeat detection.

IP allowlist

Section titled “IP allowlist”

Zed runs on your machine, so the relevant allowlist entry is your own egress IP.

See also

Section titled “See also”