MCP Server Overview
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.
An AI agent is only as useful as the hands you give it. Conbersa's MCP server is the hands. It speaks Streamable HTTP at one address:
https://api.conbersa.ai/mcp
It runs inside the same process as the rest of the Conbersa backend, so tools start real sessions and read live state directly. No polling, no queue, no waiting on another system.
Why it exists
MCP is becoming the standard way to hand an AI agent a set of tools. Connect the Conbersa server and the agent can:
- list your devices and see which are free,
- start an engagement run and hand you a session link,
- post media across platforms,
- create and fire schedules,
- and report status — all in plain language.
You never write a request payload. You say what you want, and the agent picks the tool and fills in the arguments. That is what makes Conbersa usable from Claude, ChatGPT, Cursor, opencode, or any custom agent that speaks MCP.
Transport and auth
| Property | Value |
|---|---|
| Transport | Streamable HTTP |
| Endpoint | https://api.conbersa.ai/mcp |
| Auth | X-API-Key: cb_live_... or Authorization: Bearer cb_live_... |
| Local dev endpoint | http://localhost:8080/mcp |
| Unauthenticated mode | None |
Every request carries a valid key. See API keys to make one.
What the server can do
The server exposes 22 tools in four groups:
- Read — devices, prompts, personas, brands, schedules, sessions, and content runs.
- Run — start, preview, and stop agentic engagement runs.
- Content — ingest media and post across platforms. Currently experimental.
- Schedules — full create / edit / delete / run-now / stop parity with the web app.
See the full tool reference for arguments and return shapes.
Trusted clients
The server's DNS-rebinding guard allows its public host plus the origins that common MCP clients use, including Anthropic Claude, ChatGPT, and Cursor. Auth is enforced per request regardless of origin. Operators can add hosts with MCP_ALLOWED_HOSTS and MCP_ALLOWED_ORIGINS.
Current limitations
- Content tools are experimental until the multi-platform posting path is validated end to end.
- Claude's remote OAuth connector is not supported yet. Use the bearer-key config for Claude Code or Claude Desktop, or ChatGPT's API-key auth. See Connect Claude.
- Live viewing is not streamed over MCP. Open the session link for video; use the status tools for programmatic checks.
Next
- MCP quickstart — connect in five minutes.
- Connect ChatGPT, Claude, Cursor, or opencode.