An X MCP server, still widely searched as a Twitter MCP server, gives an AI agent tools for X so a model can publish to your account instead of only drafting posts. Point Claude, Cursor, or any MCP client at Outstand's server and the agent can post, attach images or video, reply, retweet, quote, and read engagement metrics. Everything runs through the official X API using your own X app credentials.
Calling it from your own code instead of an agent? The same account works through our X API.
https://mcp.outstand.so/mcpclaude mcp add -t http \ -H "Authorization: Bearer ost_your_key" \ outstand https://mcp.outstand.so/mcp
Works with Claude Desktop, Claude Code, Cursor, Windsurf, ChatGPT, and any MCP client.
The server URL is https://mcp.outstand.so/mcp. Paste it into your client and connect X (Twitter).
claude mcp add -t http \ -H "Authorization: Bearer ost_your_key" \ outstand https://mcp.outstand.so/mcp
// claude_desktop_config.json
{
"mcpServers": {
"outstand": {
"command": "npx",
"args": [
"mcp-remote",
"https://mcp.outstand.so/mcp",
"--header",
"Authorization: Bearer ost_your_key"
]
}
}
}// .cursor/mcp.json
{
"mcpServers": {
"outstand": {
"command": "npx",
"args": [
"mcp-remote",
"https://mcp.outstand.so/mcp",
"--header",
"Authorization: Bearer ost_your_key"
]
}
}
}# Add a custom connector in your client's settings and paste # this URL, then sign in once in the browser. No API key to copy. https://mcp.outstand.so/mcp
Works with Claude Desktop, Claude Code, Cursor, Windsurf, ChatGPT, and any other MCP client. Full client setup guide.
The tools that apply to X (Twitter), out of 28 on the server.
create_postPublish or schedule a post on X, with up to 4 images, one GIF, or one video.repost_postRetweet a published post, or quote tweet it with your own commentary.create_replyReply to a comment on a post published through Outstand.get_repliesRead replies on a post published through Outstand.get_post_analyticsFetch likes, replies, retweets, and impressions for a published post.list_postsList posts, filterable by account, status, and date range.get_postFetch a single post and its per-platform publish status.delete_postDelete a post record in Outstand, cancelling it if it is still scheduled.delete_remote_postDelete the published post on X itself.request_media_upload_urlStart a media upload and get a signed URL for an image or video.confirm_media_uploadConfirm an upload once the bytes are transferred and get the public URL to attach.create_social_networkStore your own X app credentials (BYOK) so Outstand can act on your X API tier.update_social_networkRotate or update your stored X app credentials.get_auth_urlGenerate an OAuth URL to connect a new X account against your app.list_social_accountsList connected social accounts, so the agent can find your X account.get_account_metricsFetch followers, following, and post counts for a connected X account.get_account_usageRead current billing-period post usage.Yes - since 30 June 2026. X runs a hosted MCP server at https://api.x.com/mcp, maintained by the X Developer Platform, and you connect through its open-source xurl bridge, which handles the OAuth and auto-refreshes the token. There is also a self-hosted server, xdevplatform/xmcp, that you clone and run yourself.
That moves the question from whether there is an official one to what it does. The hosted server's published tool list is read-heavy: fetch posts and their likers, reposters and quoters, full-archive post search, user lookup and timelines, bookmarks, news and trends, plus Articles, which it can draft and publish. Publishing an ordinary post with media lives in the self-hosted xmcp repo instead (createPosts, and the three-step initializeMediaUpload / appendMediaUpload / finalizeMediaUpload), which means running the process yourself; its README notes tokens are "kept in memory only for the lifetime of the server process", so the connection does not survive a restart. Neither one schedules.
Both official routes need exactly what we need: your own X developer app, on whatever API tier it sits on.
What Outstand adds on top of your own X credentials is the part neither official route covers: tokens stored and refreshed so a connection survives a restart, media upload, scheduling, and the same 28-tool surface across the other 11 networks you post to. If all you need is read access to X from an agent, the official hosted server is the shorter path, and we will say so.
X is the one platform here where the bill moves with usage, so it is worth knowing what posting to X costs per request.
Five realistic ways to give an agent access to X, and what each one actually costs you.
| Approach | Setup time | Auth | Reliability | Compliance |
|---|---|---|---|---|
| Official X MCP - hosted (api.x.com/mcp) | Minutes, plus your own X developer app | Your own X app via X's xurl OAuth bridge; token auto-refreshed | Maintained by X. Read-heavy scope: no ordinary post creation, no media upload, no scheduling | Official X API by definition |
| Official X MCP - self-hosted (xdevplatform/xmcp) | Clone and run it yourself, plus your own X developer app | Your own X app; tokens held in memory only for the process lifetime | Maintained by X, but it stops when the process stops, and it does not schedule | Official X API |
| Self-hosted open-source | An hour or two, plus X developer app setup | Your own X app keys, stored and refreshed by you | Breaks when X changes tiers or your token expires | Official X API, if the project is still maintained |
| Directory-listed community server | Minutes to hours, depending on the project | Your own X app keys | Depends on the maintainer. Many predate the current API tiers | Usually the official API. Check before trusting it |
| Hosted API-based (Outstand) | Minutes once you have X app keys | Your own X app keys (BYOK), stored encrypted and refreshed for you | Maintained against the official API, token refresh handled | Official X API. No scraping, no session cookies |
X is the single network where Outstand requires your own API credentials. Every other platform we support ships with Managed Keys included, and this exception is deliberate rather than a gap.
The reason is X's API pricing. If we bundled X access behind our own app, X's per-tier costs would land inside a flat $19/month plan, and the only way to survive that would be to price for the worst case or cap you in ways you could not predict. With your own keys, your X usage sits on your own tier: you see exactly what it costs, you get that tier's rate limits rather than a share of somebody else's, and your cost of goods stays forecastable as you scale.
What you need is an X developer account and an app with OAuth 2.0 credentials. Store the client ID and secret with create_social_network, connect your account through the OAuth link, and everything after that works exactly like the other networks. The credentials stay yours and stay portable, and the X setup guide in the docs walks through the developer portal step by step.
This is a publishing server, not a listening one. It does not scrape tweets, search the firehose, pull follower lists, automate DMs, or touch X Ads. Analytics cover posts you published through Outstand, not other people's content across X. If you need monitoring or lead scraping, this is the wrong tool.
Yes, since 30 June 2026. X runs a hosted MCP server at https://api.x.com/mcp, connected through its open-source xurl OAuth bridge, and it publishes a self-hosted one as xdevplatform/xmcp. The hosted server is read-heavy: posts and their likers, reposters and quoters, full-archive search, user lookup, bookmarks, news and trends, plus drafting and publishing Articles. Creating an ordinary post with media lives in the self-hosted repo instead, and neither one schedules.
Yes, though it does not have to be one you run. An MCP server is a process that exposes tools to a model over a defined protocol, and it can be something you start on your own machine or something somebody else hosts for you. Outstand's is hosted: https://mcp.outstand.so/mcp is an HTTP endpoint you point your client at, so there is nothing to install and no process to keep alive.
With Outstand you do not have to run one. Adding it is a single command - claude mcp add -t http outstand https://mcp.outstand.so/mcp - and the endpoint stays up whether your machine does or not. The alternative is X's self-hosted xdevplatform/xmcp, which you clone, configure with your own X app, and keep running as a process; its tokens are held in memory only for the lifetime of that process, so the connection ends when the process does.
Because X charges for API access in a way that cannot be bundled into a flat plan without either overpricing everyone or capping you unpredictably. Bringing your own keys means your X usage runs on your own tier: predictable cost, that tier's rate limits, and credentials that stay yours. X is the only network where Outstand requires this - everywhere else, Managed Keys are included.
You need an X developer app with OAuth 2.0 credentials. Historically the free tier was enough for posting, and our X setup guide documents the tiers and their rate limits. X has been changing its access model for new developers, so check the current terms in the X developer portal before you commit to a volume.
There is a free tier, and historically it has been enough to post from. X has been reworking what new developers get, so read the current limits in the X developer portal rather than an older write-up, and our X API pricing breakdown walks through how the paid tiers compare. Either way that bill is X's, not ours: it sits on your own developer app and is paid directly to X, and the Outstand MCP server is included in your plan.
Not as a single chained call yet. Each post is published as one post on X today, so an agent that wants a thread should publish the first post and then add replies. Chained multi-post threads do work on Threads, where the API supports them natively.
Yes. create_post takes a scheduled time and an agent can queue a post up to 30 days ahead. Scheduling runs inside Outstand rather than on X, and a scheduled post can be cancelled with delete_post before it goes out.
Yes, both through repost_post. Passing a quote creates a quote tweet with your commentary on top; leaving it out creates a plain retweet. It can also reply to comments on posts you published through Outstand.
Outstand is $19/month, 3,000 posts included and the MCP server is included at no extra cost. Whatever X charges for your own API tier is separate and paid directly to X, which is exactly what makes it predictable.
Every claim on this page is restated, dated, and citable on the facts page.
Add your X app credentials once, approve the OAuth link, and paste the server URL into your client.
https://mcp.outstand.so/mcp