Social Fetch MCP

What Is This?

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:

• "Find this TikTok creator and add their latest videos to my app."

• "Pull the transcript for this YouTube video and summarize the sponsorships."

• "Fetch this Instagram post, inspect the response shape, and wire it into my backend."

• "Read the Social Fetch docs and choose the right endpoint for Reddit search."

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.

Related MCP server: riocloud-reader

Why Use It?

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.

• Less setup: call Social Fetch tools directly from your agent.

• Better answers: the agent can search and read the live docs before choosing an endpoint.

• Real data in the loop: test with TikTok, Instagram, YouTube, X/Twitter, Reddit, Spotify, web, and more from inside your editor.

• No API keys in editor config: sign in once with OAuth.

• Same API everywhere: MCP tools map to the public REST API, SDK, and docs.

What You Can Fetch

Social Fetch MCP exposes endpoint tools for:

• TikTok, Instagram, YouTube, X/Twitter, Telegram, Facebook, Threads, LinkedIn, Reddit, and Spotify data.

• Profiles, posts, videos, comments, transcripts, search results, and platform-specific metadata.

• Web markdown generation and AI-assisted web page questions.

• Account identity and credit balance.

• Social Fetch docs through 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.

Requirements

• A Social Fetch account.

• Credits for metered API routes.

• An MCP client with remote Streamable HTTP support and OAuth, such as Cursor, VS Code, Claude Code, Claude Desktop, or MCP Inspector.

One-Click Install

• Install in Cursor

• Install in VS Code

• Install in Windsurf

• Open the hosted install page

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.

Manual Setup

Cursor

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.

VS Code

Add this to settings.json:

{
  "mcp": {
    "servers": {
      "socialfetch": {
        "url": "https://api.socialfetch.dev/mcp"
      }
    }
  }
}

Claude Code

claude mcp add --transport http socialfetch https://api.socialfetch.dev/mcp

Then run /mcp and authenticate Social Fetch to finish the OAuth flow.

Claude Desktop

Add a custom remote MCP connector with this URL:

https://api.socialfetch.dev/mcp

Authorize Social Fetch when Claude prompts you.

stdio-only Clients

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.

Authentication

Social Fetch MCP uses OAuth 2.1. Your MCP client handles the flow:

1. The client opens Social Fetch sign-in in your browser.

2. You sign in or create an account and approve access.

3. The client receives an access token and sends it with each MCP request.

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

tools/list exposes endpoint tools plus docs tools.

Endpoint tool names match API operation IDs with dots replaced by underscores:

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:

Recommended agent prompt:

Use the Social Fetch MCP docs to add TikTok profile lookup to this app with the TypeScript SDK.

Example: TikTok Profile

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.

Troubleshooting

Repository Contents

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

Related

• Social Fetch MCP docs

• Social Fetch API reference

• TypeScript SDK

• n8n community node

License

MIT (c) Social Freak Ltd