Social Fanout

io.github.Muse-NexusPublished by GitHub account Muse-Nexusv0.1.7Updated Nov 7, 2026

Focused tools for AI agents to publish, schedule, and review posts through the Social Fanout API.

VerifiedSTDIODesktop onlyProductivity & WorkflowCommunication & Collaboration

Overview

AI-generated overview

Local MCP server that lets an assistant publish, schedule, cancel and review social media posts through the Social Fanout API.

What you can do
  • Publish or schedule posts through an existing Social Fanout connection, with a dry-run check first
  • Review recent posts by status and read a single publish job's durable status and provider receipt
  • Cancel a future scheduled job before it is claimed
  • List configured providers, account connections, publishing capabilities and first-comment capability
  • Check API health and create a first-party OAuth connection URL
When to use it
Useful when you want an assistant to draft and send or schedule social posts across connected accounts, and to check what happened to a post afterwards, without leaving the chat. Also handy for inspecting which connections and formats are available before composing content.
Requirements
Runs locally over stdio, typically via the npm package socialfanout-mcp, so Node.js is needed. Requires a Social Fanout API key in FANOUT_API_KEY (spk_ prefix), obtainable from a free signup. An optional FANOUT_API_BASE_URL overrides the default API instance. Desktop only; network access to the Social Fanout API is required.
Before you install
The API key in FANOUT_API_KEY authorizes publishing to connected social accounts, so treat it as a secret. Publishing and scheduling send real content to third-party social providers and consume publish quota; the server asks for a dry run and explicit user approval of exact content first. Cancelling a scheduled job is a write action and should be confirmed. Post content and account data are sent to the Social Fanout API.

Installation

In SourceWeft

  1. Open Social Fanout 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

11

fanout_first_comment_capability

Read automatic first-comment availability

Read availability and exact owned Facebook Page/Comments connection pairs. This is read-only and does not activate the feature or publish.

Takes no parameters.

fanout_first_comment_status

Read original first-comment command status

Read independent parent, comment and accounting status using exactly one jobId or original requestKey. After uncertainty use the ORIGINAL requestKey; this never reposts or creates an intent. Unavailable while the feature is OFF.

ParametersjobIdrequestKey

fanout_health

Check API health

Check Social Fanout API health.

Takes no parameters.

fanout_list_providers

List providers

List configured Social Fanout providers and their capabilities.

Takes no parameters.

fanout_list_connections

List connected accounts

List social account connections available to the configured Social Fanout API key.

Takes no parameters.

fanout_publishing_capabilities

Read publishing capabilities

Read implemented formats, media limits, required fields, scheduling and receipt behavior for each owned connection before preparing a post. Includes separate configured-provider readiness, stored connection health and strict support. Makes no provider requests and does not verify live permissions or native visibility.

Takes no parameters.

fanout_list_posts

List recent posts

Review recent published, scheduled, queued, failed, action-required, and canceled Social Fanout posts for the configured API key.

Parameterslimit

fanout_get_job

Get job status

Read the current durable status and provider receipt for one Social Fanout publish job.

ParametersjobIdrequired

fanout_cancel_job

Cancel scheduled post

Cancel a future scheduled Social Fanout job before the worker claims it, so the post does not go out. Confirm with the user first. The canceled audit receipt remains durable.

ParametersjobIdrequired

fanout_start_oauth

Start account connection

Create a first-party connection URL. The API key owner must sign in to SocialFanout and confirm the destination key before authorizing the provider. The URL contains no API key or PKCE verifier.

ParametersproviderrequiredreturnTo

fanout_publish_post

Publish or schedule post

Publish now or schedule a post through an existing Social Fanout connection. Always call with dryRun=true first: it checks routing and entitlements without calling the social provider or using publish quota. Then publish live (dryRun omitted or false) only after the user approves the exact content, destination and schedule. Pinterest is immediate-only. Local stdio accepts an optional requestKey: retain the same key and unchanged live arguments across retries/reconnects; never replace it after uncertainty. Use distinct validation-only and approved-live keys. Without a key, legacy requests have no caller-key retry protection. This is not an exactly-once guarantee.

ParameterslinktextrequireddryRunpageIdsubjectplatformrequiredaccountIdrequiredallowDuetmediaUrlsrequestKeyallowStitchpublishMode+7 more

Version history

3
  1. v0.1.7LatestNov 4, 2026
  2. v0.1.6Oct 13, 2026
  3. v0.1.1Sep 16, 2026

Score

65% 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
  • 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 listedRequired15 pts
  • 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.