Summary
Scheduling posts without opening the scheduler.
Reading the connected integrations first is what makes this usable in practice: the post is created against channels that exist, rather than against the ones you assumed were connected.
What it is
An MCP server over the Postiz API. It points at your Postiz instance with an API key, and ships stdio, SSE and HTTP transports plus a Docker image that runs as a non-root user.
What you get
- A post created for the channels Postiz has connected
- The posts already scheduled or published, read back
- The integrations — the social accounts connected to the instance — listed
- The account the API key belongs to, and a login call
- Stdio, SSE or HTTP transport, and a health-check endpoint
Requirements
A Postiz instance and an API key — the instance URL and the key both go in the environment, with PORT defaulting to 3084. Docker Compose brings it up in one command.
Setup effort
One command plus a key — docker-compose up -d, then supply credentials