AI assistants over MCP
Reachio is an MCP server at https://reachio.talivio.com/mcp. Connect ChatGPT, Claude, Claude Code, Gemini CLI, Cursor, VS Code or Codex once; an owner or admin picks the agency, the brand and one of three levels on Reachio's consent screen:
- Read (the default): results, brands, connections, creatives, posts, Search Console, tracking health, Test Lab.
- Read and draft: also creatives, posts, content and launch plans sent for approval, and change requests.
- Read, draft, launch and approve: also launching approved campaigns (always paused), publishing approved posts and recording your own decision — each only after you say yes in the chat.
Step-by-step setup for every assistant is on the AI page.
For example, once connected you can ask: “Plan ads for the Abuzer Kadayıf shop: three square ads for the pistachio kadayif, a €20-a-day Meta campaign in Istanbul, then send it for approval.” (Abuzer Kadayıf is an example brand in the demo workspace.)
API keys
Owners and admins make keys under Agency → API keys. A key:
- starts with
rk_live_and is shown once (Reachio keeps only a hash); - has permissions: read (always), write (drafts, media, replies, ad change requests), publish approved posts, approve and reject;
- can be limited to one brand and given an expiry date, and can be revoked any time;
- acts as the member who made it, with that member's role.
Send it as Authorization: Bearer rk_live_… to https://reachio.talivio.com/api/v1. The OpenAPI description is at /api/v1/openapi.json. Each key may make 120 requests a minute.
The same rules as the panel
Neither a key nor an assistant can go around approvals. Ad changes made through them always wait for a person's approval; campaigns are created paused; everything is in the audit log. MCP and the API are part of Agency Pro and Scale, and free for everyone during early access.