API and MCP
The API opens at launch. Want early access? Let us know.
Every paid plan includes a REST API and an MCP server.
This page is the overview. The full reference lives at docs.ploffo.com.
Basics
| REST API | https://api.ploffo.com/v1 |
|---|---|
| MCP server | https://mcp.ploffo.com |
| Format | JSON, UTF-8, ISO 8601 timestamps with time zone |
| Docs | docs.ploffo.com |
| Status | status.ploffo.com — opens at launch |
The API works per workspace. A key gives access to the workspace it was created in.
Authentication
Create an API key in the app, under your workspace settings.
Send it in the Authorization: Bearer <key> header. Treat it like a password: anyone with the key can schedule on your behalf.
The MCP server accepts the same key, or lets you sign in with OAuth.
Schedule a post with curl
This request schedules a post for Wednesday 7 October at 09:00 Belgian time. The Idempotency-Key header makes sure a request sent twice by mistake doesn’t create a second post. Look at the time in the response: you schedule 09:00 in Brussels, the system stores 07:00Z and remembers the time zone.
curl -X POST https://api.ploffo.com/v1/posts \
-H "Authorization: Bearer $PLOFFO_API_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: $(uuidgen)" \
-d '{
"channelIds": ["ch_7k2m"],
"body": "A number without a source is an opinion.",
"runAt": "2026-10-07T09:00:00+02:00"
}'Response
{
"id": "post_9fq3",
"status": "scheduled",
"runAt": "2026-10-07T07:00:00Z",
"timezone": "Europe/Brussels",
"channels": [{ "id": "ch_7k2m", "platform": "linkedin", "name": "ceeme" }]
}MCP server
MCP is the standard AI assistants use to call tools. Add the Ploffo server and your assistant can schedule and follow up in plain language.
This is the configuration for a client that supports remote MCP servers:
{
"mcpServers": {
"ploffo": {
"url": "https://mcp.ploffo.com",
"headers": { "Authorization": "Bearer <your-key>" }
}
}
}The tools
list_channels | The connected channels. |
|---|---|
create_post | Create a post. |
schedule_post | Schedule a post for a date and time. |
list_schedule | What is scheduled. |
cancel_scheduled_post | Cancel a scheduled post. |
create_approval_round | Start an approval round: link and PDF for a set of posts. |
get_publication_proof | The proof of a publication: what, when, and the public link. |
get_usage | Your usage in the current month. |
Assistants
Works in Claude, ChatGPT, Cursor and any assistant that speaks MCP. You write where you already write; Ploffo schedules.
Connect your assistant or platform
Your assistant
Every assistant below speaks MCP. The server is the same for all of them — https://mcp.ploffo.com — only the way you add it differs per assistant.
- ClaudeCustom connector, under Customize.
- ChatGPTDeveloper mode, per workspace.
- CursorOne block in mcp.json.
- Claude CodeOne line in the terminal.
- CoworkThe same connector as Claude.
- CodexOne block in config.toml.
Your automation stack
A scenario in n8n or Make can call the Ploffo server too, with no one typing anything.
Documentation
Every endpoint, field, error code and limit is at docs.ploffo.com.
Questions we get a lot
Which plans include the API?
Every paid plan: Solo, Studio and Agency. You get both the REST API and the MCP server.
What is an MCP server?
MCP (Model Context Protocol) is an open standard that lets AI assistants use external tools. With the Ploffo server, an assistant can schedule posts, request sign-off and check their status.
Can a post created through the API skip approval?
No. A post is only scheduled after you have approved it, even when it arrives through the API. Whether you also put it to your client is a choice per post.
Are there rate limits?
Yes, per key. The current limits are in the docs.
Scheduled. Signed off. Proven.
No card. 14 days. No commitment.
