Hosted MCP for social data
Add https://api.socialfetch.dev/mcp to Cursor, VS Code, or Claude, finish OAuth in the browser, and call the same 137 marketplace operations you get over REST — across 17 platforms. No API key in mcp.json.
What you get
Social Fetch runs a remote Streamable HTTP MCP server. Each public API operation becomes a typed tool (tiktok_profile_get maps to GET /v1/tiktok/profiles/{handle}). Arguments, credits, and response envelopes match the REST API. Free helpers cover docs_search, docs_read, and auth/billing utilities.
Use MCP while you build: the agent inspects live JSON, tries nl_ask_post for exploration, then you pin typed tools or ship with the TypeScript SDK. Production cron that cannot open a browser should use an API key over REST instead.
Connect a client
One-click install for Cursor, VS Code, and Windsurf, or paste the server URL into any MCP client that supports remote HTTP with OAuth.
Server URL: https://api.socialfetch.dev/mcp
Manual Cursor config
~/.cursor/mcp.json or project .cursor/mcp.json. Restart the client, then finish the OAuth browser flow when prompted.
OAuth and credits
Auth is OAuth 2.1. The client opens Social Fetch, you approve access, and it stores a token. Credits charge to the signed-in account — same rates and meta.creditsCharged fields as REST. Docs tools are free.
Anonymous walk-up without OAuth can pay metered tools with x402 (USDC on Base). Whoami, balance, and nl_ask_post still need OAuth. Invalid Bearer returns 401.
Install Agent Skills
Skills teach the harness how to use Social Fetch: read llms.txt and agents.txt, connect MCP, call POST /v1/ask, and never invent routes. Pair Skills with MCP for the usual Cursor or Claude setup.
Orientation files for agents
- llms.txt
Recommended reading order, platform coverage, and links before writing integration code.
- agents.txt
Short crawl/onboarding file for agent harnesses that look for /agents.txt.
- Ask
Natural-language router (POST /v1/ask). Via MCP, call nl_ask_post, then pin the typed tool.
- MCP docs
Scoped tool URLs, client snippets, troubleshooting, and x402 notes.
- Agent Skills docs
Install flags, what the skill teaches, and Skills vs MCP.
- Cursor & Claude guide
End-to-end MCP + llms.txt workflow with copy-paste configs.
FAQ
Do I put an API key in mcp.json?
No. Use OAuth. The client opens Social Fetch in the browser, you approve, and it stores a token. Keep sfk_… keys for REST and the SDK.
How are MCP tools billed?
Endpoint tools bill like the matching REST route (usually 1 credit on a completed standard lookup). docs_search and docs_read are free. Check meta.creditsCharged on each response.
Does MCP cover all 17 platforms?
Yes. The base server exposes the marketplace catalog — 137 operations across 17 platforms — plus auth, billing, docs, and nl_ask_post helpers. Scope with ?platforms= or ?tools= when you want a smaller tools/list.
What is the difference between MCP and Agent Skills?
MCP gives live tools. Skills give durable onboarding instructions in the agent harness (read llms.txt, use Ask, never invent endpoints). Most Cursor/Claude setups use both.
How do I explore with natural language?
Call nl_ask_post (mirrors POST /v1/ask). Routing is free; the nested lookup bills normally. Read data.routedOperation, then switch to the typed MCP tool for production workflows.
Can I use MCP for headless cron?
Not well. OAuth needs a browser once per client. For unattended jobs, use an API key with REST or the TypeScript SDK. Keep MCP for interactive coding agents.
Where is the install and troubleshooting detail?
The MCP docs cover one-click install, scoped URLs, Claude Code, stdio bridges, and common 401/402 fixes. This page is the product overview.
Connect MCP and start looking up
100 free credits, no card. Install the server, finish OAuth, optionally add Agent Skills so the harness stops inventing routes.