OmniSocials

io.github.OmniSocialsPublished by GitHub account OmniSocialsv1.56.0Updated Nov 11, 2026

Schedule and publish posts on 13 social networks, answer comments and DMs, and read analytics.

The publisher's own server: Socials Homes

VerifiedStreamable HTTPWeb executableCommunication & CollaborationBusiness & Commerce

Overview

AI-generated overview

OmniSocials is a remote MCP server that lets an assistant schedule and publish social posts, reply to comments and DMs, and read analytics across 13 networks.

What you can do
  • Schedule and publish posts across 13 social networks
  • Answer comments and direct messages
  • Read social media analytics
When to use it
Useful when you want an assistant to run social media work from one place: planning and publishing posts, keeping up with replies to comments and DMs, and checking performance numbers without switching between network dashboards.
Requirements
A remote MCP endpoint reached over streamable HTTP; OAuth sign-in is required. No environment variables or headers are declared.
Before you install
The assistant can publish posts and send replies publicly, and read account analytics, so review actions before they go out. Access is granted through OAuth to your social accounts; the server is hosted by a third party, so content and account data pass through it.

Installation

In SourceWeft

  1. Open OmniSocials 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.OmniSocials%2Fmcp-server/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": {
    "omnisocials": {
      "type": "http",
      "url": "https://mcp.omnisocials.com/"
    }
  }
}

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. v1.56.0LatestNov 11, 2026

Score

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

Other Socials integrations