Mcp Social

io.github.infoinlet-marketplacePublished by GitHub account infoinlet-marketplacev0.1.1Updated Oct 24, 2026

Multi-platform social posting for AI agents (Postiz) — channels, schedule/publish posts.

VerifiedSTDIODesktop onlyCommunication & Collaboration

Overview

AI-generated overview

A local MCP server that lets an AI assistant manage multi-platform social posting through Postiz, including channels and scheduled or published posts.

What you can do
Manage social channels connected through Postiz, so the assistant can see where posts can go. Create and schedule posts, or publish them across multiple social platforms. The manifest lists no individual tools, so the exact operations are not documented here.
When to use it
Useful when you want an assistant to draft, schedule or publish social media posts across several platforms from one place, rather than working inside each platform's own interface.
Requirements
Runs as a local process on the user's machine, installed from the npm package @infoinlet/mcp-social over stdio. Desktop only; no web execution. The manifest declares no authentication, environment variables or headers, but a working Postiz account or connection is implied by the description and is not documented.
Before you install
The server is described as publishing and scheduling posts, which changes public content on connected social accounts; review drafts before anything is sent. No credentials are declared in the manifest, but the Postiz connection it relies on is undocumented, so check what access it needs. No tool list or README is available to confirm behavior.

Installation

In SourceWeft

  1. Open Mcp Social in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.1LatestSep 16, 2026

Score

25% 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 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

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