Postonus docs
Three ways to drive Postonus from outside the dashboard — an AI assistant over MCP, a REST API, and a CLI.
Last updated on
Postonus schedules and publishes social media posts. Everything the dashboard does is also reachable from outside it, through one of three surfaces.
Pick a surface
| You want to | Use | Start here |
|---|---|---|
| Let Claude, ChatGPT, or Cursor read your queue and stage posts | MCP server | MCP |
| Call Postonus from your own code, a backend, or CI | REST API | API |
| Post from a terminal, a script, or a GitHub Action | CLI | CLI |
All three call the same operations. The MCP server needs no API key — you approve it in a browser. The API and the CLI both authenticate, and the CLI can use either a signed-in session or a key.
New to Postonus? Getting started covers the first workspace, the first channel, and the first post.
What an assistant should read
If you are an AI agent rather than a person, For agents is the map: every page here has a markdown twin, and the site publishes an index at /llms.txt.