Connects your coding agent to the Social Fetch API so it can pull real data from TikTok, Instagram, YouTube, X, Reddit, Spotify, and other platforms without leaving your editor. Exposes tools that map directly to the REST API: profile lookups, post fetches, video transcripts, search results, and web markdown generation. Also includes docs search and read tools so the agent can browse the Social Fetch documentation and pick the right endpoint itself. Hosted as a remote Streamable HTTP server with OAuth authentication, so there's nothing to clone or run locally. Useful when you want your agent to wire up social media integrations with live data instead of mocked responses, or when you need it to explore an API and build against it in the same session.
Let your coding agent fetch real social media and web data while it builds.
Documentation | API reference | Credits & billing
Server URL: https://api.socialfetch.dev/mcp
Social Fetch MCP connects Cursor, VS Code, Claude, Windsurf, and other MCP clients to the Social Fetch API. Once installed, your agent can look up creators, fetch posts, search platforms, read web pages, check your balance, and read the Social Fetch docs from inside your editor.
Use it when you want your agent to answer questions like:
The MCP server itself is hosted by Social Fetch:
https://api.socialfetch.dev/mcp
There is no local server to clone, build, or run from this repository. Clients connect to the hosted Streamable HTTP endpoint and authenticate with OAuth in the browser.
Agents are better when they can work with the same API your app uses. This gives them a direct, authenticated route to Social Fetch instead of making you bounce between docs, dashboards, scripts, and pasted JSON.
Social Fetch MCP exposes endpoint tools for:
docs_search and docs_read.Endpoint tools are metered like the REST API. Docs tools, auth_whoami, and billing_balance_get do not consume lookup credits.
Complete the OAuth browser flow after installing. If a one-click link does nothing - your editor is not installed, blocks custom URL schemes, or has no handler - use the manual setup below.
Add this to ~/.cursor/mcp.json or a project .cursor/mcp.json:
{
"mcpServers": {
"socialfetch": {
"url": "https://api.socialfetch.dev/mcp"
}
}
}
Restart Cursor, open MCP settings, and complete the OAuth browser flow when prompted.
Add this to settings.json:
{
"mcp": {
"servers": {
"socialfetch": {
"url": "https://api.socialfetch.dev/mcp"
}
}
}
}
claude mcp add --transport http socialfetch https://api.socialfetch.dev/mcp
Then run /mcp and authenticate Social Fetch to finish the OAuth flow.
Add a custom remote MCP connector with this URL:
https://api.socialfetch.dev/mcp
Authorize Social Fetch when Claude prompts you.
If your client only supports stdio MCP servers, bridge to the hosted server with mcp-remote:
npx mcp-remote https://api.socialfetch.dev/mcp
Point your client at the stdio process that command starts.
Social Fetch MCP uses OAuth 2.1. Your MCP client handles the flow:
Do not paste a Social Fetch API key into MCP config. Credits are charged to the signed-in account, just like REST API requests.
tools/list exposes endpoint tools plus docs tools.
Endpoint tool names match API operation IDs with dots replaced by underscores:
| Tool name | API operation |
|---|---|
tiktok_profile_get | tiktok.profile.get |
instagram_post_get | instagram.post.get |
web_markdown_generate | web.markdown.generate |
auth_whoami | auth.whoami |
billing_balance_get | billing.balance.get |
Each endpoint tool's arguments mirror the matching API route parameters. See the API reference for the full endpoint catalog, argument schemas, response shapes, and pricing.
Two docs tools are also available:
| Tool name | Purpose |
|---|---|
docs_search | Search Social Fetch docs across API, SDK, auth, errors, credits, and integrations. |
docs_read | Read a full docs page as markdown by pathname, such as /docs/sdk. |
Recommended agent prompt:
Use the Social Fetch MCP docs to add TikTok profile lookup to this app with the TypeScript SDK.
In Cursor, MCP Inspector, or another MCP client, call tiktok_profile_get with:
{ "handle": "nike" }
The result contains the same data and meta envelope returned by the REST API. Check meta.creditsCharged and meta.requestId after metered calls.
| Symptom | What to check |
|---|---|
401 on every call | Reconnect the server and complete OAuth again. Your token may be missing or expired. |
| OAuth redirect loop | Finish signing in at Social Fetch, then approve access to return to your client. |
402 responses | Your account is out of credits for the metered route. Top up in Credits & billing. |
| No tools listed | Reconnect the server. If it persists, restart your MCP client. |
| Client only supports stdio | Use npx mcp-remote https://api.socialfetch.dev/mcp. |
server.json - MCP Registry metadata for the hosted remote server.examples/ - Copy-paste MCP client configuration snippets.assets/socialfetch-mark.svg - Local copy of the Social Fetch mark (also served at https://api.socialfetch.dev/mcp/icon.svg).The implementation lives in Social Fetch's private API service, not in this public listing repository.
MIT (c) Social Freak Ltd
com.mcparmory/google-sheets
domdomegg/google-sheets-mcp
henilcalagiya/google-sheets-mcp
cct15/war-dashboard-data
moooonad/mcp-google-sheets-full
io.github.br0ski777/csv-to-json