Conbersa runs a fleet of real phones. Point Claude, ChatGPT, Cursor, opencode, or any MCP client at it, and the agent can post, engage, and schedule in plain language.
What Conbersa is and what it lets you automate: a fleet of real phones, AI agents that run accounts, multi-account posting, and scheduling.
Getting started3 minThe mental model behind Conbersa: devices hold accounts, runs execute tasks, sessions report status, and schedules repeat it all.
Getting started2 minCreate, use, and revoke Conbersa API keys. Every MCP request authenticates with a cb_live_ key — there is no unauthenticated mode.
The Conbersa MCP server exposes your device fleet as tools over Streamable HTTP at api.conbersa.ai/mcp. Connect Claude, ChatGPT, Cursor, or any MCP client.
MCP2 minConnect an MCP client to Conbersa in five minutes: create an API key, add the server, verify with list_devices, and start your first run.
MCP2 minAdd the Conbersa MCP server as a custom connector in ChatGPT using API-key auth, then operate your device fleet from chat.
MCP2 minConnect 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.
MCP2 minAdd the Conbersa MCP server to Cursor over Streamable HTTP so the agent can run and schedule your device fleet while you work.
MCP2 minAdd the Conbersa MCP server to opencode as a remote server in opencode.json so the agent can run, post, and schedule against your fleet.
MCP4 minEvery tool on the Conbersa MCP server: read, run, content, and schedule tools with parameters, return shapes, and when to use each.
MCP3 minCopy-ready patterns for using the Conbersa MCP server: fleet-wide engagement, previewing device behavior, multi-platform posting, and scheduled distribution.
MCP3 minFix the common Conbersa MCP connection and run errors: 401 missing or revoked key, 403 origin rejection, 421 host errors, and device-busy failures.
How Conbersa content runs work: ingest media from any public URL, then post it across platforms sequentially from one instruction. Experimental.
Platform3 minCreate, edit, fire, and stop Conbersa schedules: one-off or recurring, fixed time or randomized window, with per-day caps and per-platform content.
Platform3 minHow Conbersa devices work: pad IDs, platforms, prompt profiles, busy locks, and managed-for access. What to check before you start a run.
Conbersa runs the accounts for you. These docs assume you already have one, and an API key to match.