Twitr.sh vs Twitterapi

In-depth architectural comparison of the Twitr.sh and Twitterapi 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 Twitr.sh 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 Twitr.sh Details

Choose Twitterapi 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 Twitterapi Details

Feature & Specification Comparison

Specification	Twitr.sh Social Media	Twitterapi Social Media
Summary	X/Twitter reads, search, monitors and posting. Pay-per-call in USDC — no signup, no API keys.	Read/write X (Twitter) via twitterapi.io: mentions, thread context, create and delete tweets.
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": {
    "twitr-sh": {
      "command": "npx",
      "args": [
        "-y",
        "agentcash"
      ]
    }
  }
}

{
  "mcpServers": {
    "twitterapi": {
      "command": "npx",
      "args": [
        "-y",
        "@pedrot95dev/twitterapi.mcp"
      ]
    }
  }
}

Related MCP Server Comparisons