Zed

Zed supports MCP through context_servers in settings. Recent versions support direct HTTP URLs; older setups can use the mcp-remote stdio bridge.

Prerequisites: YetiTech Docs MCP overview

Config file

Scope	Path
User	~/.config/zed/settings.json (Linux) · ~/Library/Application Support/Zed/settings.json (macOS)
Project	.zed/settings.json in your project root

Open via Zed → Settings or Command Palette → zed: open settings

Configuration (direct HTTP — recommended)

{
  "context_servers": {
    "yetitech-docs": {
      "url": "https://mcp.yetitechstudios.com"
    }
  }
}

Configuration (mcp-remote bridge)

If direct HTTP is unavailable in your Zed version, bridge with mcp-remote:

{
  "context_servers": {
    "yetitech-docs": {
      "command": {
        "path": "npx",
        "args": [
          "-y",
          "mcp-remote",
          "https://mcp.yetitechstudios.com"
        ]
      }
    }
  }
}

Enable

1. Save settings.json.
2. Open the Agent panel → settings gear.
3. Confirm yetitech-docs shows a green active indicator.

Zed forwards configured MCP servers to external agents via the Agent Client Protocol (ACP).

Try it

• “Search YetiTech docs for Auto Aim Component usage”
• “List YetiTech plugin documentation products”

Troubleshooting

Problem	Fix
Server inactive (red/yellow)	Check Agent panel tooltip; try the mcp-remote bridge
npx not found	Install Node.js or use a globally installed mcp-remote binary
Wrong key name	Zed uses context_servers, not mcpServers

Other clients

Overview · Cursor · Claude · VS Code · Windsurf · Cline · Continue