Twitter X Automation vs TwittrAPI
A side-by-side look at the Twitter X Automation and TwittrAPI MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
T
TwittrAPISocial Media · Local subprocess (stdio)Read public Twitter/X data: tweets, profiles, followers, search. No X developer account.33EmergingAuth: not declaredVerdict: choose Twitter X Automation for social media work as a local process; choose TwittrAPI 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.
TChoose TwittrAPI when
- You need dedicated capabilities in the Social Media domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | T TwittrAPI | |
|---|---|---|
| Category | Social Media | Social Media |
| Quality signal | 51/100 · Good | 33/100 · Emerging |
| 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 | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 591 | — |
| Directory activity | 1 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Twitter X Automation | View TwittrAPI |
Tools & capabilities
Twitter X Automation tools
No tool names declared yet. Check the project README from the listing page.
TwittrAPI tools
No tool names declared yet. Check the project README from the listing page.
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"
]
}
}
}
TwittrAPI
{
"mcpServers": {
"twittrapi": {
"command": "npx",
"args": [
"-y",
"twittrapi-mcp"
]
}
}
}
Frequently asked questions
Twitter X Automation is categorized under Social Media and uses a local stdio subprocess. TwittrAPI belongs to Social Media and uses a local stdio subprocess. Pick Twitter X Automation for social media work and TwittrAPI 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. TwittrAPI 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 twittrapi 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 1 views, 0 installs and 591 GitHub stars. TwittrAPI has 33/100 (Emerging) with 0 views, 0 installs and 0 GitHub stars.