SyncDocs
Connect

Zed

Connect Zed's assistant to Sync via MCP.

Zed's assistant speaks Streamable HTTP MCP natively (recent builds), so it talks to https://sync.buzz/mcp directly. On older builds that only support stdio, fall back to mcp-remote — see the note at the bottom.

Prerequisites

  • A recent Zed build with HTTP context-server support.
  • A personal access token (see Connect overview).

Configure

Open Zed settings (Cmd+,) and add a context_servers entry:

{
  "context_servers": {
    "sync": {
      "source": "custom",
      "url": "https://sync.buzz/mcp",
      "headers": {
        "Authorization": "Bearer sync_pat_YOUR_TOKEN_HERE"
      }
    }
  }
}

Replace sync_pat_YOUR_TOKEN_HERE with the token from Account → Tokens.

Reload Zed. The assistant panel should list sync tools.

Verify

Ask the assistant:

List features in my project using the sync tools.

Zed will invoke sync_status and sync_search and return real data.

Tips

  • Zed settings are JSON with comments — store the token there if you trust your local disk, or wrap the config in .zed/settings.json and .gitignore it.
  • Scope the token in Account → Tokens to only the projects you want the assistant to touch.

Fallback for older Zed builds

If your Zed release doesn't support HTTP context servers yet, wrap the HTTP endpoint with mcp-remote as a stdio bridge:

{
  "context_servers": {
    "sync": {
      "command": {
        "path": "npx",
        "args": [
          "-y",
          "mcp-remote",
          "https://sync.buzz/mcp",
          "--header",
          "Authorization:Bearer sync_pat_YOUR_TOKEN_HERE"
        ]
      }
    }
  }
}

On this page