Agent setup

Set up DoDomain in OpenCode

The fast way: copy this sentence into OpenCode and let it do the setup below itself.

Add to Claude

Connect the MCP server

  1. 1. Add the server to opencode.json in the project root (or ~/.config/opencode/opencode.json for every project). If the file exists, merge the dodomain entry into its mcp object.

    File: opencode.json

    {
      "$schema": "https://opencode.ai/config.json",
      "mcp": {
        "dodomain": {
          "type": "remote",
          "url": "https://app.dodomain.io/api/mcp",
          "enabled": true
        }
      }
    }
  2. 2. Sign in to DoDomain (opens the browser for the OAuth consent)

    opencode mcp auth dodomain

Sign in. opencode mcp auth dodomain opens the DoDomain sign-in and consent page in the browser. OpenCode also starts this flow by itself the first time the server answers 401. No API key is involved: the MCP server uses OAuth and refuses secret keys by design.

What you get

Install the SDK

Server code uses a secret key from DODOMAIN_SECRET_KEY. Create an app at https://app.dodomain.io/dashboard and copy the secret key from its API keys card. It is shown once.

Verify

After signing in, ask the agent to call the list_apps tool: it lists the apps on your team. To check a secret key, run:

curl -s https://app.dodomain.io/api/v1/apps -H "Authorization: Bearer $DODOMAIN_SECRET_KEY"

Success is HTTP 200 with a JSON body of the form {"apps": [...]}: a secret key sees exactly its own app, with its id, name and publishable key.

Start on the free plan

No card, no sales call: create an app, mint a session, and watch the first domain verify.

OpenCode's own MCP documentation: https://opencode.ai/docs/mcp-servers/. Other agents: all agent guides.

We use analytics cookies to understand how DoDomain is used. The sign-in cookie is essential and is set regardless; the privacy policy names every service involved. Privacy policy