socialscrape-mcp

The SocialScrape MCP server: social media data (profiles, posts, comments, search, ads, transcripts) for Claude, Cursor and any other MCP client that starts a local server.

It is generated from SocialScrape's endpoint registry and grouped so an agent sees a usable number of tools instead of one per endpoint:

Only built endpoints appear as tools. A platform shows up in the next release after its endpoints are built.

Every result starts with ok | credits charged: 1 | credits remaining: 4999 (and the structured copy carries the numbers as fields). Failures are free and come back as isError with the API's error code, a retryable flag and what to do next.

Use it

The server runs on your own machine. Your MCP client (Claude Desktop, Claude Code, Cursor) starts it as a subprocess over stdio. SocialScrape does not run a hosted MCP server, so there is no MCP URL to connect to.

{ "mcpServers": { "socialscrape": {
    "command": "uvx", "args": ["socialscrape-mcp"],
    "env": { "SOCIALSCRAPE_API_KEY": "ss_live_..." } } } }

Get a key at https://socialscrape.dev/app. Tool discovery works without a key; a tool call without one explains how to add it.

Fewer tools. Some clients cap the number of tools (Cursor warns past 40). Narrow the list in the env block:

With core alone an agent still reaches every endpoint through describe and call_endpoint.

Serve it over HTTP yourself. For a client that can only reach a URL, install the extra and run the server on a host you control: pip install 'socialscrape-mcp[http]', then socialscrape-mcp http --host 127.0.0.1 --port 8080. Each request carries its own key in the x-api-key header (or Authorization: Bearer ...), and ?platforms= and ?toolsets= narrow the tools. This is yours to run and secure; SocialScrape does not offer it as a service.

Settings (environment)