X (Twitter) MCP server

X MCP server for social media publishing

Claude cannot reach X by itself. Connect Blotato's MCP server once and it can publish posts (tweets), threads, image posts, video to X from a plain prompt. One hosted endpoint, no developer app, no copy-paste.

This one publishes. Search "X (Twitter) MCP server" and you get two different kinds of tool: scrapers that read public X data, and publishers that put a post live on your own account. Blotato is the second kind, on X's official API, not browser automation.

MCP endpoint https://mcp.blotato.com/mcp

Connect X to Claude See pricing

Updated August 2026

How do I post to X with an AI agent?

Connect your X account. Sign in to Blotato and connect X through the normal login flow. Blotato holds the tokens and refreshes them, so this is the last time you think about auth.
Add the MCP server to Claude. In Claude, open Settings, then Connectors, then add a custom connector pointing at https://mcp.blotato.com/mcp. Claude Code and Cowork take the same URL.
Ask Claude to post. Write it the way you would say it out loud: "Break this article into a 6-tweet thread and publish it to X." Claude calls the publish tool and Blotato puts the post live.

What can your agent do on X through Blotato?

Publish to X

Post posts (tweets), threads, image posts, video directly, with the fields each format requires.

Schedule for later

Queue a X post for a future time and let Blotato publish it on the clock.

Upload or generate media

Hand Claude a local file or a URL, or have it generate the image or video first.

List connected accounts

See which X accounts are connected and pick the right one to post from.

Check post status

Confirm a post actually went live, and read back the error if a platform rejected it.

Read post analytics

Pull performance metrics back off your X posts so an agent can learn from what worked.

On X, Blotato covers publishing and scheduling and analytics. It does not yet cover comments and direct messages on this platform, so if that is what you need, this is the wrong tool and it is better you know now. X moved most engagement and messaging endpoints to paid tiers above the self-serve plans in 2026, so covering them would mean passing that cost through.

Tools your agent can call on X (Twitter)

These are the exact MCP tool names exposed on this platform, so you can reference them directly in a prompt or check them against your client's tool list.

blotato_get_user
blotato_list_accounts
blotato_create_post
blotato_get_post_status
blotato_list_posts
blotato_create_presigned_upload_url
blotato_get_schedule
blotato_list_schedules
blotato_update_schedule
blotato_delete_schedule
blotato_list_visual_templates
blotato_create_visual
blotato_get_visual_status
blotato_create_source
blotato_get_source_status
blotato_get_credits
blotato_buy_credits
blotato_get_post_analytics
blotato_list_top_posts

Which AI agents can post to X?

Eight, and they all reach X through the same endpoint. Claude authenticates over OAuth. The rest take your API key as a blotato-api-key header. Nothing here runs a local server.

Agent	Connects with
Claude Code	OAuth
Claude Desktop and Cowork	OAuth
Claude.ai on the web	OAuth
Cursor	API key header
OpenAI Codex	API key header
Antigravity and Replit Agent	API key header

The full setup for each client, including the copy-pasteable config, is on the social media MCP server page. Blotato does not document a direct ChatGPT connection, so use Codex if you are in the OpenAI ecosystem.

What does it look like in practice?

Screenshots from the full X walkthrough, showing the connection and a real published post.

The Blotato MCP server connected in Claude Code — Claude Code takes the same hosted endpoint as Claude Desktop.

Claude Code calling the Blotato publish tool to post to X — The agent calls the publish tool and reports back the post status.

The published post live on X — Live on X, with no developer account or API keys involved.

Why not just build it against the Twitter API?

X (still widely called Twitter) moved most write access behind paid API tiers, and the pricing has shifted more than once, so a hand-built integration is exposed to both the bill and the next change to it.

You can absolutely build it yourself, and if X is the only network you will ever post to, that 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. Blotato is one endpoint across nine of them, at a flat price that does not move when you post more.

If you would rather own that layer yourself, we wrote up the honest tradeoff between open-source and managed posting APIs, and our roundup of social media MCP servers covers the alternatives, including the ones that only draft rather than publish.

Who is already publishing to X this way?

These are Blotato customers describing their own agent and API setups, in their own words.

Between those two socials, I'm posting content to 12 platforms, which means 1 video needs to end up in 6 places when all is said and done. Any social media management tool I used previously that posts it to multiple platforms was always extremely costly, convoluted, and inconsistent. Too much fluff. Blotato keeps it as simple as possible, only showing you the stuff you need to see. Connecting socials was so easy and I was surprised when connecting multiple accounts to 1 social. Didn't skip a beat.

Nick
CEO, Naaackers & NackHabitat, Detroit

