ScheduleLaterMCP integration for developers
Give your agent a scheduling arm. The ScheduleLater MCP server runs on your machine, talks to the same API the app uses, and keeps a human in the loop by default.
| Tool | What it does |
|---|---|
list_brands | The workspace’s brands, so an agent can target the right identity. |
list_accounts | Connected accounts with platform and state. |
resolve_accounts | Turns human account references into exact account ids. |
list_posts | Posts with status, schedule and targets. |
get_post | One post in full, media and outcomes included. |
upload_media | Uploads local files, with covers and platform validation applied locally first. |
create_post | Creates a draft or scheduled post, idempotent per call. |
Scopes that mean what they say
API keys are minted per workspace by an owner or admin, with two-factor step-up required to create one. Each key carries only the scopes you grant.
- read
- List and inspect brands, accounts and posts.
- media:write
- Upload media, including covers.
- posts:draft
- Create drafts that wait for a human.
- posts:schedule
- Arm posts with a time. Withhold this to keep approval human.
Built for the failure cases
Idempotency keys on creation, so a retried call cannot double-post. Platform rules validated locally before an upload starts, with the real limits in the error message. One indistinguishable rejection for every invalid key, so the API is not an oracle.
What is the MCP server, exactly?
A small program you run on your own machine that speaks the Model Context Protocol to your agent and authenticated HTTPS to ScheduleLater. Your API key stays on your machine; every call lands on the same audited API the app uses.
Can an agent publish without a human?
Only if you grant the posts:schedule scope. The recommended setup withholds it, so agents stage drafts and a person approves everything that goes live.
What can a key never do?
A key always acts as a member, regardless of who minted it: it can never delete posts, retry publishes, manage accounts, brands or other keys, or touch settings. Revoking a key is instant and never requires two-factor.
Is there a public REST API?
Not beyond this. Machine access is deliberately scoped to the MCP surface: the routes it needs accept API keys, everything else requires a signed-in session.
Mint a key and point your agent at it
Key management lives in workspace settings inside the app.