Connect Cursor to fanout over MCP and its agent can check your connected accounts, draft a post and schedule it across any of the 16 networks fanout supports. Connection is OAuth: no API key to copy or paste for a normal setup. Publishing and other mutating actions ask for your approval before they run.
{
"mcpServers": {
"fanout": { "url": "https://www.tryfanout.com/api/mcp" }
}
}list_connections | Connected accounts, their networks and handles |
list_posts | Post history with per-network success or failure |
list_scheduled_posts | The scheduled queue |
create_post | Publish now, or schedule with scheduledAt (RFC3339 with timezone) |
update_scheduled_post | Replace text, per-network variants and time of a scheduled post |
cancel_scheduled_post | Cancel a queued post; already-published posts are untouched |
prepare_media_upload | Upload URL for images and video (client PUTs the bytes) |
get_analytics | Analytics for 1–366 days, where the network supports it |
3-day trial, card required, cancel anytime.
Yes. Once connected, Cursor's agent can call fanout's create_post tool to publish now or schedule a post for later, across any network you've connected.
Not for the normal setup — Cursor discovers OAuth from the server and opens fanout to sign in and click Allow access. A developer key is available as an alternative for headless setups.
Any of the 16 networks fanout supports, depending on which accounts you've connected — X, LinkedIn, Instagram, TikTok, YouTube, Threads, Bluesky, Telegram and more.
Claude · ChatGPT · Claude Code · OpenClaw · MCP overview
X (Twitter) scheduler · LinkedIn scheduler · Instagram scheduler · TikTok scheduler · YouTube scheduler · Threads scheduler · Bluesky scheduler · Telegram scheduler · Facebook scheduler · Pinterest scheduler · Reddit scheduler · Discord scheduler · WhatsApp scheduler · Snapchat scheduler · Google Business Profile scheduler · Slack scheduler