Side-by-Side Model Context Protocol Comparison
Twitterapi Docs MCP vs PitchGhost
In-depth architectural comparison of the Twitterapi Docs MCP and PitchGhost 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.
At a Glance & Executive Verdict
Twitterapi Docs MCP
Social Media · Local stdio
Quality: 60/100 (Good) | Auth: No auth required
PitchGhost
Social Media · Remote HTTP/SSE
Quality: 49/100 (Fair) | Auth: No auth required
Verdict Summary: Choose Twitterapi Docs MCP if you need specialized Social Media tools running via a local process. Choose PitchGhost if your workspace requires Social Media integration with remote web transport. Both servers can be configured concurrently in your client's
mcpServers manifest.Which MCP Server Should You Choose?
Choose Twitterapi Docs MCP 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).
- Primary tools included: search_twitterapi_docs, get_twitterapi_endpoint, list_twitterapi_endpoints.
Choose PitchGhost 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).
- Primary tools included: whoami, search_ghosts, get_ghost.
Feature & Specification Comparison
Tools & Capabilities Breakdown
Twitterapi Docs MCP Tools (7)
search_twitterapi_docs
Search TwitterAPI.io documentation: API endpoints, guides (pricing, rate limits, filter rules), and blog posts.
USE THIS WHEN: You need to find information across the entire documentation.
RETURNS: Ranked results with endpoint paths, descriptions, and relevance scores.
Examples:
- "advanced search" → finds tweet search endpoints
- "rate limit" → finds QPS limits and pricing info
- "webhook" → finds webhook setup endpoints
- "getUserInfo" → finds user info endpoints (supports camelCase)
get_twitterapi_endpoint
Get complete documentation for a specific TwitterAPI.io endpoint.
USE THIS WHEN: You know the exact endpoint name (e.g., from search results).
RETURNS: Full details including path, parameters, cURL example, and code snippets.
Common endpoints:
- get_user_info, get_user_followers, get_user_following
- tweet_advanced_search, get_tweet_by_id
- add_webhook_rule, get_webhook_rules
list_twitterapi_endpoints
List all TwitterAPI.io API endpoints organized by category.
USE THIS WHEN: You need to browse available endpoints or find endpoints by category.
CATEGORIES: user, tweet, community, webhook, stream, action, dm, list, trend
RETURNS: Endpoint names with HTTP method and path for each category.
get_twitterapi_guide
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).
Twitterapi Docs MCP Configuration
PitchGhost Configuration