Connect OpenClaw to Bluesky

Can OpenClaw post to Bluesky?

Postgale is the secure layer for AI agents on social media. MCP (Model Context Protocol) is the open standard that lets AI assistants such as Claude and Cursor use outside tools. An MCP server is what they connect to. OpenClaw does not reach Bluesky on its own; with Postgale connected it gets tools for the Bluesky accounts you connected and nothing else.

What do you need?

• A Bluesky account and an app password (Settings → Privacy and security → App passwords). Never your account password.
• A Postgale workspace, and a sign-in or an API key for the agent.
• Optional images or a video on a public HTTPS URL (upload them with upload_media).
• OpenClaw, set up as below (A remote MCP server or a skill that calls the REST API, with an API key).

Step 1: connect your Bluesky account

1. In Bluesky, open Settings → Privacy and security → App passwords and add one named Postgale.
2. Create a Postgale workspace, open Dashboard → Accounts → Bluesky and enter your handle and the app password.
3. Connect your AI tool: add https://postgale.com/mcp in ChatGPT, Claude or Cursor and sign in to Postgale, or create a key under Dashboard → API keys for n8n or your own code.
4. Ask the agent for a draft first. Turn on approval in the dashboard if a person should sign off before anything goes live.

From your own code, POST /api/v1/connect/bluesky with the handle and app password connects the account directly. Postgale stores the app password encrypted and renews the session by itself.

Step 2: connect OpenClaw to Postgale

1. In Postgale, open Dashboard → API keys, create a key and copy it (it starts with sk_ and is shown once). Connect the social accounts the agent may use under Dashboard → Accounts.
2. An agent that runs on its own, on a schedule or from a chat app, should use a key with approval required: create the key, then turn on approval for it under Dashboard → API keys. Everything it wants to publish, reply or send then waits for a person.
3. Store the key where OpenClaw reads secrets, for example an environment variable POSTGALE_API_KEY on the machine it runs on. Do not paste it into a chat.

Step 2a: add Postgale as an MCP server

Add a remote MCP server in OpenClaw’s configuration with these values. Field names and file locations depend on your OpenClaw version and setup; check its documentation for where MCP servers are declared.

URL:        https://postgale.com/mcp
Transport:  Streamable HTTP
Header:     Authorization: Bearer sk_…

Clients that take the common mcpServers JSON shape accept it like this:

{
  "mcpServers": {
    "postgale": {
      "url": "https://postgale.com/mcp",
      "headers": {
        "Authorization": "Bearer sk_…"
      }
    }
  }
}

What can I ask OpenClaw to do on Bluesky?

Check the connection first: “Which Bluesky accounts are connected in Postgale?” Then, in plain language:

Ask your agent“Post this announcement to Bluesky with the link to the launch post as a card.”

Ask your agent“Split this paragraph into a Bluesky thread, 300 characters per post at most. Drafts only.”

Ask your agent“Show me today’s Bluesky mentions and draft replies.”

{
  "content": "ignored",
  "platforms": [
    {
      "accountId": "acc_bsky",
      "platformSpecificData": {
        "threadItems": [
          {
            "content": "Release 2.4 is out 🎉",
            "mediaUrl": "https://media.example.com/screenshot.png",
            "altText": "The new dashboard"
          },
          {
            "content": "Faster sync and dark mode."
          },
          {
            "content": "Full changelog: https://example.com/changelog"
          }
        ]
      }
    }
  ],
  "publishNow": true
}

Which Bluesky rules does Postgale enforce?

• Text is limited to 300 characters as Bluesky counts them (an emoji counts once); a longer post is refused before it reaches Bluesky.
• Images: JPEG, PNG, WebP or GIF, up to 1 MB each and 4 per post. Video: one MP4 up to 100 MB and 3 minutes. Images and video are not mixed.
• Mentions of handles that do not exist stay plain text instead of breaking the post.
• Only app passwords are accepted. If you delete it in Bluesky, the account is marked as needing reconnection and your webhook hears about it.
• When Bluesky asks to slow down, Postgale waits until the limit resets before retrying.

How do I keep a person in the loop?

• Approval: tick “Hold posts from this app for approval” when you sign in, or in the Postgale dashboard require approval for the API key the agent uses (or for the whole workspace, or one account). Posts then wait as pending approval; comment replies and moderation, direct messages, WhatsApp sends and edits to live posts wait in the same queue. A person approves, edits or rejects each one in Dashboard → Approvals; the agent’s own key or sign-in cannot approve.
• Tool annotations: every Postgale tool declares whether it only reads, writes, or publishes live, deletes or spends. Clients that honour annotations ask before destructive tools run.
• Audit log: every write the agent makes is recorded with the key or the connected app, the action and the time.
• Revoking: each sign-in appears under Dashboard → Connected apps and each key under Dashboard → API keys; either can be revoked at any time.

What can’t an agent do on Bluesky through Postgale?

• Edit a post. Bluesky posts cannot be edited; delete and post again instead.
• Read likes, reposts or views yet.
• Send direct messages.

Common questions