In-depth architectural comparison of the Scrapebadger MCP and Twitterapi Docs MCP 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
Scrapebadger MCP
Social Media · Local stdio
Quality: 51/100 (Good) | Auth: No auth required
Twitterapi Docs MCP
Social Media · Local stdio
Quality: 60/100 (Good) | Auth: No auth required
Verdict Summary: Choose Scrapebadger MCP if you need specialized Social Media tools running via a local process. Choose Twitterapi Docs MCP if your workspace requires Social Media integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Scrapebadger 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).
Scrapebadger MCP is categorized under Social Media and uses a local stdio subprocess. In contrast, Twitterapi Docs MCP belongs to Social Media using local stdio subprocess. Select Scrapebadger MCP when you need capabilities focused on social media and Twitterapi Docs MCP when you require tools for social media.
Search for tweets (supports Twitter search operators)
get_twitter_trends
Get global trending topics (optionally by category)
get_twitter_place_trends
Get trends for a specific location (by WOEID)
search_twitter_places
Search for Twitter places by name
get_twitter_list_detail
Get details about a Twitter list
+4 more tools listed on main page
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
Get a TwitterAPI.io page from the offline snapshot by page key.
USE THIS WHEN: You need the full content of a specific page (guides, docs, policies, contact, etc.).
TIP: Use search_twitterapi_docs if you don't know the page key.
RETURNS: Full guide content with headers, paragraphs, and code examples.
get_twitterapi_url
Fetch a TwitterAPI.io or docs.twitterapi.io URL.
USE THIS WHEN: You have a specific link and want its full content.
RETURNS: Parsed content from the offline snapshot. If not found, you can set fetch_live=true (restricted to twitterapi.io/docs.twitterapi.io).
get_twitterapi_pricing
Get TwitterAPI.io pricing information: credit system, endpoint costs, QPS limits.
USE THIS WHEN: You need to know API costs, credit calculations, or rate limits.
RETURNS: Pricing tiers, credit costs per endpoint, QPS limits by balance level.
get_twitterapi_auth
Get TwitterAPI.io authentication guide: API key usage, headers, code examples.
USE THIS WHEN: You need to set up authentication or see request examples.
RETURNS: API key header format, base URL, cURL/Python/JavaScript examples.