Integrations
Connect Social Fetch to your stack
MCP, Agent Skills, n8n, Apify, Pipedream, Make, TypeScript SDK, and REST — one catalog, one envelope, one credit meter.
Social Fetch MCP
184 endpoint tools plus docs search/read for Cursor, VS Code, and Claude — OAuth at api.socialfetch.dev/mcp.
Social Fetch Agent Skills
npx skills add — teach Cursor and Claude to read llms.txt, use MCP, call POST /v1/ask, and never invent endpoints.
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.
Social Fetch for Make
Capability modules for Make scenarios — profiles, posts, search, web, and balance with your sfk_ API key (invite-based custom app).
One API, several front doors
Routes, response shape, and credits are identical across curl, SDK, n8n, and MCP. What changes is key ownership, retries, and wiring.
Common pattern: prototype in playground or MCP, pin SDK routes in production, keep n8n for ops alerts.
Pick your integration path
Entry points that 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 — 184 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 guideAgent Skills
Best for: Install with npx skills — teach agents to read llms.txt, use MCP, call POST /v1/ask, and never invent endpoints.
Tradeoff: Instructions live in the agent harness; pair with MCP or REST for live calls. Use -s socialfetch when installing from this monorepo.
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 guideMake custom app
Best for: Make scenarios with capability modules over the public API — profiles, posts, search, web, and balance.
Tradeoff: Invite-based custom app until directory listing; use the same sfk_ key as n8n and REST.
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.