OpenClaw

OpenClaw is a personal AI agent you run on your own computer or server, with an always-on gateway to WhatsApp, Telegram, Slack, Discord and more. Give it the PostQueen CLI and skill, and you can message it from your phone to write, schedule and check your posts.

A sample OpenClaw chat on a phone with PostQueen connected: a request for posts, the PostQueen tools it used, and the reply

Before you start

Plans: OpenClaw is free and open source (MIT). You bring a model provider key, such as Anthropic or OpenAI, during its onboarding.
Platforms: wherever you run the OpenClaw gateway: macOS, Linux or Windows, with Node 24.16+ or 26.1+.
OpenClaw, installed and onboarded. Follow OpenClaw’s install guide; openclaw onboard --install-daemon sets up the gateway as a background service.
A PostQueen API key. A workspace admin copies it from Connections.

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.

Connect OpenClaw

OpenClaw uses PostQueen through the postqueen CLI, taught by the postqueen skill. Run these on the machine where the OpenClaw gateway runs.

Install the CLI and the skill

npm install -g postqueen
npx skills add GkhanKINAY/postqueen-agent -g -a openclaw

The skill teaches OpenClaw the PostQueen commands; the CLI runs them. The postqueen skill explains what it covers.

Sign the CLI in

On the computer the gateway runs on, under the same user account, run:

postqueen auth:login

A workspace Admin or Super Admin approves it in the browser. The CLI saves the login in ~/.postqueen/credentials.json, which the gateway’s commands read too.If the gateway runs on another machine or user, with no browser, give it the key instead. A key you export in your own terminal does not reach a background gateway, so put it in openclaw.json:

openclaw.json

{
  skills: {
    entries: {
      postqueen: {
        env: { POSTQUEEN_API_KEY: "YOUR_API_KEY" },
      },
    },
  },
}

Or set POSTQUEEN_API_KEY in the environment the gateway service starts with. Restart the gateway after either change.

Check that the skill is eligible

openclaw skills list --eligible

postqueen must be in the list. OpenClaw counts the skill as eligible when the postqueen command is on the PATH.

Check that it works

Message OpenClaw, from its chat or a linked chat app: “List my PostQueen channels.” It runs the CLI and answers with the channels you connected. To link WhatsApp, Telegram, Slack or Discord, see Chat channels.

Good to know

The gateway has to be running to answer your messages. A machine that sleeps means an agent that goes quiet.
OpenClaw can install the CLI and the skill itself if you allow it. You still give it the key.
The CLI can do more than MCP: it can also delete a post. See the CLI for every command.
Ask for drafts when you want to check first. A draft waits on your PostQueen calendar, and nothing publishes until you schedule it.

Other ways to connect

Way	Address	Notes
The CLI and the skill	No address	From OpenClaw’s docs. The route above
MCP with the Bearer header	`https://api.postqueen.ai/mcp`	Keeps the key out of the address
Sign in with PostQueen	`https://api.postqueen.ai/mcp-oauth-dynamic`	A workspace admin approves the sign-in

openclaw mcp add postqueen --url https://api.postqueen.ai/mcp \
  --transport streamable-http \
  --header "Authorization=Bearer YOUR_API_KEY"
openclaw mcp probe postqueen

Set the transport: OpenClaw assumes SSE when it is left out. MCP tools appear in the coding and messaging tool profiles, not in minimal.

Add the server with --auth oauth and the address https://api.postqueen.ai/mcp-oauth-dynamic, then run:

openclaw mcp login postqueen

A workspace admin signs in to PostQueen and approves. The sign-in address has 21 tools, all but ask_postqueen. Revoke access in PostQueen under Connections > Approved Apps.

Try this first

List my PostQueen channels. Then write a short Bluesky post about today's special and save it as a draft for 5pm.

The draft appears on your PostQueen calendar, ready for you to check and schedule.

Run it on a schedule

The OpenClaw gateway has a scheduler: it wakes the agent at the job’s time and can send the result to a chat channel. openclaw cron works as an alias for the same commands.

openclaw automations create "0 9 * * 1-5" \
  "Save one post from today's notes as a PostQueen draft." \
  --name "Daily draft" --session isolated

Source: OpenClaw, managing scheduled jobs.

Troubleshooting

Symptom	Fix
`postqueen` is not in `openclaw skills list --eligible`	Put the `postqueen` command on the `PATH`.
The gateway does not see your login or key	Run `postqueen auth:login` as the user the gateway runs as. An `export` in your terminal does not reach a background gateway, so a key goes in `openclaw.json`, then restart the gateway.
MCP connects but no tools appear	Add `--transport streamable-http`. Without it OpenClaw assumes SSE.
The key is refused	Copy it again from Connections > API Keys. Only a workspace Admin or Super Admin can reveal it.
You followed a NanoClaw guide	NanoClaw is a different app with its own setup. See NanoClaw.

More fixes are on Troubleshooting agents.

Is it the same as NanoClaw?

No. The names are close, but they are different apps with different setups:

Product	What it is	How it connects
OpenClaw (this page)	A personal agent with an always-on gateway to your chat apps	The PostQueen CLI and skill
NanoClaw	An assistant that runs each agent in its own container	PostQueen’s MCP server, with the key in its vault

Next steps

Every agent

Which agents can post to PostQueen, and how each one connects.

The MCP tools

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

Prompts and tool calls

The order an agent calls the tools in, with prompts that work.

Troubleshooting agents

What to do when a connection or a command fails.

Start here

Assistants and bots

Coding agents

Editors and more

MCP reference

CLI reference

Troubleshooting

Before you start

Connect OpenClaw

Check that it works

Good to know

Other ways to connect

Try this first

Run it on a schedule

Troubleshooting

Is it the same as NanoClaw?

Next steps

Every agent

The MCP tools

Prompts and tool calls

Troubleshooting agents

​Before you start

​Connect OpenClaw

​Check that it works

​Good to know

​Other ways to connect

​Try this first

​Run it on a schedule

​Troubleshooting

​Is it the same as NanoClaw?

​Next steps

Every agent

The MCP tools

Prompts and tool calls

Troubleshooting agents

Before you start

Connect OpenClaw

Check that it works

Good to know

Other ways to connect

Try this first

Run it on a schedule

Troubleshooting

Is it the same as NanoClaw?

Next steps