Social → Context vs SocialCrawl

A side-by-side look at the Social → Context and SocialCrawl MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Social → Context logoSocial → ContextSocial Media · Remote HTTP/SSETurn a TikTok/Instagram/YouTube link into text for your AI: metadata, transcript and image OCR.55GoodAuth: not declaredSocialCrawl logoSocialCrawlSocial Media · Local subprocess (stdio)Access 21+ social media platforms through one unified API. Profiles, posts, search.56GoodAuth: not declared

Verdict: choose Social → Context for social media work over a hosted endpoint; choose SocialCrawl 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?

Social → Context logoChoose Social → Context when

  • You need dedicated capabilities in the Social Media domain.
  • You prefer a remote HTTP/SSE transport.
  • You want tools like socialdl_extract, socialdl_metadata, socialdl_download.
Explore Social → Context

SocialCrawl logoChoose 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.
Explore SocialCrawl

Feature & specification comparison

Rows where the two servers differ are marked.

SpecSocial → Context logoSocial → ContextSocialCrawl logoSocialCrawl
CategorySocial MediaSocial Media
Quality signal55/100 · Good56/100 · Good
Install commandConfirmedConfirmed
TransportRemote HTTP/SSELocal subprocess (stdio)
AuthNot declaredNot declared
PricingNot declaredNot declared
Required env varsNone listedSOCIALCRAWL_API_KEY
Verified ownerCommunity listingCommunity listing
GitHub stars00
Directory activity 1 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
Tools97

Tools & capabilities

Social → Context tools 9

  • socialdl_extractDownload a social-media link (TikTok, Instagram reel/post/carousel, YouTube, or any direct .mp4) and return it as usable text context: metadata (author, caption, duration), the audio/video transcript, and a vision description (OCR + summary) of each image in a carousel/post. YouTube uses its existing captions when available. Use this to give Claude the content of a video or post the user pasted.
  • socialdl_metadataLightweight lookup: resolve a social-media link to its metadata (author, caption, duration, counts) and media URLs WITHOUT transcribing or running vision. Cheaper than socialdl_extract — use when the caption/context alone is enough.
  • socialdl_downloadResolve a TikTok / Instagram / YouTube link (or direct .mp4/image URL) to its DIRECT download URLs from the source CDN — every video quality, audio track and image, with quality labels. Use when the user wants to DOWNLOAD/save the media instead of transcribing it. No transcription/vision.
  • show_versionShow the current MCP platform and adapter versions.
  • report_bugReport a bug, missing feature, or send feedback. Include the conversation array with recent messages for reproduction.
  • connectReturns connection status and URLs. When all providers are connected, returns authenticated:true and empty pending[]. When credentials are missing, returns connect_url for the toolkit and per-install URLs.
  • toolkit_infoReturns the current toolkit state: installed MCPs, their connection status, the accounts connected to each one, and how many catalog tools each exposes.
  • marketplaceThe official mcp.ai marketplace — the in-platform catalog of every MCP/tool, AND the way to run them. Covers capability requests like "find an MCP that does X", "consulta um CPF", "is there a tool for Y". Core flow: action=search discovers MCPs by intent → describe returns one MCP's full profile (every tool with its id + params, pricing, auth) so you pick the right tool_id → invoke RUNS that tool. KEY: invoke works even when the MCP is NOT installed — it runs the tool pontualmente (one-off), without adding the MCP to the toolkit and without bloating the tool list. If the MCP needs a credential/login, invoke returns a connect link; if it is paid and the wallet is empty, invoke returns a checkout/top-up link (the user opens it, then you retry). Use install only to make an MCP PERMANENT in the active toolkit (its tools then show up natively in future sessions); prefer invoke for a single/occasional use. list_tools lists what is callable right now. subscribe/cancel handle per-MCP billing; report_bug sends feedback; request_mcp asks us to build a NEW MCP when nothing fits. Search/describe flag installed_in_toolkit vs installed_in_workspace. Writes (install/uninstall/subscribe/cancel and the one-off install behind invoke) require workspace owner/admin. It also carries the mcp.ai PROMPT LIBRARY, which is about ready-made prompt TEXT rather than MCPs: search_prompts finds one, get_prompt returns its full text with {{variables}} filled, and publish_prompt saves a prompt and returns a shareable mcp.ai/p/<slug> link that opens without login.
  • authenticateMCP.AI for IDE agents (Cursor, etc.): log in in the browser, copy the access token. Best: add it to this server's config as a header `Authorization: Bearer <token>` for a permanent, non-expiring connection. Or paste it here for a session-only login: call with { token: "<jwt>" } after the user pastes, or with no args to get the link.

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).

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.

Social → Context

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "social-context": {
      "url": "https://api.mcp.ai/p_socialdl"
    }
  }
}

SocialCrawl

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "socialcrawl": {
      "command": "npx",
      "args": [
        "-y",
        "socialcrawl-mcp"
      ],
      "env": {
        "SOCIALCRAWL_API_KEY": "YOUR_SOCIALCRAWL_API_KEY_HERE"
      }
    }
  }
}

Frequently asked questions

Social → Context is categorized under Social Media and uses a remote HTTP/SSE transport. SocialCrawl belongs to Social Media and uses a local stdio subprocess. Pick Social → Context for social media work and SocialCrawl 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.

Social → Context has no declared pricing — check the project's own site. SocialCrawl 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 social-context and socialcrawl as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Social → Context has a quality signal of 55/100 (Good) with 1 views, 0 installs and 0 GitHub stars. SocialCrawl has 56/100 (Good) with 1 views, 0 installs and 0 GitHub stars.