Docs/MCP

Connect Claude to Conbersa

Connect Claude Code or Claude Desktop to the Conbersa MCP server with a bearer-key config. Note: Claude's remote OAuth connector is not supported yet.

Updated September 23, 2026 · 2 min read

Claude talks to Conbersa through a bearer key. One thing to know up front: Claude's remote OAuth connector doesn't work here yet. The config below does.

Use it for Claude Code or Claude Desktop.

Prerequisites

  • A Conbersa API key (cb_live_...) from Settings → API keys.
  • Claude Code or Claude Desktop.

Configure Claude Code

Add Conbersa to your MCP configuration (.mcp.json in the project, or your user-level MCP settings):

{
  "mcpServers": {
    "conbersa": {
      "type": "http",
      "url": "https://api.conbersa.ai/mcp",
      "headers": { "Authorization": "Bearer cb_live_YOUR_KEY" }
    }
  }
}

Reload Claude Code. Run /mcp to confirm the conbersa server is connected with 22 tools.

Configure Claude Desktop

Edit claude_desktop_config.json and add the same entry:

{
  "mcpServers": {
    "conbersa": {
      "type": "http",
      "url": "https://api.conbersa.ai/mcp",
      "headers": { "Authorization": "Bearer cb_live_YOUR_KEY" }
    }
  }
}

Restart Claude Desktop after saving.

Note: The remote connector in Claude's connector directory uses OAuth and won't authenticate against Conbersa today. Adding Conbersa there will fail. Use the config above.

Verify

Ask Claude:

Use the conbersa server to list my devices.

You should get your fleet back. If not, see MCP troubleshooting.

What Claude can do

  • Inspect devices, prompts, personas, brands, and schedules.
  • Start and stop engagement runs, with a live session link.
  • Post media across platforms (experimental).
  • Create, edit, fire, and stop schedules.

Example prompts

Preview what each TikTok device would run for a lurk engagement, then start it.

Start my "Recovery — Instagram" prompt on the two free IG devices and give me the session link.

Schedule a full engagement for my three best TikTok devices every day at 10am Eastern.

Security

  • One key per client. Revoke them independently.
  • Keep keys out of source control. .mcp.json is often committed — use a user-level config or a .env reference instead.
  • If a config file gets shared, revoke its key in Settings.

Next

FAQ

Frequently asked questions

Not yet. Claude's remote connector expects OAuth, which the Conbersa MCP server does not implement. Use the bearer-key HTTP config for Claude Code or Claude Desktop instead — it connects to the same endpoint and exposes all 22 tools.
Claude Code uses a project .mcp.json or your user-level MCP settings. Claude Desktop uses claude_desktop_config.json in its application support folder. Either way, add Conbersa as an http server with an Authorization: Bearer cb_live_... header.
You can, but it is better to create a separate key per client. That way you can revoke one without disrupting the other. See API keys for how to create and revoke keys.