Conbersa Overview
What Conbersa is and what it lets you automate: a fleet of real phones, AI agents that run accounts, multi-account posting, and scheduling.
Most social media automation gets caught. Not because the code is bad, but because it isn't a phone. Platforms look at the device, the network, and the behavior behind an account, and emulators and browsers fail those checks.
Conbersa goes the other way. Real Android phones, one account each, driven by AI agents that post content and run organic engagement on TikTok, Instagram Reels, YouTube Shorts, and Facebook Reels.
The idea underneath it is small: software bots get banned; physical phones don't. Every account gets its own device, its own carrier IP, its own fingerprints, and weeks of ordinary behavior behind it. That is the difference between automation that gets flagged and distribution that compounds.
What can you automate?
- Multi-account content distribution. Post the same media across a fleet of accounts, platform by platform, from one instruction.
- Agentic engagement. Run saved prompts or free-form tasks that like, comment, follow, and search, each account following its own persona.
- Scheduling. Fire one-off or recurring runs at exact times or inside randomized windows, in any timezone.
- Media ingestion. Pull content from any public URL — Google Drive, S3, R2, Supabase, Dropbox, presigned links — and push it to the fleet.
How the pieces fit together
- The fleet — physical devices, each with a
pad_id, a platform, and a saved prompt profile. See Device fleet & pad IDs. - Runs — a session that executes a task across one or more devices right now. See How Conbersa works.
- Schedules — the same runs, on a timetable. See Scheduling runs.
- The MCP server — exposes all of it as tools any MCP client can call. See MCP server overview.
Two ways to drive it
The web app (app.conbersa.ai). The cockpit. Start runs, watch sessions live, manage prompts, personas, brands, and schedules, and create API keys.
The MCP server (api.conbersa.ai/mcp). Lets Claude, ChatGPT, Cursor, opencode, or any MCP-compatible agent call Conbersa directly. You ask in plain language; the agent picks the tools.
Both paths hit the same backend and the same fleet. Nothing is simulated.
What Conbersa is not
Conbersa is not a scheduler like Buffer, Hootsuite, or Later. Those tools queue posts to accounts you already own. Conbersa runs a fleet of real devices and accounts as a managed service, and does the warming, isolation, and health monitoring that keeps them alive.
Where to go next
- New here? Start with How Conbersa works.
- Connecting an AI client? Go to MCP quickstart.
- Need a key? See API keys.