TwtAPI vs Xdataapi: X (Twitter) data
A side-by-side look at the TwtAPI and Xdataapi: X (Twitter) data MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose TwtAPI for social media work over a hosted endpoint; choose Xdataapi: X (Twitter) data for social media over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose TwtAPI when
- You need dedicated capabilities in the Social Media domain.
- You prefer a remote HTTP/SSE transport.
Choose Xdataapi: X (Twitter) data when
- You need dedicated capabilities in the Social Media domain.
- You prefer a remote HTTP/SSE transport.
- You have the keys it needs:
XDATAAPI_KEY.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Social Media | Social Media |
| Quality signal | 40/100 · Fair | 40/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Remote HTTP/SSE |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | XDATAAPI_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 1 |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View TwtAPI | View Xdataapi: X (Twitter) data |
Tools & capabilities
TwtAPI tools
No tool names declared yet. Check the project README from the listing page.
Xdataapi: X (Twitter) data 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.
TwtAPI
{
"mcpServers": {
"twtapi": {
"url": "https://mcp.twtapi.com/mcp"
}
}
}
Xdataapi: X (Twitter) data
{
"mcpServers": {
"xdataapi-x-twitter-data-3": {
"url": "https://api.xdataapi.io/mcp"
}
}
}
Frequently asked questions
TwtAPI is categorized under Social Media and uses a remote HTTP/SSE transport. Xdataapi: X (Twitter) data belongs to Social Media and uses a remote HTTP/SSE transport. Pick TwtAPI for social media work and Xdataapi: X (Twitter) data 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.
TwtAPI has no declared pricing — check the project's own site. Xdataapi: X (Twitter) data 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 twtapi and xdataapi-x-twitter-data-3 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, TwtAPI has a quality signal of 40/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Xdataapi: X (Twitter) data has 40/100 (Fair) with 0 views, 0 installs and 1 GitHub stars.