> **For coding agents and LLMs:** This is one Social Fetch marketing page (markdown export). For API orientation start with [`/llms.txt`](https://www.socialfetch.dev/llms.txt); for auth and crawl rules use [`/agents.txt`](https://www.socialfetch.dev/agents.txt); for every operation use [`/llms-endpoints.txt`](https://www.socialfetch.dev/llms-endpoints.txt).

## This page

- **On-site (HTML):** <https://www.socialfetch.dev/glossary/mcp-for-social-data>
- **Markdown (.mdx) URL:** <https://www.socialfetch.dev/glossary/mcp-for-social-data.mdx>

---

# 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 is the default; send x-api-key if the client never prompts.

## What's actually on offer

Hosted MCP at https://api.socialfetch.dev/mcp — add the URL, finish OAuth in the browser. If the client never prompts, send x-api-key from an env var. Tools map 1:1 from REST: 25 platforms, 264 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. Auth is OAuth or the same x-api-key header.

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 the signed-in 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 so keys stay out of config files. Same catalog, envelope, billing — different transport. Clients that never prompt OAuth can still send x-api-key.

## Common mistakes

Pasting a plaintext sfk_ key in mcp.json — prefer OAuth, or interpolate x-api-key from an env var.

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 — OAuth by default, or x-api-key if the client never prompts.

### 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?

Prefer OAuth. If the client never prompts, set headers x-api-key from an env var. See /docs/integrations/mcp.

### 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.

## Related

- [MCP docs](https://www.socialfetch.dev/docs/integrations/mcp)
- [Agent Skills](https://www.socialfetch.dev/docs/integrations/skills)
- [Ask](https://www.socialfetch.dev/ask)
- [Integrations hub](https://www.socialfetch.dev/integrations)
- [API credits](https://www.socialfetch.dev/glossary/api-credits)
- [Social data for AI agents](https://www.socialfetch.dev/glossary/social-data-for-ai-agents)
- [Ask natural-language API](https://www.socialfetch.dev/glossary/ask-natural-language-api)
