A side-by-side look at the Influship 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 Influship 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 Influship when
You need dedicated capabilities in the Social Media domain.
You prefer a local stdio subprocess transport.
You have the keys it needs: INFLUSHIP_API_KEY, INFLUSHIP_MCP_URL.
You want tools like search_creators, autocomplete_creators, find_lookalike_creators.
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.
Influship 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 Influship 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.
Influship has no declared pricing — check the project's own site. 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 influship 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, Influship has a quality signal of 52/100 (Good) with 1 views, 0 installs and 1 GitHub stars. X Twitter Scraper has 63/100 (Good) with 4 views, 0 installs and 214 GitHub stars.