SocialCrawl

Skills & MCP Server

Connect any MCP client or agent skill to the SocialCrawl API, hosted or local

SocialCrawl ships two packages that put the API inside an AI agent: an MCP server for any MCP-compatible client, and an Agent Skill for agents that read skill files. Both call the same API, return the same envelope, and bill the same credits, so pick whichever your client supports.

Hosted MCP endpoint: https://mcp.socialcrawl.dev/mcp. Your key travels as a request header, never as a query string.

Prerequisites

  • An API key from socialcrawl.dev, under Dashboard → API Keys. New accounts start with 100 free credits and no card.
  • Hosted server: an MCP client that can send an Authorization header.
  • Local server: Node.js with npx available on your machine.
  • Agent Skill: an agent that reads skill files (Claude Code, Cursor, Windsurf, Codex, Gemini CLI, and 40+ others).

Server URL

Copy this into any client that accepts a remote MCP endpoint:

MCP URL
https://mcp.socialcrawl.dev/mcp

It speaks the Streamable HTTP transport. Send your key as Authorization: Bearer YOUR_API_KEY, or as x-api-key. A request with no key still reaches the three discovery tools (socialcrawl_find, socialcrawl_endpoint and socialcrawl_estimate), which cost nothing.

How to connect

Create an API key

Sign in at socialcrawl.dev and open Dashboard → API Keys. Keys look like sc_... and are shown once, so store yours before you leave the page. See Authentication.

Register the server with your client

Every client below reaches the same seven tools. The hosted server needs nothing installed; the local server runs socialcrawl-mcp through npx on your machine.

Hosted, one line:

Terminal
claude mcp add --transport http socialcrawl https://mcp.socialcrawl.dev/mcp \
  --header "Authorization: Bearer YOUR_API_KEY"

Local, if you would rather run the package yourself:

Terminal
claude mcp add --scope user socialcrawl -e SOCIALCRAWL_API_KEY=YOUR_API_KEY -- npx -y socialcrawl-mcp

Flags go before the -- separator; everything after it is the command Claude Code runs.

Edit ~/Library/Application Support/Claude/claude_desktop_config.json on macOS, or %APPDATA%\Claude\claude_desktop_config.json on Windows.

Hosted:

