The real workflow, not a lookalike
Over 25 tools cover drafts, uploads, review, approval, scheduling, campaigns and status, on the same services the app runs on.
Profaily for developers
The publishing layer for whatever you’re building
Profaily’s MCP server gives your agent, script or tool the same publishing workflow the app uses: drafts, review, scheduling and status.
Built for how developers work
Sign-in you would expect
Users connect with OAuth. Scopes separate reading, writing and publishing, and a producer’s approval rules still apply.
Safe to call twice
Writes take an idempotency key. Scheduling shows a preview first and only commits when you confirm.
Made for agents
Inputs and outputs are schemas, errors say what to do next, and video bytes never travel through a tool call.
Connect
OAuth in, scoped tools out
A client discovers the server through its OAuth metadata, the user signs in to Profaily, and the client receives only the scopes it asked for.
- Read, write and publish scopes
- Role checks happen on the server, not in your prompt
- Works with Claude, ChatGPT and other MCP clients
Preview
Show the plan, then commit it
Scheduling tools take a confirm flag. Call with confirm: false to get exactly what would go out and when, show it to a person, then call again with confirm: true.
- The preview names the time and every destination
- A stale version returns POST_STALE instead of overwriting
- The same call with the same key does not double-post
// 1. what would happen?
schedule_post({
post_id: "7d1c…",
version: "2026-10-29T21:50:12Z",
scheduled_at: "2026-10-30T09:00:00+01:00",
confirm: false,
idempotency_key: "plan-7d1c-1"
})
// → { confirmed: false, scheduled_for: "…09:00", valid: true }
// 2. do it
schedule_post({ …same, confirm: true,
idempotency_key: "plan-7d1c-2" })Review
Approval is part of the API
An editor’s agent sends a video for review. A producer’s agent, or the producer in the app, approves it. The rules your team set do not change because the caller is code.
- send_for_review, approve_review, request_changes
- Approving schedules the video in a second, confirmed call
- Every step lands in the same history as in the app
Upload
Bytes go to storage, not through the tool
Ask for an upload session, send the file to the short-lived signed URL, then register it. Or point Profaily at a link and let it fetch.
- create_video_upload and upload_video
- import_video_from_link for Drive, Dropbox and OneDrive
- Files are checked before they can be scheduled
Questions people ask first
Something else? Email support@useprofaily.com.
Is there a public REST API?
Not yet. The MCP server is the integration surface today. If you need a REST endpoint, tell us what you are building.
Which clients work with it?
Any MCP client that supports OAuth, including Claude and ChatGPT.
Are there rate limits?
Yes. Each plan includes a monthly allowance of AI app calls, and tools are limited per minute to protect your channels and ours.
Can my agent publish without a human?
It can on accounts where it holds publish permission. On teams that use approvals, it can only send for review, and a producer approves.
Do I need a paid plan to try it?
Business starts with a 14-day free trial, and every plan includes AI app calls.
Discover 
Profaily
Give your agent a publishing layer
Connect Claude or ChatGPT in a minute and see the tools for yourself.
