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 35 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 August 2026
Which AI agents can post to social media?
These 18 can, once you connect them to a publishing layer that holds the accounts:
Claude.ai, Claude Cowork, Claude Code, ChatGPT, OpenAI Codex, Google Antigravity, Cursor, Grok Bot, Cline, GitHub Copilot, Replit Agent, Windsurf, Perplexity Computer, OpenClaw, Hermes Agent, OpenCode, Gemini CLI, and NanoClaw.
None of them can reach a social account on its own, because none of them holds platform credentials.
Point one at Blotato's hosted MCP server at https://mcp.blotato.com/mcp and it gets 35 tools
for publishing and scheduling across nine platforms.
Every entry below was checked against that vendor's own MCP documentation rather than against what a
comparison post claims. The setup is the same shape everywhere, point the agent at one URL and
authenticate, and each card links to the exact steps for that client. Claude and ChatGPT authenticate
over OAuth. The rest take your API key as a blotato-api-key header.
Claude.ai
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.
Connects with OAuth
Claude Cowork
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.
Connects with OAuth
Claude Code
The terminal agent. One command adds the server, and it is the setup most Blotato API users are already running.
Connects with OAuth or header
ChatGPT
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.
Connects with OAuth only
OpenAI Codex
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.
Connects with API key header
Google Antigravity
Google’s agent-first development platform. Its MCP config is shared across the IDE, the CLI, and the SDK.
Connects with API key header
Cursor
The editor a lot of builders live in. Paste the JSON config, restart, and publishing is available beside the code that generates the content.
Connects with API key header
Grok Bot
SpaceXAI’s AI teammates, run from a Cursor account, with a persistent cloud computer per member. Connect Blotato once and every Bot you run can publish, on a schedule, with your laptop closed.
Grok Bot launched in early beta on August 11, 2026, and is included with higher-tier SuperGrok and Cursor plans rather than sold on its own. Its connection to a custom MCP server runs from Cursor’s backend, not your machine, so the server must be reachable over the public internet, which a hosted endpoint already is.
Connects with API key header
Cline
Open-source coding agent that runs in VS Code or from its own CLI. It reaches a hosted endpoint over streamable HTTP, so the same config works in the extension and the terminal.
Cline picks its transport from the `type` field, and leaving it out falls back to the legacy SSE transport rather than erroring, which reads as the endpoint being broken. Set "type": "streamableHttp" explicitly.
Connects with API key header
GitHub Copilot
Copilot agent mode in VS Code. It reads MCP servers from mcp.json, so publishing sits in the editor most teams already have open.
Two different products carry this name. Copilot agent mode in VS Code is the one described here, and it accepts both OAuth and a header. Copilot cloud agent on github.com also takes remote MCP servers, but does not support OAuth for them and reads secrets from COPILOT_MCP_-prefixed variables instead, so a config that works in one is not guaranteed in the other.
Connects with OAuth or header
Replit Agent
Replit’s agent, useful when the thing posting is an app you are building in the same place.
Connects with API key header
Windsurf
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.
Connects with API key header
Perplexity Computer
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.
Connects with OAuth or API key
OpenClaw
Self-hosted personal agent with SSE and streamable HTTP transports, headers, and an OAuth login command.
Connects with OAuth or header
Hermes Agent
Nous Research’s open agent. Its MCP config takes a URL plus headers, and it supports OAuth 2.1 with PKCE.
Connects with OAuth or header
OpenCode
Open-source terminal agent, model agnostic. Remote servers take a URL and headers, with automatic OAuth via dynamic client registration.
Connects with OAuth or header
Gemini CLI
Google’s open-source terminal agent. Takes an httpUrl plus headers, so the Blotato endpoint drops straight in.
Connects with API key header
NanoClaw
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.
Connects with Via an stdio bridge
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, though the config shape differs per client and a copied block is the usual reason a setup fails silently. The URL field is url in Cursor, serverUrl in Antigravity and Windsurf, and httpUrl in Gemini CLI. Replit Agent takes no config file at all: you add the server by URL in Integrations. Each client's exact block is on its own page. | API-key header. |
| Grok Bot | Yes, as a custom remote MCP server added from its Plugins surface. The form takes a name, the URL, and optional headers, and the connection runs from Cursor's backend rather than your machine, so the server has to be publicly reachable, which a hosted endpoint is. Early beta: it launched August 11, 2026. | The blotato-api-key header, pasted into the optional headers field on the custom server form. |
| Cline, GitHub Copilot | Yes, both from inside VS Code. Cline picks its transport from the type field, and omitting it silently falls back to legacy SSE rather than erroring, so set it to streamableHttp explicitly. Copilot agent mode reads MCP servers from mcp.json, but the Agent Host does not read .vscode/mcp.json and skips servers that use input variables, so put the config in a workspace .mcp.json or ~/.copilot/mcp-config.json with the key written literally. | Cline takes the API-key header. Copilot takes OAuth or the 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.
| Capability | Coverage through one connection |
|---|---|
| Publishing and scheduling | All nine platforms: X, LinkedIn, Facebook, Instagram, TikTok, YouTube, Threads, Bluesky, and Pinterest. |
| Analytics | Eight platforms: everything except LinkedIn, which returns no metrics yet. |
| Comments | Instagram and Facebook. |
| Direct messages | Instagram and Facebook. |
| Keyword-triggered DM automation | Instagram and Facebook. Reply-only, so it answers comments and DMs rather than starting conversations. |
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.
Is there a social media API for AI agents?
Yes, and you are looking at it. Blotato is a social media API for AI agents: the same hosted endpoint your agent calls over MCP is a REST social media posting API your own backend can call directly. One key covers both, so an agent workflow and a server-side integration run on one bill instead of two stacks. Publishing and scheduling cover nine platforms, and the price is $29/mo flat rather than metered per call or per account.
The practical split: if a model is deciding what to publish, connect over MCP. If your code is deciding, call the REST API. Which layer you should build on covers the tradeoff, and the full machine-readable reference lives at help.blotato.com/api/llm.
All 35 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: the DM automation tools reply to a comment or an incoming message on Instagram and Facebook, so a cold-outreach DM sequence is still not something to plan around.
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
DM automation
blotato_create_automationblotato_list_automationsblotato_update_automationblotato_delete_automationblotato_list_automation_runsblotato_list_automation_logsblotato_get_automation_analytics
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, messaging, and DM automation tools return data for Instagram and Facebook. Analytics tools cover every platform except LinkedIn, which returns no metrics yet. Publishing and scheduling work on all nine platforms.
What this looks like in a real session
You say: "Schedule this week's posts: the product update to LinkedIn and X tomorrow at 9am, and the tutorial clip to TikTok and YouTube on Thursday."
The agent calls blotato_create_post once per platform with the scheduled times, then
confirms with blotato_list_schedules. Your laptop can be closed when they publish,
because scheduling runs on Blotato.
You say: "What performed best last week, and are there any comments I should reply to?"
The agent calls blotato_list_top_posts and blotato_get_post_analytics for
the numbers on every platform except LinkedIn, then blotato_list_comments
on Instagram and Facebook and drafts replies you approve before it calls
blotato_post_comment.
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
AI agents for social media FAQs
01 How do I get an AI agent to post to social media?
02 Can Claude Code post to social media?
03 Which AI coding agents can manage social media accounts?
04 Can ChatGPT post to social media through Blotato?
05 Can I use Blotato with an AI agent that is not on this list?
06 What can an AI agent actually do on social media, and what can it not do?
07 Is there an API for scheduling social media posts from an AI agent?
08 What is the difference between a social media API and an MCP server?
09 Do I need a developer app or API keys for each platform?
10 Does the agent need to be running when a scheduled post goes out?
11 How much does it cost to connect an AI agent?
Blotato Your AI Agent still can't post to social media.
Point Claude, ChatGPT, n8n, or your own agent at Blotato's MCP and that's fixed: 9 platforms behind one key, flat $29/mo.
Connect your agentFlat pricing. Cancel anytime.