Skip to main content
Four routes run her from outside the app, and all four end in the same place: a post on your calendar. They ride the same Public API, so the result never depends on which one you picked.
The create-post cap is shared too. One instance-wide API_LIMIT per organization per hour, identical on every plan. Cloud and the shipped Compose files set it to 30; unset on your own instance it sits at 90. A chatty source reaches it faster than you expect, whichever route it came in on.
A draft keeps the date you gave it and does nothing until you publish it. Publish one weeks later and it can fire immediately, because that stored date is already behind you.

​
The four at a glance

​
Pick the CLI when

You are already in a terminal. Run postqueen integrations:list, copy the channel ID you want, and posts:create puts the post on the calendar. Almost every command prints JSON after a one-line header, so a shell script or a CI job can read the answer. The Scripting and CI section names the handful that print plain text instead. It is also the route an AI agent drives best, because the skill teaches your assistant the flags before it runs anything. Your numbers come back here too: analytics:platform and analytics:post have no equivalent in the MCP tool set or the n8n node, though the API carries them.
One thing is missing: the CLI does not generate video.
Every command and flag: Command Reference.

​
Pick MCP when

You want to describe the post rather than write the call. “Schedule a post to X for tomorrow at 10am” is the whole interaction, and the client picks the tools on its own: one to find your channels, one to read what X accepts, one to schedule. Point your client at a single URL and 11 tools arrive with their schemas. Among the four routes, AI image generation appears only here.
No tool reads analytics, and none lists or deletes an existing post. When you need those, keep the CLI installed alongside.
Copy-paste configuration for your client: Client Setup.

​
Pick the public API when

You are writing the code yourself, or you need something the other three never carry. This is the widest surface of the four, and the layer they all ride on. Several of its 22 key-authenticated operations stop right here.
Building for other PostQueen users? OAuth2 gives you tokens that act on their behalf, so nobody hands over an API key. Working in Node? @postqueen/node is a typed client where every method maps to one endpoint.

​
Pick n8n, Zapier or Make when

The trigger is not yours to build: a row in a sheet a client keeps filling in, an article going live, a Monday timer. Your tool already knows about all of that, and the only missing step is the post at the end. She can also take the first step herself, with no outside tool at all.

RSS AutoPost

She reads a feed hourly and drafts the newest item for you.

Webhooks

She calls your endpoint the moment a post goes live.

​
Next steps

CLI

Install it globally, export your key, and 16 commands are one line away.

MCP

One URL for your client, and 11 tools arrive with their schemas.

Public API

REST for your own code, with your API key as the only setup.

Automation

n8n, Zapier and Make, plus the two routes where she moves first.