I spent a few days in December testing out 7-8 providers of automation interfaces for posting to social media platforms. In the end I chose VistaSocial - 5 times more expensive than the competitors. Now I am switching from Vista Social to Blotato, where I am getting the same functionality at a fraction of the price. I am in the automation business, so the UI look&feel is not very relevant, I am mostly focused on the hooks that you can access from automated flows.

Mihai M.
Founder, IQBiz.ro, Romania

Twitter MCP server or X MCP server: what is the difference?

There is no difference. Twitter became X in 2023, and the network, the API, and the MCP tooling are the same thing under both names. Most people still search for a Twitter MCP server, and most tools are still listed under both, so if you landed here looking for Twitter, you are in the right place.

What does differ is what each server actually does. Most of the Twitter MCP servers you will find are open-source wrappers around the X API that you clone, host, and supply your own developer credentials to. X also ships its own official MCP server, which connects an AI tool to the X API under your account permissions. Both are real options, and both leave you managing X API access and its per-call pricing yourself.

Blotato is the hosted alternative: it holds the X connection, so you never create a developer account, load API credits, or maintain a server. The tradeoff is honest, though. If you want to read timelines, search tweets, or pull follower data, an open-source Twitter MCP server or the official X one is the better fit. Blotato is built to publish, so a scheduled thread, an image tweet, or a video post is what it does well.

FAQ

X (Twitter) MCP server FAQs

01 Can Claude post to X?

Yes. Claude cannot reach X on its own, but connecting an MCP server gives it the tools to publish. Add Blotato's server at https://mcp.blotato.com/mcp, connect your X account once, then ask Claude to post in plain language.

02 What is an X (Twitter) MCP server?

It is a Model Context Protocol server that exposes X actions as tools an AI assistant can call. Instead of you describing the X API to Claude, the server hands Claude a publish action it can invoke directly.

03 Do I need X API access or a developer app?

No. Blotato holds the platform integration and the OAuth tokens, so you connect your account through a normal login flow instead of registering a developer app. X (still widely called Twitter) moved most write access behind paid API tiers, and the pricing has shifted more than once, so a hand-built integration is exposed to both the bill and the next change to it.

04 What kind of X account do I need?

X and Twitter are the same platform. X rebranded from Twitter in 2023, and the API, the MCP tooling, and this page all refer to the same network, so a Twitter MCP server and an X MCP server are the same thing. A normal X account works; you do not need a developer account to publish through Blotato.

05 Can Claude schedule X posts for later?

Yes. Ask for a time and Blotato queues the post and publishes it then. You do not need Claude open at the scheduled moment.

06 What else can Blotato's MCP server do on X?

07 Does this X (Twitter) MCP server publish, or only read X data?

It publishes. This matters because "X (Twitter) MCP server" returns two different kinds of tool: scrapers that read public X data for analysis, and publishers that put a post live on your own account. Blotato is the second kind, built on X's official API rather than scraping, so your agent finishes the job instead of handing you a draft.

08 Is there a Twitter MCP server, or only an X one?

They are the same thing. X was called Twitter until 2023, and the API and MCP tooling still cover one network under both names. Blotato's server publishes to your X account whether you searched for a Twitter MCP server or an X one.

09 Can Claude post a tweet or a thread for me?

Yes. Ask for a single post or a full thread in plain language and Blotato publishes it to your X account, with images or video attached if you include them. You can also schedule it for later instead of posting now.

10 Do I need an X developer account or API credits?

Not with Blotato, because Blotato holds the X integration and the credentials. You do need them if you run an open-source Twitter MCP server or X's own official MCP server, since both call the X API under your account and its pricing.

11 Which AI agents can post to X?

Claude Code, Claude Desktop, Claude Cowork, Claude.ai on the web, Cursor, OpenAI Codex, Google Antigravity, and Replit Agent can all publish to X through Blotato's MCP server at https://mcp.blotato.com/mcp. Claude connects over OAuth; Cursor, Codex, Antigravity, and Replit Agent connect with a blotato-api-key header. Blotato does not document a direct ChatGPT connection, so use Codex if you are in the OpenAI ecosystem. The same endpoint also covers the other eight platforms.

12 Which X MCP server should I use?

Decide by whether you need to publish or to read. Search "X (Twitter) MCP server" and most results are scrapers that read public X data, plus open-source servers you host yourself and register your own X developer app for. Blotato is the hosted publisher: your agent puts a post live on your own X account through the official API, with 19 tools behind one endpoint at $29/mo flat. If you only need to read public X data, a scraper is the cheaper answer and you should use one.

13 How much does it cost?

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

Does the same connection cover other platforms?

X is one target on the same endpoint. Once Claude is connected, it can publish to the rest without any further setup.