OpenClaw

OpenClaw Social Media MCP Setup

OpenClaw registers a social media MCP server from the command line rather than a config file you hand-edit. Run openclaw mcp add with the Blotato URL and a header, and the server joins OpenClaw's own client-side registry, which it then projects into eligible runtimes. Because OpenClaw is self-hosted you get both auth paths: a header for unattended runs, or openclaw mcp login for OAuth.

Endpoint https://mcp.blotato.com/mcp OAuth or header

Connect OpenClaw See pricing

Updated August 2026

How to connect OpenClaw to social media

Connect your social accounts in Blotato and copy your API key from Settings then API.
Register the server: openclaw mcp add with --url https://mcp.blotato.com/mcp and a --header flag carrying your key.
Check it registered with openclaw mcp list, then openclaw mcp probe blotato to connect and confirm the tools it exposes.
For OAuth instead of a header, use openclaw mcp login rather than passing --header.

One CLI command, no config file to edit

openclaw mcp add blotato --url https://mcp.blotato.com/mcp --transport streamable-http --header blotato-api-key:YOUR_API_KEY

How do I know it worked?

Ask OpenClaw to list your connected accounts. It calls blotato_list_accounts and returns your platforms, which confirms both the connection and the authentication in one step. If you see your accounts, setup is done.

First prompt to run

What social media accounts do I have connected?

An AI agent answering "what social accounts do i have connected?" by calling Blotato and listing 10 connected social media accounts across Twitter, Bluesky, Instagram, Threads, LinkedIn, Facebook, YouTube, Pinterest, and TikTok — The reply you are looking for: the agent calls Blotato and lists every connected account. Here it returns 10 accounts across all nine platforms.

Worth knowing before you rely on it: analytics prompts only return data for X, Instagram, Facebook, Threads, and Bluesky. The other four platforms publish normally but report no metrics yet.

What to ask OpenClaw once it is connected

Every morning, turn yesterday's notes into a post and publish it.: A scheduled OpenClaw run ending in blotato_create_post. This is the unattended case the header auth exists for, since an expired OAuth session on a self-hosted agent stops publishing with nobody watching.
Did anything fail overnight?: blotato_list_posts plus blotato_get_post_status on anything still pending. Worth logging, because an async publish that failed at 3am looks identical to one that never ran.
Show me what tools this server actually exposes.: openclaw mcp probe blotato connects and reports them. Note that openclaw mcp tools is a different command: it sets the include and exclude filters, which is how you hand an unattended agent publishing without the tools that spend credits.

What breaks, and how to fix it

The consideration specific to a self-hosted agent is that nothing supervises it. If you run OpenClaw unattended, the header path is safer, because an OAuth session that expires while nobody is watching turns into an agent that silently stops publishing rather than one that prompts you to reconnect. If tools do not appear, openclaw mcp doctor checks the saved definition for local problems and openclaw mcp probe connects to the server for live proof, which is the pair worth running before you start editing config by hand.

What is different about OpenClaw

OpenClaw is the only client here that is both an MCP server and an MCP client: openclaw mcp serve exposes OpenClaw itself, while the other subcommands manage outbound servers like Blotato. It also has a real CLI registry with doctor and probe diagnostics, so you debug a connection with commands rather than by re-reading a JSON file, and per-server include and exclude filters so an unattended agent can hold the publishing tools without the ones that spend credits.

Vendor documentation: OpenClaw MCP setup. For how a client discovers and calls tools once connected, see the MCP client concepts reference.

Already connected and want the workflow?

This page covers the connection. Our guide to building a social media manager on OpenClaw covers skill file versus CLI versus MCP, and what breaks when an agent posts unattended.

FAQ

OpenClaw social media FAQs

01 Can OpenClaw post to social media?

Yes. OpenClaw cannot reach a social account on its own, because it has no platform credentials. Connecting it to Blotato's hosted MCP server at https://mcp.blotato.com/mcp gives it tools to publish and schedule across nine platforms: X, LinkedIn, Facebook, Instagram, TikTok, YouTube, Threads, Bluesky, and Pinterest. OpenClaw authenticates with oauth or header.

02 How do I connect OpenClaw to social media?

03 How do I set up OpenClaw for social media?

Setting up OpenClaw for social media takes one connection. Connect your social accounts in Blotato, then give OpenClaw the hosted MCP endpoint https://mcp.blotato.com/mcp and authenticate with oauth or header. For OpenClaw specifically that means: one cli command, no config file to edit. Once it loads, OpenClaw can publish and schedule to X, LinkedIn, Facebook, Instagram, TikTok, YouTube, Threads, Bluesky, and Pinterest from a plain-language prompt.

04 What is the best way to manage social media with OpenClaw?

Let OpenClaw do the drafting and decision making, and let a publishing layer hold the accounts and the schedule. The thing that makes this work on OpenClaw in particular: OpenClaw is the only client here that is both an MCP server and an MCP client: openclaw mcp serve exposes OpenClaw itself, while the other subcommands manage outbound servers like Blotato. It also has a real CLI registry with doctor and probe diagnostics, so you debug a connection with commands rather than by re-reading a JSON file, and per-server include and exclude filters so an unattended agent can hold the publishing tools without the ones that spend credits.

05 What goes wrong when connecting OpenClaw?

06 Does OpenClaw need to be running for a scheduled post to go out?

No. Scheduling runs on Blotato rather than inside OpenClaw. Once the agent queues a post, it publishes at the scheduled time whether or not OpenClaw, your terminal, or your laptop is on. This is the practical difference between an agent that drafts and a system that runs unattended.

07 What can I ask OpenClaw to do once it is connected?

"Every morning, turn yesterday's notes into a post and publish it." A scheduled OpenClaw run ending in blotato_create_post. This is the unattended case the header auth exists for, since an expired OAuth session on a self-hosted agent stops publishing with nobody watching. "Did anything fail overnight?" blotato_list_posts plus blotato_get_post_status on anything still pending. Worth logging, because an async publish that failed at 3am looks identical to one that never ran. "Show me what tools this server actually exposes." openclaw mcp probe blotato connects and reports them. Note that openclaw mcp tools is a different command: it sets the include and exclude filters, which is how you hand an unattended agent publishing without the tools that spend credits.

08 How much does it cost to connect OpenClaw?

Starter is $29/mo flat for 20 connected accounts, and the price does not scale with posting volume. API and MCP access is not part of the 7-day trial: generating a key activates the paid Starter plan, so plan on subscribing rather than trialing it.

Connecting a different agent?

Same endpoint, same accounts, one setup per client. The AI agents for social media hub covers what all of them share, including every tool your agent can call.