Twitter X Automation vs X MCP
A side-by-side look at the Twitter X Automation and X MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Twitter X Automation for social media work as a local process; choose X MCP for social media as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Twitter X Automation when
- You need dedicated capabilities in the Social Media domain.
- You prefer a local stdio subprocess transport.
Choose X MCP when
- You need dedicated capabilities in the Social Media domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
TWITTER_MODE, RETTIWT_API_KEY, TWITTER_BEARER_TOKEN, TWITTER_API_KEY, TWITTER_API_SECRET, TWITTER_ACCESS_TOKEN, TWITTER_ACCESS_SECRET, TWITTER_REQUEST_TIMEOUT_MS. - You want tools like
get_tweet, get_tweet_replies, get_user_profile.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Social Media | Social Media |
| Quality signal | 51/100 · Good | 56/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | TWITTER_MODERETTIWT_API_KEYTWITTER_BEARER_TOKENTWITTER_API_KEYTWITTER_API_SECRETTWITTER_ACCESS_TOKENTWITTER_ACCESS_SECRETTWITTER_REQUEST_TIMEOUT_MS |
| Verified owner | Community listing | Community listing |
| GitHub stars | 604 | 1 |
| Directory activity | 3 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | 5 |
| Full listing | View Twitter X Automation | View X MCP |
Tools & capabilities
Twitter X Automation tools
No tool names declared yet. Check the project README from the listing page.
X MCP tools 5
get_tweetOne post. Accepts a numeric ID or an `x.com` or `twitter.com` status URL.get_tweet_repliesReplies and available page metadata.get_user_profileOne public profile. A leading `@` is accepted.search_tweetsMatching posts and available page metadata. Search operators depend on the provider.get_server_infoVersion, active provider, tools, limits, and capabilities.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Twitter X Automation
{
"mcpServers": {
"twitter-x-automation": {
"command": "npx",
"args": [
"-y",
"xactions"
]
}
}
}
X MCP
{
"mcpServers": {
"twitter-x-mcp": {
"command": "npx",
"args": [
"-y",
"@granitebps/twitter-mcp"
],
"env": {
"TWITTER_MODE": "YOUR_TWITTER_MODE_HERE",
"RETTIWT_API_KEY": "YOUR_RETTIWT_API_KEY_HERE",
"TWITTER_BEARER_TOKEN": "YOUR_TWITTER_BEARER_TOKEN_HERE",
"TWITTER_API_KEY": "YOUR_TWITTER_API_KEY_HERE",
"TWITTER_API_SECRET": "YOUR_TWITTER_API_SECRET_HERE",
"TWITTER_ACCESS_TOKEN": "YOUR_TWITTER_ACCESS_TOKEN_HERE",
"TWITTER_ACCESS_SECRET": "YOUR_TWITTER_ACCESS_SECRET_HERE",
"TWITTER_REQUEST_TIMEOUT_MS": "YOUR_TWITTER_REQUEST_TIMEOUT_MS_HERE"
}
}
}
}
Frequently asked questions
Twitter X Automation is categorized under Social Media and uses a local stdio subprocess. X MCP belongs to Social Media and uses a local stdio subprocess. Pick Twitter X Automation for social media work and X MCP for social media.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Twitter X Automation has no declared pricing — check the project's own site. X MCP has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add twitter-x-automation and twitter-x-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Twitter X Automation has a quality signal of 51/100 (Good) with 3 views, 0 installs and 604 GitHub stars. X MCP has 56/100 (Good) with 1 views, 0 installs and 1 GitHub stars.