AI Agent Ready
Every command returns structured JSON, so LLMs and pipelines can parse results and chain the next step without scraping text.
Point Claude, ChatGPT or your own scripts at the postqueen CLI and run your channels from the terminal. Every command speaks JSON.
npm install -g postqueen # Authenticateexport POSTQUEEN_API_KEY=your_api_keyEvery command returns structured JSON, so LLMs and pipelines can parse results and chain the next step without scraping text.
One CLI posts to X, LinkedIn, Reddit, Instagram, YouTube, TikTok and every other channel postqueen supports.
Compose threaded posts with per-item media and let postqueen convert them to each platform's native thread format.
Attach images, video, audio and documents: PNG, JPG, MP4, MOV, PDF and more upload straight from the command line.
Exact timestamps, drafts for review, and batch scheduling for whole campaigns from a single JSON file.
Discover each channel's extras at runtime: subreddit flairs, YouTube playlists, Pinterest boards, LinkedIn pages.
List your connected accounts and pull platform-specific options like flairs and playlists before you compose.
postqueen integrations:list # Get platform settingspostqueen integrations:settings <id>Quick posts with flags, or full campaigns from a JSON file: content, media, schedule and target channels in one call.
# Simple postpostqueen posts:create \ -c "Check out our new feature!" \ -m "screenshot.png" \ -s "2026-08-01T09:00:00Z" \ -i "x-id,linkedin-id" # Complex post from JSONpostqueen posts:create --json campaign.jsonList what's queued, upload media for reuse and pull per-platform or per-post analytics into your workflow.
# List scheduled postspostqueen posts:list # Get platform analytics (last 30 days)postqueen analytics:platform <id> -d 30 # Get analytics for a specific postpostqueen analytics:post <post-id> -d 7 # Upload media for reusepostqueen upload video.mp4Everything the CLI does is also available through the public API and the official Node SDK.
npm install @postqueen/node # Every capability of the public API:# posts, uploads, integrations, video# Base URLhttps://api.postqueen.ai/public/v1 # Authenticate with your API keyAuthorization: <POSTQUEEN_API_KEY>Each one has its own guide: how it connects, what it can do and the questions that come up. Anything that runs a shell command or calls an MCP tool works, these are just the ones written up.
Message your agent from the chat apps you already use and let it draft, schedule and publish through postqueen, completely hands free.
Set up OpenClawMessage Hermes from the chat apps you already use, or hand it one brief: it plans multi-step tasks and drives the postqueen CLI end to end.
Set up HermesQueue a week of content without leaving your terminal. Claude Code talks to postqueen over the CLI or the built-in MCP server.
Set up Claude CodeDraft with ChatGPT anywhere, then let postqueen fan the result out to every channel you run.
Set up ChatGPTLet OpenAI's software agent handle your posting pipeline: one prompt in, a scheduled week out.
Set up CodexManage your channels from the same editor you build in. Cursor's agent drives postqueen over the CLI or MCP.
Set up CursorAdd postqueen as a connector once on claude.ai and the scheduling tools follow you into the desktop app and your phone.
Set up ClaudeGoogle's open source terminal agent runs every postqueen command and reads the JSON back, so a week of posts is one prompt away.
Set up Gemini CLIAnything that can run a shell command or call an MCP tool. Claude, Claude Code, ChatGPT, Codex, Cursor, Gemini CLI, OpenClaw and Hermes each have a setup guide here, and your own cron jobs and CI runners work the same way.
No, they reach the same account with the same API key. The CLI is better when you want an exact command you can put in a script; MCP is better when you would rather describe the outcome. Most people end up using both for different jobs.
Never. Channels are connected once in postqueen over each platform's official OAuth, and the agent only ever holds a postqueen API key. Revoking that key cuts the agent off without touching your channel connections.
No, and it is the thing people most often get backwards. The agent creates the post; postqueen holds the schedule and publishes it. Once a post is on the calendar it goes out at its time whether the agent, the laptop or the CI job is still alive.
Yes. Ask for drafts and nothing is scheduled: the posts wait on the calendar with no time set until you give them one. It is the setup worth starting with, and most people move to direct scheduling once the output stops surprising them.
Yes. The CLI, the public API, the Node SDK, the n8n node and the MCP server are on every plan, and posts are unlimited on all of them. What your plan bounds is how many channels you connect.
Queue this week's posts in minutes, or hand the whole thing to your favorite AI. postqueen keeps publishing either way.
Seven days free. Cancel in one click from settings.