For AI agents & developers

Social media publishing
automation for AI agents.

Turn Claude, ChatGPT, OpenClaw, Hermes, or your own agent into a social publishing house. Claude can use local MCP, a custom GPT can import the Social Fanout Action where Actions are available, and other agents can use REST. Inspect each destination’s result. If an outcome is unclear, check the receipt and destination before retrying.

Start for $0 Choose your setup
Free tier MCP + REST + GPT Action No raw tokens Self-hostable
your-agent · social-fanout (mcp)
agent> publish "shipped v2 🚀" to x, bluesky, discord
→ social-fanout · fanning out…
3 published · 0 raw tokens touched · logged
Plugs into the agent you already run
Claude ChatGPT Actions Cursor VS Code OpenClaw ☤Hermes Any MCP client
Claude through local MCP · ChatGPT through an imported Action where available · OpenClaw, Hermes, and other agents through REST or a compatible local MCP workflow.
One call out → 12 types exposed · live status varies
Instagram X / Twitter LinkedIn members YouTube · limited Facebook Bluesky Threads Reddit Discord Email TikTok Pinterest · limited
Pass a targets array — up to 20 in one call — and get a per-target result back. here's what's live today. LinkedIn member publishing is available for eligible connected profiles, with periodic reconnect when LinkedIn does not issue refresh access. LinkedIn Page publishing works for Pages administered by the connected member under Development Tier, and refreshable Page connections renew on publish; Standard Tier review is pending for unrestricted customer Page access. LinkedIn uses the dashboard, REST API, or local MCP; the current ChatGPT Action excludes it. Pinterest Standard access is active, and production OAuth/public-Board lookup are verified. Publishing verification remains pending.
The agent problem
Your agent shouldn't be holding your X password.

Autonomous agents act on their own. Handing one raw platform tokens lets a bad instruction expose those credentials. Social Fanout keeps platform credentials behind its own API key.

🔑

No raw credentials

Your agent gets one Social Fanout key. Platform tokens stay server-side and refresh only where the provider supports it. The publishing agent uses the Social Fanout key, which must also stay private because it authorizes publishing.

🧾

Requests are logged; API keys can be deleted

Created jobs retain their status and provider receipts when available. Inspect uncertain outcomes before retrying. Delete the Social Fanout API key to block future calls. This does not remove posts already published.

🚦

Scoped & rate-limited

Per-key platform and monthly publish limits bound usage. Review the exact content and accounts before publishing; limits do not replace approval.

Wire it in
One publishing service. Use it from the agent you already run.

Point Claude or another compatible client at the local MCP server, have an agent call REST, or import the GPT Action into ChatGPT where Actions are available. Same Social Fanout key and per-destination results either way.

mcp setup 
# point the local MCP server at your key, then run it
FANOUT_API_BASE_URL=https://socialfanout.com \
FANOUT_API_KEY=spk_live_… \
  npm --silent run mcp
# → your agent gets fanout_publish_post + health,
#   providers, connections, publishing_capabilities & start_oauth.

ChatGPT setup: import the hosted Action schema. It calls REST and is not a hosted remote MCP endpoint.

Building an agent product?
Ship publishing as a feature of your own agent.

Embed Social Fanout inside your app or agent and offer it to your own users. Arrange self-hosted source access, or embed our hosted service, under a lightweight written agreement.

Talk about embedding

Give your agent a voice —
not your passwords.

Create a free account, point your agent at the MCP server, and choose from the connected destinations currently available to that account.

Start for $0 Read the docs