Skip to main content
Glama
Social Broadcast MCP

Social Broadcast MCP

Social Broadcast MCP

MCP server open source (MIT) for publishing to social media (Facebook, Instagram, YouTube) using the official APIs of each platform, with your own OAuth credentials.

No central service. No plans. No artificial limits. No payment middlemen.

Why does it exist?

SaaS tools (SocialCannon, PostFast, Buffer...) charge a monthly subscription and impose limits (accounts, posts, media uploads). This project does the same thing —posting from an AI agent (Hermes, Claude, etc.)— but each user connects their own accounts with their own developer apps. Free forever.

⚠️ Key difference vs SaaS: they already have apps approved by Meta/Google with full review. Here you create your own app (for free) and use it for your own accounts. That is valid for personal/own business use, and it avoids Meta App Review, which is only required for public access to third-party accounts.

Related MCP server: instagram-mcp

Platforms

Platform

Status

API

Media

Notes

Facebook

✅

Meta Graph API

image, video

Page or profile with pages_manage_posts

Instagram

✅

Meta Graph API

image, video, Reels, Stories

Requires a Business/Creator account linked to a FB page

YouTube

✅

Meta Graha API

video

Uploads with private/unlisted/public visibility

TikTok

🔜

API de Contenido Público de TikTok

video

Requires TikTok audit (2–6 weeks); pattern documented in docs/

X/Twitter

⚠️

API v2

image, video

X's free tier is very limited; documented in docs/

Installation

git clone https://github.com/tu-usuario/social-broadcast-mcp.git
cd social-broadcast-mcp
npm install
npm run build

Configuration in Hermes (or any MCP client)

# ~/.hermes/config.yaml (o config del perfil)
mcp_servers:
  social-broadcast:
    command: "node"
    args: ["/ruta/a/social-broadcast-mcp/dist/index.js"]

Or in any compatible MCP client:

{
  "mcpServers": {
    "social-broadcast": {
      "command": "node",
      "args": ["/ruta/a/social-broadcast-mcp/dist/index.js"]
    }
  }
}

Usage

1. Connect Facebook and Instagram

You need to create an app at developers.facebook.com (see docs/SETUP_META.md) and get:

  • App ID (clientId)

  • App Secret (clientSecret, only needed in development)

Then, from the agent:

connect_meta(clientId: "TU_APP_ID", clientSecret: "TU_APP_SECRET")

The browser opens → you authorize with your account → the accounts will be saved locally in the process.

2. Connect YouTube

Create a project in Google Cloud Console with the YouTube Data API v3 (see docs/SETUP_YOUTUBE.md):

connect_youtube(clientId: "TU_CLIENT_ID", clientSecret: "TU_CLIENT_SECRET")

3. See connected accounts

list_accounts()

4. Publish

publish_post(
  accountId: "fb:533433607139839",
  content: "🌀 CREA TU PROPIO GONG 🌀\nUn gong hecho por ti, para ti, como tú.",
  mediaUrls: ["https://tudominio.com/imagen.jpg"],
  platformOptions: { "mediaType": "REELS" }  // para Reels de IG
)

To schedule it instead of publishing right away, add scheduledAt: "2026-09-01T18:00:00+01:00".

Note about media: the API accepts public URLs. For local files, host them somewhere reachable (an S3/GCS bucket, your website, or an exposed local server) and use that URL. A direct-upload helper is on the roadmap.

Documentation

Security

  • Tokens are stored locally in ~/.social-broadcast-mcp/ with 0600 permissions.

  • They are never sent to any external server.

  • No reducing telemetry. No analytics. Nothing that calls home.

  • Check src/auth/store.ts to see exactly what gets stored.

License

MIT — free to use, copy, modify, and redistribute. Made for the community, out of the real experience of posting the Templo del Gong calendar (Vilagarcía de Ars) news.

Disclaimer

This project is not affiliated with Meta, Google, TikTok, or X Corp. The names belong to their respective owners. Use of the APIs is subject to each platform's terms of service.

Available Tools

6 tools
connect_metaA

Inicia el flujo OAuth para conectar Facebook e Instagram. Requiere clientId (y clientSecret opcional) de tu app en developers.facebook.com. Abre el navegador para autorizar.

Inputs: clientId (required), scopes, clientSecret.

connect_youtubeB

Inicia el flujo OAuth para conectar YouTube. Requiere clientId y clientSecret de tu proyecto en Google Cloud Console.

Inputs: clientId (required), clientSecret (required), scopes.

list_accountsB

Lista las cuentas de redes sociales conectadas

Inputs: platform.

list_platformsA

Lista las plataformas soportadas y sus capacidades

Inputs: no named parameters.

publish_postB

Publica o programa un post en una cuenta conectada

Inputs: content (required), accountId (required), mediaUrls, scheduledAt, +1 more.

refresh_accountsB

Refresca la lista de cuentas de una plataforma ya conectada

Inputs: platform (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.7/5.0

    Scored across 6 tools

    Disambiguation4/5

    The tool purposes are mostly distinct: platform listing, account listing, platform connection, refresh, and publishing are separate workflows. The only mild overlap is between list_accounts and refresh_accounts, but their descriptions make the difference understandable.

    Naming Consistency4/5

    All tool names are in snake_case and follow a verb_noun pattern, which is consistent. Minor deviation is that connect_meta and connect_youtube use platform/brand fragments rather than the generic verb_noun style, but the overall pattern remains clear.

    Tool Count5/5

    Six tools is well-scoped for a social broadcast server focused on connecting platforms and publishing posts. Every tool covers a meaningful action without unnecessary redundancy.

    Completeness4/5

    The core lifecycle is mostly covered: list platforms, connect accounts, list/refresh accounts, and publish or schedule posts. Missing disconnect functionality and scheduled-post management are noticeable gaps, but they do not block the primary broadcasting workflow.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      B
      quality
      B
      maintenance
      Enables reading, publishing, commenting on, and analyzing Instagram Business/Creator accounts through the official Graph API, with multi-account support and an optional self-hosted publishing panel.
      29
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables direct management of Facebook Pages and linked Instagram Business/Creator accounts through the official Meta Graph API, including posting, scheduling, reading and responding to comments, and viewing insights.
      20
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants and autonomous agents to connect to social media accounts and manage, generate, schedule, upload media for, and publish content across Facebook Pages, YouTube, TikTok, Instagram, and X, plus maintain a content pipeline.
      14
      MIT