Integrations
Connect Social Fetch to your stack
MCP, n8n, Apify, Pipedream, TypeScript SDK, and REST — same endpoints, same envelope, same credit metering.
Social Fetch MCP
87 endpoint tools plus docs search/read for Cursor, VS Code, and Claude — OAuth at api.socialfetch.dev/mcp.
Social Fetch for n8n
One node for TikTok, Instagram, YouTube, and 8 more platforms — every public endpoint, ready for your workflows and AI agents.
Social Fetch on Apify
TikTok Store Actors with dataset export and pay-per-result billing — no Social Fetch API key in your input.
Social Fetch for Pipedream
Polling profile updates plus consolidated profile, post, transcript, and balance actions — components ready for registry PR.
One API, several front doors
Routes, response shape, and credits are identical whether you call from curl, the SDK, an n8n workflow, or an MCP tool in Cursor. What changes is who holds the API key, how retries work, and how much wiring you do before the first successful lookup.
None of these paths lock you out of the others. A common pattern: prototype in the playground or MCP, pin explicit routes in the SDK for production, and keep n8n for ops alerts that do not belong in your main codebase.
Pick your integration path
Four entry points cover most teams we talk to. Open the guide for auth steps, example calls, and billing notes for that surface.
MCP for AI clients
Best for: Cursor, VS Code, or Claude Desktop — 87 endpoint tools plus docs search without maintaining your own OpenAPI plugin.
Tradeoff: OAuth at api.socialfetch.dev/mcp. Great for exploration; less ideal for headless cron that cannot complete a browser login.
Open guiden8n verified node
Best for: One node for TikTok, Instagram, YouTube, and eight more platforms with every public operation exposed.
Tradeoff: Visual wiring is fast; complex branching still lives in workflow JSON or a Code node.
Open guideTypeScript SDK
Best for: Node or TypeScript services with method names that match REST routes and Result-based errors.
Tradeoff: You own deployment, retries, and secret storage — the SDK does not run your cron schedule.
Open guideApify Store Actors
Best for: TikTok dataset export on Apify billing — pay per result, no Social Fetch API key in Actor input.
Tradeoff: Platform coverage is Actor-specific; the full catalog lives on REST and MCP.
Open guide
Still deciding?
Run a smoke test in the playground, then read the quickstart. REST and SDK docs cover auth headers and meta fields every other path inherits.