Vidlens MCP vs X Twitter Scraper
A side-by-side look at the Vidlens 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 Vidlens 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 Vidlens MCP when
- You need dedicated capabilities in the Social Media domain.
- You prefer a local stdio subprocess transport.
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 | 43/100 · Fair | 63/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | Paid service |
| Required env vars | None listed | XQUIK_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 34 | 214 |
| Directory activity | 1 views 0 installs 0 upvotes | 4 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Vidlens MCP | View X Twitter Scraper |
Tools & capabilities
Vidlens MCP tools
No tool names declared yet. Check the project README from the listing page.
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.
Vidlens MCP
{
"mcpServers": {
"vidlens-mcp-2": {
"command": "npx",
"args": [
"-y",
"vidlens-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
Vidlens 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 Vidlens 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.
Vidlens MCP 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 vidlens-mcp-2 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, Vidlens MCP has a quality signal of 43/100 (Fair) with 1 views, 0 installs and 34 GitHub stars. X Twitter Scraper has 63/100 (Good) with 4 views, 0 installs and 214 GitHub stars.