Twitterapi IO MCP vs X Twitter Scraper
A side-by-side look at the Twitterapi IO MCP and X Twitter Scraper MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Twitterapi IO MCP for social media work as a local process; choose X Twitter Scraper for social media as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Twitterapi IO MCP when
- You need dedicated capabilities in the Social Media domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
search_twitterapi_docs, get_twitterapi_endpoint, list_twitterapi_endpoints.
Choose X Twitter Scraper when
- You need dedicated capabilities in the Social Media domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
XQUIK_API_KEY.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Social Media | Social Media |
| Quality signal | 65/100 · Great | 63/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | API key required |
| Pricing | Free | Paid service |
| Required env vars | None listed | XQUIK_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 10 | 218 |
| Directory activity | 1 views 0 installs 0 upvotes | 4 views 0 installs 0 upvotes |
| Tools | 7 | Not listed |
| Full listing | View Twitterapi IO MCP | View X Twitter Scraper |
Tools & capabilities
Twitterapi IO MCP tools 7
search_twitterapi_docsSearch 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_endpointGet 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_ruleslist_twitterapi_endpointsList 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_guideGet 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_urlFetch 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_pricingGet 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_authGet 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.
X Twitter Scraper tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Twitterapi IO MCP
{
"mcpServers": {
"twitterapi-io-mcp": {
"command": "npx",
"args": [
"-y",
"twitterapi-io-mcp"
]
}
}
}
X Twitter Scraper
{
"mcpServers": {
"xquik-dev-x-twitter-scraper": {
"command": "bunx",
"args": [
"shadcn@4.18.0"
],
"env": {
"XQUIK_API_KEY": "YOUR_XQUIK_API_KEY_HERE"
}
}
}
}
Frequently asked questions
Twitterapi IO MCP is categorized under Social Media and uses a local stdio subprocess. X Twitter Scraper belongs to Social Media and uses a local stdio subprocess. Pick Twitterapi IO MCP for social media work and X Twitter Scraper for social media.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Twitterapi IO MCP is listed as free. Auth: no auth required. X Twitter Scraper is listed as a paid service. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add twitterapi-io-mcp and xquik-dev-x-twitter-scraper as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Twitterapi IO MCP has a quality signal of 65/100 (Great) with 1 views, 0 installs and 10 GitHub stars. X Twitter Scraper has 63/100 (Good) with 4 views, 0 installs and 218 GitHub stars.