X (Twitter) MCP Server
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.
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.
First post in minutes.
The server URL is https://mcp.outstand.so/mcp. Paste it into your client and connect X (Twitter).
- 01Create an X developer account and an app in the X developer portal, then copy its OAuth 2.0 client ID and secret. X is the one network where you bring your own keys.
- 02Add those credentials to Outstand with create_social_network, or paste them in the dashboard. Your agent can do this step too.
- 03Connect your X account through the OAuth link, which now runs against your own X app.
- 04Add https://mcp.outstand.so/mcp to your MCP client and ask it to post.
Claude Code
claude mcp add -t http \ -H "Authorization: Bearer ost_your_key" \ outstand https://mcp.outstand.so/mcp
Claude Desktop
// claude_desktop_config.json
{
"mcpServers": {
"outstand": {
"command": "npx",
"args": [
"mcp-remote",
"https://mcp.outstand.so/mcp",
"--header",
"Authorization: Bearer ost_your_key"
]
}
}
}Cursor
// .cursor/mcp.json
{
"mcpServers": {
"outstand": {
"command": "npx",
"args": [
"mcp-remote",
"https://mcp.outstand.so/mcp",
"--header",
"Authorization: Bearer ost_your_key"
]
}
}
}Any client with a custom connector (ChatGPT, Claude web, Cursor)
# 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.
What your agent can do.
The tools that apply to X (Twitter), out of 27 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.upload_mediaStart 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.
Does X have an official MCP server?
No. X does not publish an MCP server, so everything available today is third-party.
Unlike Instagram or LinkedIn, the X landscape is not really split between scrapers and API clients: most of the open-source options on GitHub do wrap the official X API. The catch is that all of them hand you the hard part. You register the developer app, you pick an API tier, you store and refresh the tokens, and you absorb whatever X does to its pricing next. Many of these projects were written against an older tier structure and quietly stopped working when it changed.
A hosted server like Outstand does not remove the need for your own X credentials, and we are upfront that it cannot. What it removes is everything around them: token refresh, retries, media upload, scheduling, and the same tool surface across every other network you post to.
Choosing a X (Twitter) MCP.
Three realistic ways to give an agent access to X, and what each one actually costs you.
| Approach | Setup time | Auth | Reliability | Compliance |
|---|---|---|---|---|
| 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 |
Authentication: X is the one platform where you bring your own keys
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.
X (Twitter) specifics.
- ✓Media rules follow X: up to 4 images, or one GIF, or one video, and the types cannot be mixed in a single post.
- ✓Threads are not chained yet. Each post publishes as a single post on X, so an agent that wants a thread should publish and then reply.
- ✓Retweets and quote tweets both work through repost_post. Pass a quote to add commentary, or leave it out for a plain retweet.
- ✓Post analytics return likes, replies, retweets, and impressions. Time-ranged account engagement needs X Analytics on a Premium tier, so it comes back empty rather than guessed.
What this MCP doesn't do.
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.
Frequently asked questions.
Does X have an official MCP server?
No. X has not shipped an MCP server, so every option is third-party. Most of the open-source ones do wrap the official X API, but they leave you to register the developer app, choose an API tier, and handle token storage and refresh yourself.
Why do I need my own X API keys?
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.
What X API tier do I need?
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.
Can Claude post threads on X?
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.
Can it schedule posts on X?
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.
Does it retweet and quote tweet?
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.
What does it cost?
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.
Connect X, publish your first post in minutes
Add your X app credentials once, approve the OAuth link, and paste the server URL into your client.
https://mcp.outstand.so/mcp