SalesTouch vs X Twitter Scraper

In-depth architectural comparison of the SalesTouch and X Twitter Scraper 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 SalesTouch when:

• You need dedicated capabilities in the Social Media domain.
• You prefer remote streaming HTTP/SSE transport architecture.
• Your security boundary fits: OAuth 2.0 (Paid Service).

Explore SalesTouch Details

Choose X Twitter Scraper when:

• You need dedicated capabilities in the Social Media domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: API Key required (BYOK (Pay Provider Direct)).
• You have access to required keys: XQUIK_API_KEY.
• Primary tools included: 120+ MCP v2.6.1 endpoints covering search, profiles, timelines, followers, and more, Supports OAuth 2.1 and API key authentication, Delivers filtered data with usage-based billing on delivered results.

Explore X Twitter Scraper Details

Feature & Specification Comparison

Specification	SalesTouch Social Media	X Twitter Scraper Xquik-dev Social Media
Summary
Category & Scope	Social Media	Social Media
Quality signal

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": {
    "salestouch": {
      "url": "https://img.shields.io/badge/version-0.8.0-111827"
    }
  }
}

{
  "mcpServers": {
    "xquik-dev-x-twitter-scraper": {
      "command": "npx",
      "args": [
        "-y",
        "skills@1.5.3"
      ],
      "env": {
        "XQUIK_API_KEY": "YOUR_XQUIK_API_KEY_HERE"
      }
    }
  }
}

Related MCP Server Comparisons