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.
Conbersa runs social accounts for teams that already make finished content. The managed service covers account setup, publishing and scheduled account activity on real phones. Your team supplies the videos, rights and direction; production and editing are not included.
The base plan includes 10 devices and 10 TikTok accounts for $1,000/month, with two months paid upfront. Instagram and Facebook are available as paid add-ons; YouTube Shorts requires a separate quote. See current scope and pricing.
Real phones do not make accounts immune to restrictions. Platform rules, content, activity and account history still matter. There is no guarantee of reach or account survival.
Managed service and optional technical controls
These docs describe the web app and MCP tools. The MCP server is optional; it is not a prerequisite for buying managed account operations. Confirm the supported platforms, content handoff and account-readiness timeline for your plan before starting.
The content-upload tools remain labelled experimental until their end-to-end multi-platform path is validated. That label describes those technical tools; it should not be treated as a blanket readiness claim for every managed workflow. Check the tool-specific limitations before relying on it.
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 handles account setup and recurring activity. Account restrictions remain possible.
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.