# superbot on Devin

> Remote Streamable HTTP, signed in with OAuth. Devin CLI keeps user-level servers under `mcpServers` in `$XDG_CONFIG_HOME/devin/mcp_config.json` (default `~/.config/devin/mcp_config.json`; `%APPDATA%\devin\mcp_config.json` on Windows), and `devin mcp add -s user` writes there. Devin takes no custom model endpoint, so this wires tools only. Docs retrieved 2026-10-10 from [docs.devin.ai/cli/extensibility/mcp/configuration](https://docs.devin.ai/cli/extensibility/mcp/configuration).

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

Run these two commands in a terminal:

```sh
devin mcp add -s user superbot https://superbot.gg/mcp
devin mcp login superbot
```

The first adds superbot to Devin for every project.
The second opens a browser sign-in for your Superbot account.
No key goes in the config file.

If superbot relay is installed, turn Devin on in its Your apps list instead.
Both use the name `superbot` in Devin's config, so only one of them can win.

This gives Devin superbot's tools and nothing else.
Devin keeps its own models.

## Check it

`devin mcp list` shows `superbot` among your servers.
`devin mcp get superbot` shows its details.

## Config by hand

The command above writes this entry for you.
To add it yourself, put it in `$XDG_CONFIG_HOME/devin/mcp_config.json` (default `~/.config/devin/mcp_config.json`), then run `devin mcp login superbot`:

```json
{
  "mcpServers": {
    "superbot": {
      "url": "https://superbot.gg/mcp",
      "transport": "http"
    }
  }
}
```

## Remove it

`devin mcp remove superbot`