mcp.json
{
  "mcpServers": {
    "socialcrawl": {
      "type": "http",
      "url": "https://mcp.socialcrawl.dev/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Local:

mcp.json
{
  "mcpServers": {
    "socialcrawl": {
      "command": "npx",
      "args": ["-y", "socialcrawl-mcp"],
      "env": {
        "SOCIALCRAWL_API_KEY": "YOUR_API_KEY"
      }
    }
  }
}

Edit .cursor/mcp.json in your project (or the global equivalent). Cursor uses the same mcpServers shape as Claude Desktop.

mcp.json
{
  "mcpServers": {
    "socialcrawl": {
      "type": "http",
      "url": "https://mcp.socialcrawl.dev/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

For the local package, swap the three type/url/headers keys for "command": "npx", "args": ["-y", "socialcrawl-mcp"], and "env": { "SOCIALCRAWL_API_KEY": "YOUR_API_KEY" }.

Edit .vscode/mcp.json. VS Code uses the servers key and an explicit transport type.

JSON
{
  "servers": {
    "socialcrawl": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "socialcrawl-mcp"],
      "env": {
        "SOCIALCRAWL_API_KEY": "YOUR_API_KEY"
      }
    }
  }
}

Windsurf reads the same mcpServers block as Claude Desktop:

mcp.json
{
  "mcpServers": {
    "socialcrawl": {
      "command": "npx",
      "args": ["-y", "socialcrawl-mcp"],
      "env": {
        "SOCIALCRAWL_API_KEY": "YOUR_API_KEY"
      }
    }
  }
}

Any client with stdio transport works with the same three values: command npx, args ["-y", "socialcrawl-mcp"], and SOCIALCRAWL_API_KEY in the environment.

Any client that supports a remote Streamable HTTP server needs the URL plus a header:

MCP URL
https://mcp.socialcrawl.dev/mcp
Authorization: Bearer YOUR_API_KEY

A client that cannot attach a custom header still connects, but only the three no-key discovery tools will work.

Restart and verify

Restart the client so it reads the new configuration, then ask the agent to list SocialCrawl platforms. That runs socialcrawl_find with no task, which costs nothing and proves the connection before you spend a credit.

To check the hosted server itself:

cURL
curl https://mcp.socialcrawl.dev/healthz

Available tools

The MCP server exposes seven tools, in this order:

ToolWhat it doesNeeds API key?
socialcrawl_findStart here. A task in plain words becomes the best endpoints, each with the parameters the task already supplies, the ones still missing, the credit cost and the exact call. With no task it lists the platforms, or one platform's endpointsNo
socialcrawl_endpointOne endpoint's contract: purpose, parameters, where the rows are, up to 25 response fields, cost rule, paging, latency and timeout. A platform slug returns its endpoints; a topic such as errors or pagination returns that guideNo
socialcrawl_estimateThe exact credits before you spend, for one call, a plan of several calls, or a walk of items rows. A platform slug returns its price tableNo
socialcrawl_requestCalls one endpoint, GET, or POST with a body for the batch endpoints. Refuses a call above max_credits, and cuts a large page at row boundariesYes
socialcrawl_collectWalks a paged endpoint until items unique rows, the last page or max_credits, supplying the cursors and dropping duplicates. result_id reads a stored result for freeYes
socialcrawl_accountFree checks: balance (with this session's spend), transactions (the receipts for one request_id), status (platform health) and freshness (whether the server's catalogue is behind the API)Yes, except status
socialcrawl_manageStateful work by area and action: Monitors, cohorts, web jobs, change monitors and browser sessions, and Prism background jobs. Managing is free; runs, scrapes and queries billYes

The three discovery tools need no key and cost nothing, so an agent can find the endpoint for a task, read its parameters and price the call before it spends anything. With a key set they ask the API's free /v1/utility/* routes first, and answer from the catalogue bundled with the server when a route cannot be reached. socialcrawl_request and socialcrawl_collect spend credits at each endpoint's own price.

Local validation before every call

Before it sends anything, socialcrawl_request checks locally that the platform exists, the endpoint exists, and all required parameters are present. A bad call comes back as a fix-it message instead of a wasted credit.

Agent Skill

The socialcrawl skill works with Claude Code, Cursor, Windsurf, Codex, Gemini CLI, and 40+ other agents. It lets your agent fetch current public data (subject to documented endpoint caches), generate code snippets, and answer API questions in natural language.

Install it from skills.sh:

Terminal
npx skills add socialcrawl/skills

Add -g to install globally instead of per project. To install from Git, copy the socialcrawl subdirectory rather than the whole repository, because agents discover a skill at <skills-dir>/<name>/SKILL.md:

Terminal
git clone --depth 1 https://github.com/socialcrawl/skills /tmp/socialcrawl-skills
mkdir -p .claude/skills
cp -r /tmp/socialcrawl-skills/skills/socialcrawl .claude/skills/socialcrawl

Then export your key so it persists across sessions (add the line to ~/.bashrc, ~/.zshrc, or your shell's equivalent):

Terminal
export SOCIALCRAWL_API_KEY="YOUR_API_KEY"

The skill resolves your key from three sources in order: $SOCIALCRAWL_API_KEY, then ~/.config/socialcrawl/api_key, then a prompt. If it has to prompt, it saves the answer to ~/.config/socialcrawl/api_key so you paste it once. The literal placeholder YOUR_API_KEY is treated as unset.

Invoke it directly with /socialcrawl, or ask in natural language: "Get the TikTok profile for @charlidamelio", or "Search YouTube for machine learning videos". The skill picks the platform and endpoint, makes the call, and returns structured JSON.

Skills or MCP?

Agent SkillMCP server
Install viaskills.sh, Gitnpm, MCP Registry, hosted URL
ProtocolSkill files read by the agentMCP stdio or Streamable HTTP
Client supportClaude Code, Cursor, Windsurf, Codex, Gemini CLI, 40+Any MCP-compatible client
Discovery toolsNo (the skill handles routing)Yes (3 free tools, no key)
Local validationNoYes (saves credits)
Offline docsYes (reference files)Yes (bundled data)
PagingYes (reference file, calls the REST API)Yes (socialcrawl_collect)
MonitorsYes (reference file, calls the REST API)Yes (socialcrawl_manage, monitors)
Web and browserYes (reference file, calls the REST API)Yes (socialcrawl_manage, web)

What does it cost?

Credits are billed exactly as the REST API bills them: most endpoints are 1 credit, heavier ones 5 or 10, and composite or bundle endpoints carry their own price (search/everywhere is a flat 20). Cache hits cost 0. The three discovery tools and socialcrawl_account cost 0 too. See Endpoint pricing for the exact figure per endpoint and Credits for how the ledger works.

Troubleshooting

Next steps