Your agent just learned to publish
Point any MCP client at one URL. Pharlo absorbs every platform's OAuth, quota and upload surface — your AI ships posts, pulls analytics, and runs approval workflows through plain conversation
Connect in three clicks.
No SDKs in the way
Point your AI client at our MCP URL. OAuth discovery and dynamic client registration happen automatically — Pharlo issues tokens, refreshes them, and rotates them upstream of your model
https://pharlo.io/_mcppharlo_live_… key — tokens issue instantly, scoped to the channels you've already connected 17 tools.
One conversation
Every MCP tool maps 1:1 to a Pharlo REST endpoint. Same payloads, same credits, no AI surcharge — and every platform change is our problem, not your prompt's
Upload to YouTube or Facebook, set title, description, tags, schedule. Update or cancel after the fact. The same payload shape whether it lands as a video, a Reel, or a Short
Views, watch time, subscriber growth, side-by-side channel comparisons — your agent reads live numbers from a normalized schema, not seven different platform shapes
Connect channels and pages, watch token health, refresh credentials before they expire, audit who's linked to what. Operational housekeeping your agent does for you
Wire the MCP into Cursor, Windsurf, n8n, or your own agent runtime. Generate the content, get approval, publish on cadence — the platform-integration tax sits with us
Battle-tested by TheSoul Group
Pharlo MCP is the same posting infrastructure that runs TheSoul Group — a decade of daily publishing across YouTube, Meta, TikTok and Snapchat. When a platform changes its API on Tuesday, we've already shipped the fix in production. Your agent inherits that operational scar tissue on day one
Same credits
for REST and MCP
Every MCP tool call costs the same as the REST endpoint behind it. 1 credit = $0.001. No AI surcharge, no per-tool tax, no surprise renegotiations when a platform changes its quota
| Operation | Tier | Credits | Cost |
|---|---|---|---|
| Publish to channel Submit a video for delivery to YouTube, Meta, or any connected platform — webhook included | Publish | 25 credits | $0.025 |
| Retry a failed publish Re-queue a failed assignment without re-processing intake | Retry | 5 credits | $0.005 |
| Live platform stats Real-time views, likes, and engagement pulled directly from YouTube / Meta APIs | Platform | 2–3 credits | $0.002–0.003 |
| Update, cancel, or modify Patch a pending assignment, cancel a scheduled one, or update a connection | Write | 2 credits | $0.002 |
| Read — list or fetch detail Any GET on assignments, connections, or webhook delivery logs | Read | 1 credit | $0.001 |
| Auth, OAuth, account & team management Login, token refresh, organizations, invitations, platform discovery, health checks | Free | Free | $0 |
CEILING(size_GB × 25, 1). MCP tool calls use the exact same credit costs as the
equivalent REST endpoint — no surcharge for AI
integrations
Start with $5 — get 5,000 credits
Enough to publish ~200 standard videos, run thousands of reads, and fully exercise both the REST API and MCP server before you commit to anything bigger