Behavry Integration — Zed Editor

Zed registers MCP servers under its context_servers setting. Zed supports Streamable HTTP context servers natively, so Behavry connects directly to the unified MCP gateway (/mcp/v1) — no mcp-proxy or stdio bridge required.

---

Prerequisites

• A running Behavry instance (your control-plane URL, or http://localhost:8000 for a local stack)
• Zed installed
• An enrolled agent (gives you the client_id / client_secret)

---

1. Enroll the agent

In the dashboard: Agents → Enroll Agent → Zed. Behavry provisions the agent and gives you the config block to paste, with credentials filled in.

2. Config file locations

OS	Path
macOS / Linux	~/.config/zed/settings.json
Windows	%APPDATA%\Zed\settings.json

3. Config block

Merge under the context_servers key (note: Zed uses context_servers, not mcpServers):

{
  "context_servers": {
    "behavry": {
      "url": "https://<your-behavry-host>/mcp/v1",
      "headers": {
        "Authorization": "Basic <base64(client_id:client_secret)>"
      }
    }
  }
}

---

Verify

1. Reload settings: cmd-shift-p → zed: reload settings (or quit and reopen)
2. Open a project and open the Assistant panel
3. Run a tool-using query (e.g. "List the files in this project")
4. The tool call appears in the dashboard → Live Activity

---

Troubleshooting

Tools not available in Zed's assistant — Confirm the context_servers.behavry entry is present with a url ending in /mcp/v1, then reload settings.

Connection refused — The Behavry backend isn't reachable: curl https://<your-behavry-host>/health.

401 Unauthorized — Credentials wrong or agent revoked. Re-enroll and paste the fresh block.

Settings not taking effect — Zed caches settings; use Zed → Settings → Open Settings to confirm the key, then quit and reopen.