Connect OpenClaw to LinkedIn: coming soon

Can OpenClaw post or comment on LinkedIn through Postgale?

Coming soon: LinkedIn is not available yet. A LinkedIn profile or Page cannot be connected in Postgale today, so nothing on this page works against LinkedIn yet. What is planned may change before launch.

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. Until LinkedIn is live, Dashboard → Accounts shows LinkedIn as “Coming soon”, and OpenClaw gets no LinkedIn account to act on.

What is planned for LinkedIn?

The plan is LinkedIn’s official Community Management API, with the same approval, audit log and revocable access as the other platforms. Details may change before launch:

• Posts from a personal profile or a company Page, each connected as its own account, with images, a video or a document.
• Mentions of people and companies, and a first comment.
• Comments and reactions on Page posts.
• Post and Page analytics, including follower demographics.

Set up OpenClaw with Postgale today

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 OpenClaw do through Postgale today?

An agent can publish today on Instagram, Facebook Pages, Threads, TikTok, Telegram, Discord, Bluesky and Mastodon, and answer customers on WhatsApp Business. X and LinkedIn are coming soon.

Nothing has to go out unreviewed. Approval can be required per workspace, per connected account, per API key or per signed-in app; while it applies, posts wait as pending approval in the dashboard, and replies, direct messages and edits to live posts are refused. Every write the agent makes is kept in the audit log.

Common questions