Turn Claude, ChatGPT, OpenClaw, Hermes, or your own agent into a social publishing house. Compatible clients can use the hosted OAuth MCP connector; local MCP, the private GPT Action, and REST remain available alternatives. Inspect each destination’s result. If an outcome is unclear, check the receipt and destination before retrying.
OpenClaw
☤Hermes
Any MCP client
Autonomous agents act on their own. Handing one raw platform tokens lets a bad instruction expose those credentials. Social Fanout keeps platform credentials server-side and gives agents a separate, authenticated publishing surface.
Platform tokens stay server-side and refresh only where the provider supports it. Hosted connector clients use per-user OAuth without receiving your Social Fanout API key. REST, local MCP, and private GPT Actions use an API key that must stay private because it authorizes publishing.
Created jobs retain their status and provider receipts when available. Inspect uncertain outcomes before retrying. Revoke a hosted client in Dashboard → Authorized assistants, or delete the API key to block future calls. This does not remove posts already published.
Per-key platform and monthly publish limits bound usage. Review the exact content and accounts before publishing; limits do not replace approval.
Connect a compatible client to the hosted OAuth MCP endpoint, point a local client at the stdio MCP package, have an agent call REST, or import the private GPT Action where Actions are available. The hosted connector binds one existing Social Fanout key without exposing it to the client; the alternative paths use customer-managed API keys.
Connect an eligible social account, let your agent inspect its publishing capabilities, then review the content before asking it to publish. Social Fanout handles delivery; you keep control of what is sent.
For Claude Desktop, use the local MCP setup guide. Compatible remote clients can use the hosted OAuth MCP connector. Hosted publishing requires an exact dry run and confirmation token before the live request. Client setup and directory availability vary; this is not a claim of an official Claude or ChatGPT listing.
Building social posting into your own app? The social publishing REST API accepts multiple targets in one request and returns a result for each. The local MCP publish tool sends to one destination per call. Inspect each result before retrying so a partial failure does not create duplicate posts.
Claude Desktop extension 0.1.6 for macOS and Windows: open the file,
paste your API key into the masked field, then ask Claude to list
your connections. It runs locally, not as a claude.ai web or mobile
connector. SHA-256 86170f0517d16f4a15ae5370d79a79519abc0376c8cc1f7e4fcf7f07ac4e7d77
# Claude Code: add the local MCP server with your key claude mcp add --env FANOUT_API_KEY=your-fanout-api-key \ --transport stdio socialfanout \ -- npx -y --package=https://socialfanout.com/downloads/socialfanout-mcp-0.1.6.tgz socialfanout-mcp # Cursor or manual Claude Desktop setup: socialfanout.com/quickstart # → your agent gets fanout_publish_post + health, # providers, connections, publishing_capabilities & start_oauth.
Hosted connector endpoint: https://socialfanout.com/mcp.
Directory availability remains subject to OpenAI and Anthropic review.
As a separate private-GPT alternative, import
the hosted Action schema.
It calls the REST API directly. The local MCP package remains available
for clients that launch a stdio server on your machine.
Embed Social Fanout inside your app or agent and offer it to your own users. Arrange source access to run it on your own infrastructure, or embed our hosted service, under a lightweight written agreement.
Start a 7-day trial with no card, point your agent at the MCP server, and choose from the connected destinations currently available to that account.