Claude + X (Twitter): What the Integration Can (and Can't) Do in 2026
Yes — X (Twitter) now has an official MCP server that Claude can use. On June 30, 2026, X shipped a hosted remote MCP server at https://api.x.com/mcp, exposing 200+ X API endpoints: full-archive search, trends, post interactions, bookmark management, and drafting and publishing long-form X Articles. It’s real and connectable — not a marketing page. But there are two catches. First, it’s not in Claude’s connectors directory — you add it as a custom connector, and it requires your own X developer app enrolled in pay-per-use billing. Second, like every Claude MCP setup, it only works inside a conversation you start — no triggers, no scheduling, nothing runs while you’re away.
Here’s exactly what the integration does, what it costs per call, how to set it up, and what to use if you want X work that runs on its own.
What the official X MCP server does
X’s hosted MCP server (Streamable HTTP) connects Claude to the X API with your account’s permissions. Per X’s docs, that includes:
- Search and research — full-archive post, user, and news search; trends by location; post interactions (who liked, reposted, quoted).
- Bookmarks — read and organize bookmarks and bookmark folders.
- X Articles — draft and publish long-form Articles from a chat, the clearest confirmed write path in the docs.
- 200+ endpoints total — the surface tracks the underlying X API, which includes post creation; pay-per-use pricing lists a per-post rate, so posting is priced in, but check what your enrolled app exposes before building a workflow around plain tweets.
X’s docs name Claude Desktop as a supported client (alongside Cursor and VS Code), and since it’s a hosted remote server it can also be added on claude.ai as a custom connector.
The real cost: pay-per-use API pricing
The MCP server is free to connect. Every call it makes is not. X killed the Free, Basic, and Pro API tiers in February 2026 and moved to pay-per-use credits:
- $0.015 per post created — but $0.20 per post if it contains a URL, a 13x surcharge that stings for exactly the “share my new blog post” workflow most people want.
- $0.005 per post read (capped around 2M reads/month), $0.010 per user read, $0.001 per read of your own data.
- Credits are purchased upfront against your developer app; without a pay-per-use enrollment and a Production environment, the MCP returns
client-not-enrollederrors.
Pennies per action sounds cheap, and for occasional posting it is. But a daily brand-monitoring habit reads thousands of posts, and a cross-posting workflow that always includes a link pays the $0.20 rate every time. Budget before you build.
How to set it up
- Create an X developer account and app, enroll it in pay-per-use billing, and set the app to the Production environment.
- On claude.ai: Settings → Connectors → Add custom connector, with
https://api.x.com/mcp(remote custom connectors require a paid Claude plan). On Claude Desktop, X’s docs route auth through thexurl mcpbridge, which handles OAuth 2.0 with auto-refresh. - Authorize with your X account (user-context OAuth for writes; an app-only bearer token gets you read-only).
- In a chat, ask Claude to search posts, pull trends, or draft an Article.
One policy note: X requires automated accounts to carry the “Automated” label linked to a human-run account, and it bans automated likes, reposts, and follow/unfollow. Enforcement is real — X purged around 1.7M AI bot accounts in 2026. Post through the API honestly and you’re fine.
The limits that actually matter
- No triggers, no monitoring. The MCP only works inside a conversation you start. There’s no “when someone mentions my company, alert me” or “post this at 9am Tuesday.” Nothing fires on an event.
- Developer-account friction. Your own app, a credit card on file, pay-per-use enrollment — this is a builder’s setup, not a one-click connector.
- Costs compound quietly. $0.005 a read is invisible until a research session burns through a few thousand posts; a link in every post is $0.20 a pop.
- Laptop-bound for anything scheduled. The closest thing to autonomy is Claude Cowork’s scheduled tasks, which run on a fixed clock, not on inbox events.
So Claude is great for “research this topic on X and draft an Article right now” — and not built for “watch my mentions and post on a schedule.”
If you want X work that runs on its own: Carly
The moment you want something to happen on X without you in the chat — a mentions digest every morning, a post that goes out at the scheduled time after you approve it, a trend alert when a competitor spikes — you’ve crossed past what an MCP session can do.
That’s where Carly fits. Carly is an AI executive assistant built to act on triggers. X connects to Carly via your own API key — paste it on carlyassistant.com/integrations (using the same pay-per-use developer app) and it works like any native connection:
- Every morning at 8, a digest of mentions of your handle and brand keywords, summarized with what needs a reply — at $0.005 a read, a focused daily pull costs cents.
- Draft-and-approve posting: Carly drafts the post from your blog or product update, emails it to you for approval, then publishes at the scheduled time ($0.015 per post — Carly can keep links out of the post body to dodge the $0.20 link rate).
- Weekly competitor watch: full-archive search on rival brand terms, digested with sentiment into one email.
- No-code setup. Describe the workflow in plain English; Carly interviews you and builds it.
- Actually sends — drafts and sends email across Gmail and Outlook, updates records, manages tasks.
- Connects to anything — 200+ native integrations, plus any other tool via your own API key.
AI agents start at $35/month, and steps in a workflow that don’t use AI run free and unlimited.
Claude vs Carly
| Claude (official X MCP) | Carly | |
|---|---|---|
| Search posts, users, trends | Yes | Yes, via your X API key |
| Publish X Articles | Yes | Yes |
| Acts on triggers / schedules | No | Yes |
| Monitors mentions on its own | No | Yes |
| Works while laptop is closed | Yes (hosted), but only mid-chat | Yes (cloud, 24/7) |
| Sends email as part of the flow | No (Gmail draft-only) | Yes (Gmail + Outlook) |
| Setup | X developer app + pay-per-use + custom connector | Paste your API key, describe the workflow |
| Pricing | Pro $20 / Max $100–$200 + per-call X fees | AI agents from $35/mo + per-call X fees |
Claude with the X MCP is a powerful X research-and-writing console inside a chat. Carly is a teammate that watches X and posts on your schedule.
Frequently Asked Questions
Does Claude work with X (Twitter)?
Yes. X ships an official hosted MCP server at api.x.com/mcp (live June 30, 2026) that Claude can use as a custom connector — full-archive search, trends, bookmarks, and publishing X Articles. It’s not in Claude’s one-click connectors directory, and it requires your own X developer app enrolled in pay-per-use billing.
Is the X MCP server free?
Connecting is free; the calls aren’t. X’s pay-per-use pricing charges $0.015 per post created ($0.20 if the post contains a URL) and $0.005 per post read. The old Free, Basic, and Pro tiers were discontinued in February 2026.
Can Claude post tweets automatically?
Not on its own. The MCP only runs inside a conversation you start — there’s no scheduling or event trigger, so Claude can’t post at 9am or reply when someone mentions you. For scheduled and trigger-based posting via the X API, use an agent platform like Carly.
How do I connect Claude to X?
Create an X developer app, enroll it in pay-per-use with a Production environment, then add https://api.x.com/mcp as a custom connector on claude.ai (Settings → Connectors; paid plan required) or connect via the xurl mcp bridge on Claude Desktop. Without pay-per-use enrollment you’ll hit client-not-enrolled errors.
More: Claude + LinkedIn · Claude + Typefully · Claude + Facebook · Claude connectors · Can Claude send emails · Claude vs Carly
Ready to automate your busywork?
Carly schedules, researches, and briefs you—so you can focus on what matters.
See what people say
"Before Carly, I relied on a Calendly link, but the whole process felt impersonal and not very professional. Carly changed that by handling all the back-and-forth, so I'm no longer stuck in endless email threads trying to line up schedules.
Now Carly reaches out to candidates, shares my real-time availability, lets them pick a slot, then sends a Zoom link and drops it straight into my calendar. She sends reminders to both of us before each call, which has significantly reduced no-shows and last-minute confusion.
On top of scheduling, Carly acts like a full executive assistant, sending me my schedule the night before so I can prepare for each call. It reminds me of the old x.ai assistant, but Carly is noticeably smarter, faster, and better suited to my healthcare recruitment business."
