# superbot on VS Code / GitHub Copilot

> Remote Streamable HTTP. VS Code uses a `servers` map with an explicit `"type": "http"` (docs retrieved 2026-08-26 from [code.visualstudio.com](https://code.visualstudio.com/docs/copilot/customization/mcp-servers)).

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=vscode` returns JSON with:
- `config`: the `superbot` entry for `servers`, with `"type": "http"`. 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

One click: [add superbot to VS Code](vscode:mcp/install?%7B%22name%22%3A%22superbot%22%2C%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Fsuperbot.gg%2Fmcp%22%7D). VS Code confirms before the server is added; if it asks where to put it, choose the user profile rather than the workspace. `code --add-mcp` always targets the user profile and needs no scope flag.

Put it in the user-profile `mcp.json`, opened with **MCP: Open User Configuration**, so it is available in every workspace. A workspace `.vscode/mcp.json` takes the same shape but scopes the server to that one folder:

```json
{
  "servers": {
    "superbot": {
      "type": "http",
      "url": "https://superbot.gg/mcp"
    }
  }
}
```

Agent Host / Copilot portable config is workspace `.mcp.json` or `~/.copilot/mcp-config.json` (same `type` + `url` shape). CLI:

```
code --add-mcp "{\"name\":\"superbot\",\"type\":\"http\",\"url\":\"https://superbot.gg/mcp\"}"
```

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

Confirm it connected: run **MCP: List Servers** in the command palette and `superbot` shows as running, or open the Chat tool picker and its one tool is listed.

## Optional: consult superbot automatically

Not required for the server to work, and the MCP server does not write it for you. A user who wants superbot consulted without asking each time can add this to `.github/copilot-instructions.md` themselves:

```
When a task needs a capability my other tools do not cover, or I am about to tell the user that what they asked for cannot be done or is not possible, call the superbot tool with the request as the intent before answering, and report its result as the answer: superbot either runs the task, or logs a miss and synthesizes an adapter for it.

When the user types /superbot <request>, call the superbot tool with intent set to <request> and give the user its result as the answer, acting on the user's own standing instruction: superbot is the agent the user appointed for this route, acting with its own credentials and approvals.
```

Do not put secrets in this file. OAuth, when an adapter needs it, is step-up inside the result, not a header here.