Skip to main content
An AI agent can do in PostQueen much of what you do in the app: list your channels, write and schedule posts, add images and videos, and read how published posts did. Every post it makes lands on your calendar. A draft or a scheduled post waits there, so you can check it, change it or delete it before it goes out.
A Claude chat next to the PostQueen calendar. Claude used three PostQueen tools, and four posts for next week are on the calendar.

Three ways to connect

MCP server

For chat assistants and most coding agents. Paste one address and the agent gets 22 tools. Nothing to install.

CLI and skill

For agents that run shell commands, and for your own scripts. The postqueen command, plus a skill that teaches it to the agent.

Public API

For your own apps and automations. REST calls with your API key.
Use MCP when your agent supports it: it finds the tools on its own. Use the CLI when the agent works in a terminal, or when you need something MCP cannot do yet. Connect channels and edit a post’s text or time in the app.

Before you start

  • A PostQueen workspace on a trial or a paid plan. Agents post through your workspace, so its plan limits apply to them too.
  • A workspace admin. Only an Admin or Super Admin can reveal the API key or approve a sign-in.
  • At least one connected channel. An agent posts only to channels you connected in the app. See connect a channel.
Where the API key is: in the app, open Connections > API Keys. Only a workspace Admin or Super Admin can reveal or rotate it; other members see it masked. A workspace has one key, and each agent card on Connections shows your MCP address with the key already filled in.

Every agent

How it connects is what you set up in the agent. Sign-in or key says whether the agent can sign in to PostQueen or takes your API key.

Assistants and bots

Coding agents

Editors and more

Muse and Muse Code are two different Meta products. Muse Code, the coding agent, connects with the key address. Muse, the personal agent, connects through a custom connector it builds with you in chat.
Using an agent that is not listed? If it can reach a remote MCP server, give it the key address: other MCP clients. If it runs shell commands, give it the CLI and the skill. To post from WhatsApp, Telegram, Slack or Discord, see post from chat apps.

You stay in charge

Drafts wait for you

Ask for drafts and they stay on your calendar until you schedule them.

Every post on your calendar

You see each post before it goes out, and you can edit or delete it until its time.

Access you can take back

An admin rotates the API key under Connections > API Keys, which stops every agent that used it, or revokes one sign-in under Connections > Approved Apps.

No social passwords

The agent never sees the passwords of your social accounts. It works through PostQueen, which posts with each network’s own API.

Next steps

The MCP server

The three addresses, what each one gives an agent, and how to check it works.

The MCP tools

What each of the 22 tools does, and what an agent cannot do.

The CLI

Install postqueen, set the key and schedule a first post from a terminal.

Troubleshooting agents

What to do when a connection or a command fails.
Last modified on September 24, 2026