ReachSocial

dev.reachsocialPublished by reachsocial.devOfficial publisherv0.3.1Updated Oct 29, 2026

Instagram, X, TikTok, YouTube, Facebook and Reddit data. Approved OAuth or API-key access required.

VerifiedStreamable HTTPWeb executableWeb Search & Scraping

Overview

AI-generated overview

Remote MCP endpoint giving an assistant access to social media data from Instagram, X, TikTok, YouTube, Facebook and Reddit.

What you can do
  • Retrieve social media data across Instagram, X, TikTok, YouTube, Facebook and Reddit.
  • No individual tools are documented in the manifest, so the exact operations are not specified.
  • Access is gated behind an approved ReachSocial API key or OAuth authorization.
When to use it
Worth considering when you need an assistant to work with social platform data from several networks through one hosted endpoint, and you already have or can obtain approved ReachSocial access.
Requirements
A remote streamable HTTP endpoint at reachsocial.dev; no local package or runtime. An approved ReachSocial API key sent as an Authorization header in the form Bearer plus the key, or OAuth authorization, which is described as an owner-only pilot. Access must be requested from the provider before use.
Before you install
The Authorization header carries a secret API key; keep it private and avoid exposing it in logs or shared configurations. Access is approval-based and OAuth is limited to an owner-only pilot, so availability may be restricted. Social platform data is fetched through a third-party service, so queries and results pass through the provider.

Installation

In SourceWeft

  1. Open ReachSocial in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/dev.reachsocial%2Fsocial-data/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "reachsocial": {
      "type": "http",
      "url": "https://reachsocial.dev/mcp/"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.3.1LatestOct 29, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.