# superbot on Zed

No account yet? Follow https://superbot.gg/auth.md: it signs the user in with an emailed code and gives you a token for `https://superbot.gg/mcp`.

## Install for agent CLIs (no sign-in step)

`curl -fsS -X POST https://superbot.gg/mcp/install -d client=zed` returns JSON with:
- `config`: the `superbot` entry for `context_servers`. Its `url` is the endpoint and its `headers` hold `"Authorization": "Bearer <token>"`, which installs this server with its own key. The entry has the shape of the Config by hand entry below, plus those headers.
- `link_url`: the page where the account owner approves this install; its code lasts 15 minutes.

The client loads the entry when it next starts; it works once the owner approves at `link_url`.
Until then its `superbot` tool answers with a fresh `link_url`.

## Install with OAuth

Without a key, this server answers the entry under Config by hand with a 401 and an OAuth challenge. A client that supports MCP OAuth signs in from that challenge.

## Config by hand

Zed reads MCP servers from `context_servers` in its settings file. There is one settings file per user, so this is global by nature: Zed has no per-project MCP scope to get wrong.

`~/.config/zed/settings.json` (on macOS also `~/Library/Application Support/Zed/settings.json`):

```json
{
  "context_servers": {
    "superbot": {
      "url": "https://superbot.gg/mcp"
    }
  }
}
```

Connecting opens a browser sign-in for your Superbot account.

Confirm it connected: reload Zed, open the agent panel's Context Servers, and `superbot` should list as running.

Zed's settings file allows comments, so it is JSONC rather than strict JSON. An automated installer that cannot parse comments should leave the file alone and print the block above rather than rewriting it and dropping them.

Remove it by deleting the `superbot` entry from `context_servers`.