Connect Cursor to Conbersa

Cursor connects to Conbersa as a remote MCP server, so the coding agent can start runs, post content, and manage schedules while you're in the editor.

Prerequisites

• A Conbersa API key (cb_live_...) from Settings → API keys.
• A Cursor version that supports remote MCP servers with headers.

Add the server

Create or edit ~/.cursor/mcp.json (global) or .cursor/mcp.json (project):

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

Then open Cursor's MCP settings panel and enable the conbersa server. It lists the available tools.

Verify

Ask Cursor:

List my Conbersa devices.

A fleet response means you're connected. If not, check MCP troubleshooting.

Example prompts

Preview a lurk engagement for these three TikTok pad IDs and tell me what each device will do.

Start a content run posting sample.mp4 to TikTok and Instagram, then give me the session link.

List my schedules and stop the one named "Nightly warmup".

Notes

• Project configs get committed. A .cursor/mcp.json with a live key in a shared repo is a leak. Use the global config, or a project config that pulls the secret from your tooling.
• One key per machine keeps revocation simple.

Next

• Connect opencode.
• Tool reference.