The API and the MCP server

Two ways, one rule

You can drive Ploffo from outside in two ways, and both follow the rule that holds everywhere in Ploffo: nobody signs off for someone else.

What that means in practice depends on your setup, and it is worth being precise about:

• If someone still has to approve — your client through the approval link, or an approver on your team — then a post arriving through the API or an assistant always lands as a proposal. No key and no setting gets past that. It is exactly what this product exists for.
• If you are the only approver, then your call is the tick. You prepared the post yourself, with your own key; there is no screen where you would have to give yourself permission a second time. It goes straight into the schedule.

That keeps the promise intact without making you do a step that adds nothing.

The API

An ordinary HTTP endpoint at api.ploffo.com/v1. You use it to create posts from your own system: a web shop that prepares a post for every new product, a till system that passes on opening hours, your own planning tool.

The full example with fields and response is on the API page.

The MCP server

MCP is how AI assistants talk to programs. Connect mcp.ploffo.com and your assistant — Claude, ChatGPT, Cursor, or any other that speaks MCP — can work inside your Ploffo itself: prepare a post, read the calendar, pull up a file.

That is not the same as a chat window inside the app. You work in your own assistant, with your own context around you, and Ploffo is a tool in it.

Keys

You create them in the app. A key belongs to one workspace, so you can revoke it without touching the rest.

Before launch

The API and the MCP server open at launch. Want early access? Let us know — we will put you on it the moment it opens.