X (read Only) vs Xdataapi: X (Twitter) data

In-depth architectural comparison of the X (read Only) and Xdataapi: X (Twitter) data MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

Which MCP Server Should You Choose?

Choose X (read Only) when:

• You need dedicated capabilities in the Social Media domain.
• You prefer remote streaming HTTP/SSE transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).

Explore X (read Only) Details

X

Choose Xdataapi: X (Twitter) data when:

• You need dedicated capabilities in the Social Media domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).

Explore Xdataapi: X (Twitter) data Details

Feature & Specification Comparison

Specification	X (read Only) twscrape Twitter Social Media	X Xdataapi: X (Twitter) data Social Media
Summary	Read-only X/Twitter MCP: posts, threads, replies, search via twscrape. No API key.	Read-only public X (Twitter) data: profiles, tweets, threads, followers, search. Pay per result.
Category & Scope	Social Media

Tools & Capabilities Breakdown

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

{
  "mcpServers": {
    "twscrape-twitter-x-read-only": {
      "url": "https://YOUR-APP.example.com/mcp"
    }
  }
}

{
  "mcpServers": {
    "xdataapi-x-twitter-data-2": {
      "command": "npx",
      "args": [
        "-y",
        "xdataapi-x-twitter-data-2"
      ]
    }
  }
}

Related MCP Server Comparisons