MCP & API
The entire product is drivable by AI agents. ReachPill ships a Model Context Protocol server with the full tool set — plan campaigns, generate media, review the queue, draft blog posts — over a single endpoint.
The endpoint
https://app.reachpill.com/mcp
Streamable-HTTP MCP. Two ways to authenticate:
- •OAuth 2.1 (recommended for assistants) — paste the URL into any MCP-capable client (Claude connectors, ChatGPT, etc.). Discovery, registration and consent are handled automatically; you approve the org being connected.
- •API keys (for scripts and servers) — create an
mg_live_key inSettings → MCPand send it asAuthorization: Bearer mg_live_…. Keys are org-scoped and revocable.
Connect from Claude Code
claude mcp add --transport http reachpill https://app.reachpill.com/mcp
Claude Code walks the OAuth flow in the browser on first use. There's also a drop-in SKILL.md downloadable from Settings → MCPthat teaches an agent the product's workflows, not just its endpoints.
What the tools cover
- •Campaigns — create, plan arcs, preview cost, list and update; approve, reject, skip or reschedule occurrences.
- •Generation — images and video across the model catalog, compositions and recipes, cost estimation.
- •Blog — create, generate, update and publish posts (git or webhook).
- •Social — schedule, update and cancel posts; list connected accounts and slots.
- •Brand — read and update the Brand DNA, remember and forget facts.
- •Account — balance, usage summaries and spend breakdowns.
Tools that generate content are marked as credit-spending and bill the org like any other generation — agents can check
Next: Credits & billing →get_balance and estimate_cost first.