Agent Update

Connect

Zed → Agent Update

A fast Rust editor. Its built-in agent panel loads MCP servers as "context servers".

Zed talks to Agent Update over MCP. The server is https://api.tryagentupdate.com/v1/mcp, the transport is Streamable HTTP, and the credential is one header.

Where it goes: ~/.config/zed/settings.json (macOS/Linux) or %APPDATA%\Zed\settings.json (Windows)

Setup

~/.config/zed/settings.json
{
  "context_servers": {
    "agent-update": {
      "url": "https://api.tryagentupdate.com/v1/mcp",
      "headers": { "Authorization": "Bearer au_live_..." }
    }
  }
}

Before you file a bug

The top-level key is context_servers, not mcpServers. The header doubles as the OAuth switch: per Zed's docs, with no configured Authorization header it starts the MCP OAuth flow instead. We serve no OAuth metadata, so a misspelled key gives you a confusing failed OAuth prompt rather than a clean 401. Zed does no ${env:...} interpolation, so the token sits in the file in cleartext. Drop any "source": "custom" key from older tutorials, and ignore posts claiming Zed needs an mcp-proxy wrapper.

Check it worked

Ask the agent to text you. A 401 means the token is wrong, or the word Bearer is in there twice. No tool at all means the transport string is wrong. Both are covered in troubleshooting.

Next

The five tools and their arguments are on the MCP page. The same tools over plain HTTP are on the REST page. Every other tool is on the docs index.

← All docs