Access 21+ social media platforms through one unified API. Profiles, posts, search.
Most knowledge and memory work still happens through a UI a human drives. SocialCrawl MCP server moves it into the conversation instead. Access 21+ social media platforms through one unified API. Profiles, posts, search.
Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
The server publishes 5 tools. What each one is for:
socialcrawl_list_platforms — Discover all 21 supported platforms with their slugs and endpoint countssocialcrawl_list_endpoints — See all endpoints, required parameters, and credit costs for a specific platformsocialcrawl_request — Make any SocialCrawl API call — fetch profiles, posts, comments, search results, and moresocialcrawl_get_docs — Access detailed API documentation for a platform or specific endpointCursor — Add to .cursor/mcp.json in your project root or ~/.cursor/mcp.json globally:Configuration is passed through the environment: SOCIALCRAWL_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
This sits in the knowledge and memory group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. SocialCrawl's toolset — socialcrawl_list_platforms, socialcrawl_list_endpoints, socialcrawl_request and 2 more — is a fair guide to whether it matches your workflow. It is maintained by RidioDevelopment; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| socialcrawl_list_platforms | Discover all 21 supported platforms with their slugs and endpoint counts |
| socialcrawl_list_endpoints | See all endpoints, required parameters, and credit costs for a specific platform |
| socialcrawl_request | Make any SocialCrawl API call — fetch profiles, posts, comments, search results, and more |
| socialcrawl_get_docs | Access detailed API documentation for a platform or specific endpoint |
| Cursor | Add to .cursor/mcp.json in your project root or ~/.cursor/mcp.json globally: |
{
"mcpServers": {
"socialcrawl": {
"command": "npx",
"args": ["-y", "socialcrawl-mcp"],
"env": {
"SOCIALCRAWL_API_KEY": "your_api_key_here"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| SOCIALCRAWL_API_KEY | Credential the server authenticates with. | Yes |
A knowledge graph your assistant keeps between sessions — entities, relations and observations that persist.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
A structured scratchpad for hard problems — stepwise reasoning with revisions, branches and visible logic.
Symbol-level code navigation, refactoring and memory for coding agents — the IDE brain your assistant has been missing.
Chat with your second brain — search, read and write vault notes through the Local REST API.