Connecting an assistant

Connecting an assistant#

An editor or an assistant can be connected to your workspace over MCP, so it can read and write as you.

Takes

10 minutes

Needs

a key of your own

What it can do#

It can read and write in the channels you are in, and reply in a conversation: the same things you can do, and nothing more. It cannot see a channel you are not in. What it writes is marked as coming from a machine, so nobody mistakes it for you.

Getting a key#

1. Open your profile settings and find the part called MCP. The first thing there is your keys.
2. Make one and copy it. It is shown once, so paste it straight into the block below.
3. Keep it to yourself, because it acts as you. You can only have one at a time, so to change it, take it back and make another.

Pointing your assistant at Guild#

Pick your assistant below and paste the block into the file it names, replacing the placeholder with the key you copied.

You can delete a key whenever you like. If you stop using an assistant, delete its key.

[[mcp.servers]]
name = "guild"
transport.type = "http"
transport.url = "https://api.useguild.dev/mcp"
auth.type = "api_key"
auth.key = "YOUR_GUILD_API_KEY"

{
  "mcpServers": {
    "guild": {
      "headers": {
        "Authorization": "Bearer YOUR_GUILD_API_KEY"
      },
      "type": "http",
      "url": "https://api.useguild.dev/mcp"
    }
  }
}

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "guild": {
      "enabled": true,
      "headers": {
        "Authorization": "Bearer YOUR_GUILD_API_KEY"
      },
      "type": "remote",
      "url": "https://api.useguild.dev/mcp"
    }
  }
}

[mcp_servers.guild]
url = "https://api.useguild.dev/mcp"
http_headers = { Authorization = "Bearer YOUR_GUILD_API_KEY" }