Docs/MCP

Connect opencode to Conbersa

Add the Conbersa MCP server to opencode as a remote server in opencode.json so the agent can run, post, and schedule against your fleet.

Updated September 23, 2026 · 2 min read

opencode reaches Conbersa the same way: a remote server in opencode.json. Add it once and the agent gets all 22 tools.

Prerequisites

  • A Conbersa API key (cb_live_...) from Settings → API keys.
  • opencode with MCP support.

Add the server

Edit opencode.json in your project (or the global config) and add a conbersa entry under mcp:

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "conbersa": {
      "type": "remote",
      "url": "https://api.conbersa.ai/mcp",
      "enabled": true,
      "timeout": 60000,
      "headers": {
        "X-API-Key": "cb_live_YOUR_KEY"
      }
    }
  }
}

Reload opencode. The Conbersa tools show up.

Verify

Ask the agent:

List my Conbersa devices.

If you get your fleet, you're connected. If not, see MCP troubleshooting.

Example prompts

Which devices are free, and which prompt does each one run by default?

Start a run using my saved prompt on the free TikTok devices.

Ingest this public Drive link and post it to TikTok, then send me the session link.

Notes

  • Keep keys out of commits. Add opencode.json to .gitignore when it holds a live key, or read the key from an environment variable.
  • Multiple accounts. You can register several entries — say conbersa-admin and conbersa-readonly — with different keys to separate access levels.
  • Local development. Point url at http://localhost:8080/mcp when you run the backend locally.

Next

FAQ

Frequently asked questions

Add a remote MCP entry to opencode.json under the mcp key. Set type to remote, url to https://api.conbersa.ai/mcp, enabled to true, and add an X-API-Key header with your cb_live_ key. opencode exposes the Conbersa tools to the agent automatically.
For local use that is fine, but do not commit an opencode.json containing a live key. Keep it in a gitignored file or reference it from your environment. If it is ever committed, revoke the key in Settings and issue a new one.
Both work. The examples here use X-API-Key because opencode's config supports arbitrary headers. Authorization: Bearer cb_live_... is equivalent if you prefer that form.