AI Agents for Social Media
Blotato is the social media publishing layer for AI agents. It is a hosted MCP server
at https://mcp.blotato.com/mcp that gives any connected agent 28 tools to publish,
schedule, and analyze social media posts across nine platforms: X, LinkedIn, Facebook, Instagram,
TikTok, YouTube, Threads, Bluesky, and Pinterest. Claude Code, Claude.ai, Claude Desktop, Claude
Cowork, ChatGPT, OpenAI Codex, Cursor, Google Antigravity, and Replit Agent all connect to it, over
OAuth or a blotato-api-key header. Plans start at $29/mo.
Your agent can already write the post. It cannot publish one, because it has no social account and no platform credentials. Blotato is the layer that closes that gap: connect it once and the agent you already run publishes and schedules across nine platforms.
https://mcp.blotato.com/mcp Updated July 2026
Which AI agents can post to social media?
15 of them, each checked against that vendor's own MCP documentation rather than against
what a comparison post claims. Blotato is a standard remote MCP server, so the setup is the same
everywhere: point the agent at one URL and authenticate. Claude and ChatGPT use OAuth. The rest take
your API key as a blotato-api-key header.
Claude.ai
OAuth
Claude in the browser. Add Blotato as a custom connector and you can ask for a post from the same chat window you already draft in.
Claude Cowork
OAuth
Claude working across your files and tools without a terminal. The closest thing to handing social media to an assistant rather than running it yourself.
Claude Code
OAuth or header
The terminal agent. One command adds the server, and it is the setup most Blotato API users are already running.
ChatGPT
OAuth only
Where most people already draft posts. Add Blotato as a connector in Developer mode and the draft and the publish happen in the same window.
Custom MCP servers in ChatGPT live behind Developer mode, which is web only and on Pro, Plus, Business, Enterprise, or Education accounts. It connects over OAuth rather than an API-key header, which is how Blotato authenticates Claude too.
OpenAI Codex
API key header
OpenAI’s coding agent. Setup is a form in the app rather than JSON, or an entry in config.toml.
Codex asks for a form rather than JSON: choose the streamable HTTP server type, set the URL, leave the bearer token blank, and add blotato-api-key as a header.
Google Antigravity
API key header
Google’s agent-first development platform. Its MCP config is shared across the IDE, the CLI, and the SDK.
Cursor
API key header
The editor a lot of builders live in. Paste the JSON config, restart, and publishing is available beside the code that generates the content.
Replit Agent
API key header
Replit’s agent, useful when the thing posting is an app you are building in the same place.
Windsurf
API key header
Cascade supports remote MCP servers with custom headers, so the Blotato endpoint fits its config shape.
Windsurf is now part of Devin Desktop under Cognition, so its MCP documentation lives in the Devin docs. Cascade takes the same JSON config as Cursor.
Perplexity Computer
OAuth or API key
Perplexity’s agentic workspace. It takes custom remote MCP connectors with None, API Key, or OAuth 2.0 authentication.
Add Blotato under custom remote connectors, choosing streamable HTTP as the transport. On an organization plan an admin has to enable custom connectors first, and a connector stays private to you until it is shared.
OpenClaw
OAuth or header
Self-hosted personal agent with SSE and streamable HTTP transports, headers, and an OAuth login command.
Hermes Agent
OAuth or header
Nous Research’s open agent. Its MCP config takes a URL plus headers, and it supports OAuth 2.1 with PKCE.
OpenCode
OAuth or header
Open-source terminal agent, model agnostic. Remote servers take a URL and headers, with automatic OAuth via dynamic client registration.
Gemini CLI
API key header
Google’s open-source terminal agent. Takes an httpUrl plus headers, so the Blotato endpoint drops straight in.
NanoClaw
Via an stdio bridge
Registers MCP servers by launching a local command, so it reaches a hosted endpoint through a bridge rather than a URL field.
NanoClaw documents registering stdio MCP servers in a group container config rather than a remote URL, so point it at Blotato with a standard stdio-to-HTTP bridge such as mcp-remote. One extra step, same endpoint.
Which agents can publish, and how each one authenticates
| Agent | Can it publish through Blotato? | How it authenticates |
|---|---|---|
| Claude.ai, Claude Desktop, Claude Cowork | Yes, by adding Blotato as a custom connector. | OAuth. Header auth is not usable here: Anthropic restricts custom-connector headers to a reviewed allowlist that does not include blotato-api-key. |
| Claude Code | Yes. One claude mcp add command, then authenticate from the /mcp menu. | OAuth, or the API-key header. |
| ChatGPT | Yes, but only through Developer mode, which is web only and on Pro, Plus, Business, Enterprise, or Education accounts. Not available on the free tier or in the mobile apps. | OAuth. Blotato serves the protected-resource metadata, dynamic client registration, and PKCE that Developer mode expects. |
| OpenAI Codex | Yes. A different OpenAI product from ChatGPT, set up with a form rather than JSON. | API-key header. Choose the streamable HTTP server type and leave the bearer token blank. |
| Cursor, Google Antigravity, Replit Agent, Windsurf, Gemini CLI | Yes. Each takes a remote server URL plus custom headers, so the same JSON config works across all five. | API-key header. |
| Perplexity Computer | Yes, under custom remote connectors. On an organization plan an admin has to enable custom connectors first. | API key or OAuth, with streamable HTTP as the transport. |
| OpenClaw, Hermes Agent, OpenCode | Yes. All three document remote MCP servers with headers and an OAuth path, though header forwarding and OAuth have known open bugs in some configurations. | OAuth or the API-key header. |
| NanoClaw | Not directly. It registers MCP servers as a local command rather than a URL, so it reaches a hosted endpoint only through a bridge. | Point it at Blotato with a standard stdio-to-HTTP bridge such as mcp-remote. |
The list is not a limit. Blotato speaks standard MCP over streamable HTTP, so any client that accepts a server URL plus a header works, including ones that shipped after this page did. The copy-pasteable config for each client sits on the social media MCP server page.
What can your agent actually do once it is connected?
Capability is uneven across networks, and most pages gloss over that. Here is the honest version, so you can rule Blotato out quickly if it does not fit what you are building.
- Publishing and scheduling: all nine platforms.
- Analytics: X, Instagram, Facebook, Threads, and Bluesky.
- Comments: Instagram and Facebook.
- Direct messages: Instagram and Facebook.
Scheduling runs on Blotato rather than in the agent, which is the part that matters for anything unattended: once the agent queues a post, it goes out on time whether or not the agent is still running.
All 28 tools your agent can call
This is the surface area your agent gets. It matters when you are deciding what to hand off, because an agent can only automate what it has a tool for: there is no tool here that runs a keyword-triggered DM sequence, so that workflow is not something to plan around yet.
Accounts
blotato_get_userblotato_list_accountsblotato_list_pinterest_boards
Publishing
blotato_create_postblotato_get_post_statusblotato_list_posts
Content calendar
blotato_list_schedulesblotato_get_scheduleblotato_update_scheduleblotato_delete_schedule
Analytics
blotato_list_top_postsblotato_get_post_analytics
Comments
blotato_list_commentsblotato_get_commentblotato_post_comment
Messages and DMs
blotato_list_conversationsblotato_get_conversationblotato_list_messagesblotato_get_messageblotato_send_message
Videos and images
blotato_list_visual_templatesblotato_create_visualblotato_get_visual_status
Content extraction
blotato_create_sourceblotato_get_source_status
Media and credits
blotato_create_presigned_upload_urlblotato_get_creditsblotato_buy_credits
Comments and messaging tools return data for Instagram and Facebook. Analytics tools cover X, Instagram, Facebook, Threads, and Bluesky. Publishing and scheduling work on all nine platforms.
Which social platforms can your agent publish to?
Nine, on one connection. Each page below covers that network's setup, the exact prompt, and what Blotato can and cannot do there.
Publish feed posts, carousels, Reels from an agent prompt.
Publish text posts, image posts, documents from an agent prompt.
X
Publish posts (tweets), threads, image posts from an agent prompt.
TikTok
Publish videos, photo slideshows from an agent prompt.
YouTube
Publish videos, Shorts from an agent prompt.
Publish Page posts, photos, Reels from an agent prompt.
Threads
Publish posts, threads, image posts from an agent prompt.
Bluesky
Publish posts, threads, image posts from an agent prompt.
Publish Pins, video Pins from an agent prompt.
Why not wire the platform APIs up yourself?
You can, and if you only ever post to one network it is a reasonable call. The trade shows up at the second platform. Every network has its own auth model, its own upload flow, and its own review process, and they change on their own schedules rather than yours.
The alternative to one key is five vendors, five approval processes, and five bills that each move with volume. Blotato is one hosted endpoint across nine networks on the platforms' official APIs, with no browser automation to babysit and a flat price that does not change when you post more. If you would rather own that layer, we wrote up the honest tradeoff between open-source and managed posting APIs.
Still deciding which agent to run? Our comparison of 12 AI agents for social media tests each one on whether it can publish at all. This page assumes you have already picked one and covers how it connects. The protocol side lives on the social media MCP server page.
What does this look like in practice?
The gap between "my agent can call a publish tool" and "my agent runs my social media" is mostly workflow. This walkthrough is Sabrina Ramonov doing the second thing from a single Claude Code session.
Who is already running social media from an agent?
Three customers on what changed once the publishing step stopped being manual.
I'm building an AI startup focussing on educational content in social media (eventually) and experimenting with a lot of things right now. Blotato as a platform is incredibly easy to use, has a great API for our needs and great pricing. The best part is the openness of the platform: all other platforms we tested continuously limit you and try to pry more money out of you for little value. Blotato is the opposite: open and offering incredible power.
Thomas BiskupCEO, 3B Ventures UG
What I like about Blotato is that it's a tool that removes creative bottlenecks, particularly its API features. Blotato turns you into a content machine, like, content creation on a steroids. I'm very happy that I came across this tool on YouTube. Now, I don't have to worry about publishing anymore. If you're looking for an affordable API solution or mass content production and publishing, Blotato is worth a try.
Gee MiguelOwner, Inksthetik, Philippines
Once I connected Blotato into my n8n workflow, everything changed. I now have an automated pipeline that generates, formats, and publishes content directly to LinkedIn. It takes me from idea to draft to optimized post to live, without friction. Since setting this up, I've gone from zero consistency to having a repeatable content engine.
DanielFounder, TheBag.KE, Nairobi