SocialCrawl vs Twitter X Automation
A side-by-side look at the SocialCrawl and Twitter X Automation MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose SocialCrawl for social media work as a local process; choose Twitter X Automation 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 SocialCrawl when
- You need dedicated capabilities in the Social Media domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
SOCIALCRAWL_API_KEY. - You want tools like
socialcrawl_find, socialcrawl_endpoint, socialcrawl_estimate.
Choose Twitter X Automation when
- You need dedicated capabilities in the Social Media domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Social Media | Social Media |
| Quality signal | 56/100 · Good | 51/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | SOCIALCRAWL_API_KEY | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 612 |
| Directory activity | 1 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 7 | Not listed |
| Full listing | View SocialCrawl | View Twitter X Automation |
Tools & capabilities
SocialCrawl tools 7
socialcrawl_findStart here: a task in plain words -> the best endpoints (3 by default) of 646, each with the params the task supplies (URLs and @handles resolved), the params still missing, the credit cost and the exact call. With no task it lists platforms, or one platform's endpoints. Free; no key needed.socialcrawl_endpointRead before calling: one endpoint's purpose, params, where the rows are and up to 25 response fields, cost rule, paging, latency, timeout, next endpoints and a sample link. id (or platform+resource, path), a platform slug (its endpoints) or a guide topic. Free.socialcrawl_estimateExact credits before you spend: one call (id, platform+resource or path, plus the params you will send; calls for a job total; items for a walk) or a plan of several calls. Uses the API's estimator when available, else the bundled pricing. A platform slug gives its price table; no id gives the pricing overview. Free.socialcrawl_requestCall one endpoint (platform+resource, or id, or path). Validated locally first (a bad call is free), quoted, refused above max_credits and confirmed above the threshold. A large page is cut at row boundaries; socialcrawl_collect result_id reads the rest. Spends credits; needs SOCIALCRAWL_API_KEY.socialcrawl_collectWalk a paged endpoint (id, platform+resource or path) to `items` unique rows, the last page or max_credits: cursors supplied, duplicates dropped, stops on a 402, refused free when one page exceeds max_credits. Small results come back whole. result_id (+offset, limit, format) reads a stored result, free. Spends credits.socialcrawl_accountFree checks: balance (with this session's spend), transactions (itemised ledger; the receipts for one request_id), status (platform health; read it before retrying a 502/503) and freshness (whether this server's bundled catalogue is behind the API).socialcrawl_manageStateful work by area + action: monitors (scheduled recipes, webhooks, alerts), cohorts (mention search over your own panel of accounts), web (scrape, search, crawl and agent jobs, change monitors, browser sessions) and jobs (Prism background jobs). A wrong field is refused free with the rules. Managing is free; scrapes, jobs, queries and monitor runs bill credits. dry_run: true validates and quotes a create/update and never creates it. rows_new alerts need track (id=monitors).
Twitter X Automation 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.
SocialCrawl
{
"mcpServers": {
"socialcrawl": {
"command": "npx",
"args": [
"-y",
"socialcrawl-mcp"
],
"env": {
"SOCIALCRAWL_API_KEY": "YOUR_SOCIALCRAWL_API_KEY_HERE"
}
}
}
}
Twitter X Automation
{
"mcpServers": {
"twitter-x-automation": {
"command": "npx",
"args": [
"-y",
"xactions"
]
}
}
}
Frequently asked questions
SocialCrawl is categorized under Social Media and uses a local stdio subprocess. Twitter X Automation belongs to Social Media and uses a local stdio subprocess. Pick SocialCrawl for social media work and Twitter X Automation 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.
SocialCrawl has no declared pricing — check the project's own site. Twitter X Automation has no declared pricing — check the project's own site. 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 socialcrawl and twitter-x-automation as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, SocialCrawl has a quality signal of 56/100 (Good) with 1 views, 0 installs and 0 GitHub stars. Twitter X Automation has 51/100 (Good) with 3 views, 0 installs and 612 GitHub stars.