What is MCP for social data?
MCP connects AI clients (Cursor, Claude, VS Code, etc.) to tools over a standard protocol. MCP for social data means those clients call Social Fetch operations as tools — same REST catalog, same billing, OAuth instead of an API key in config.
What's actually on offer
Hosted MCP at https://api.socialfetch.dev/mcp — add URL, OAuth in browser, no sfk_ key. Tools map 1:1 from REST: ${MARKETING_PLATFORM_COUNT} platforms, ${MARKETING_API_ENDPOINTS} operations.
Tool names: {platform}_{resource}_{action} — tiktok_profile_get, youtube_video_transcript_get, etc. Free utilities: docs_search, docs_read, auth_whoami, billing_balance_get, nl_ask_post.
A concrete call
tiktok_profile_get → data.lookupStatus + profile fields, meta.requestId/creditsCharged/version — same as REST except OAuth auth instead of x-api-key.
Unclear ask → nl_ask_post (0 routing credits; nested lookup bills normally). Response includes routed operation for repeat typed calls.
How it's used in practice
Prototyping in Cursor/Claude/VS Code — explore without hand-writing HTTP. Claude Code: `claude mcp add --transport http socialfetch https://api.socialfetch.dev/mcp`.
Pattern: docs_search/nl_ask_post to orient, then pin typed tool or REST path for production/CI. Credits charge to OAuth account — same balance as REST.
MCP vs plain REST integration
REST/@socialfetch/sdk for servers, CI, backends — long-lived sfk_ key.
MCP for MCP-aware clients: typed tool list, OAuth avoids keys in config files. Same catalog, envelope, billing — different transport.
Common mistakes
Pasting sfk_ key in mcp.json — hosted server is OAuth only.
200 without checking lookupStatus — not_found is a completed answer, not success with data.
Inventing tool names — use MCP tool list, docs_search, or nl_ask_post.
What it is not
Not different data or broader scope — same public-data as REST.
Not separate pricing — same credit rules including not_found billing.
Not a replacement for Agent Skills — MCP provides tools; Skills provide usage instructions. Install both.
FAQ
What is MCP for social media data?
MCP lets AI clients call external tools. Social Fetch exposes the REST catalog as typed MCP tools with OAuth auth.
How do I connect Claude to a social data API?
`claude mcp add --transport http socialfetch https://api.socialfetch.dev/mcp`, then `/mcp` for OAuth. See /docs/integrations/mcp.
Do I put an API key in mcp.json?
No for hosted Social Fetch MCP — OAuth in browser when connecting.
Are MCP calls billed differently from REST?
No — same credits, 402 behavior, meta.creditsCharged. docs_search, docs_read, auth_whoami, billing_balance_get free on both.
What tools does Social Fetch expose over MCP?
{platform}_{resource}_{action} mapped from REST plus docs_search, docs_read, auth_whoami, billing_balance_get, nl_ask_post.
What's the difference between MCP and the /v1/ask endpoint?
Same routing idea — POST /v1/ask on REST, nl_ask_post on MCP. 0 routing credits; nested lookup bills normally.
Should I use MCP or REST in production?
REST/SDK for servers and CI with API key. MCP for AI clients prototyping or agent workflows.
Does MCP give access to different or more data than REST?
No — same public-data scope, platforms, and lookupStatus semantics.