Social Media MCP Server

io.github.connected-pathsPublished by GitHub account connected-pathsv0.1.0Updated Oct 24, 2026

Publish to Bluesky, Threads, LinkedIn, Facebook Pages, and Instagram from ChatGPT or Claude.

VerifiedStreamable HTTPWeb executableCommunication & Collaboration

Overview

AI-generated overview

Remote MCP server that lets an assistant publish posts to Bluesky, Threads, LinkedIn, Facebook Pages and Instagram.

What you can do
  • Publish content to connected social accounts across Bluesky, Threads, LinkedIn, Facebook Pages and Instagram.
  • The listing names no individual tools, so the exact operations (posting, scheduling, media handling) are not documented here.
  • Access is through a hosted endpoint rather than a local package.
When to use it
Useful when you want an assistant to draft and publish social media posts to several networks from one conversation, instead of switching between each platform's own composer.
Requirements
A remote MCP endpoint at social-mcp.connectedpaths.com over streamable HTTP. OAuth authentication is required, so the user must sign in and authorize the connection; no environment variables or headers are declared.
Before you install
The server publishes content publicly to real social accounts, so review drafts before sending. OAuth grants it access to the connected accounts, and the content you submit passes through a third-party hosted service. No tool list or documentation is provided, so the exact scope of what it can do is unclear.

Installation

In SourceWeft

  1. Open Social Media MCP Server 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/io.github.connected-paths%2Fmcp-social/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": {
    "social-media": {
      "type": "http",
      "url": "https://social-mcp.connectedpaths.com/mcp"
    }
  }
}

README

This repository has no README.

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.1.0LatestSep 16, 2026

Score

60% 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.

  • License10 pts

    Declare a license in the repository or the registry entry.