Claude and ChatGPT can write a week of posts in a minute. Neither one can post them on its own. What closes that gap is an MCP server from a social media scheduler: you connect it once, and the assistant gets tools like "create post", "list scheduled posts" and "delete post".
I build one of these schedulers (Fuxux), so I'll use it for the exact steps, but the setup is the same for any scheduler with a remote MCP server. A table of the others is at the end.
What you need
- A scheduler account with your social accounts connected. The assistant can only post to accounts you've connected there. It never sees your Instagram or LinkedIn password.
-
The scheduler's MCP server, reached in one of two ways:
- A directory listing (Claude's connector directory, ChatGPT's plugin directory). You click Connect, sign in, done.
- The server URL, added by hand as a custom connector. Same result, a few more clicks.
Most schedulers now let you sign in (OAuth) instead of pasting an API key. Prefer that: nothing secret ends up in a chat or a config file, and you can revoke access from the scheduler's settings.
Claude (web, desktop and mobile)
From the directory:
- Open the scheduler's page in Claude's connector directory. For Fuxux that's
https://claude.ai/directory/fuxux. - Choose Connect. Claude opens the scheduler in your browser.
- Sign in, check what Claude will be able to do, and choose Allow access.
- Test with something read-only first: "list my connected accounts in Fuxux".
By hand: Settings → Connectors → add a custom connector, name it, paste the server URL (https://www.fuxux.com/api/mcp), then Connect and sign in.
The connection belongs to your Claude account, so it's there on web, desktop and mobile.
Claude Code
One command, then sign in from inside a session:
claude mcp add --transport http fuxux https://www.fuxux.com/api/mcp
Run /mcp in Claude Code, pick fuxux, authenticate, and your browser handles the sign-in. No key is stored anywhere.
ChatGPT
From the plugin directory: search for the scheduler under Plugins (or open its listing), choose Install plugin, then Connect. ChatGPT opens a new tab where you sign in and allow access. In a chat, mention it with @Fuxux (or whatever the plugin is called).
As a custom MCP server: Plugins → Add → Create custom MCP server, paste the URL, leave authentication on OAuth. Custom MCP servers need a paid ChatGPT plan; directory plugins don't.
Prompts that work well
- "Here's the outline of my talk. Turn it into a LinkedIn post and a shorter Threads version, and save both as drafts."
- "Plan three Facebook posts for our café's opening week and schedule them for 8:00 on Monday, Wednesday and Friday."
- "Show me my drafts and suggest which one to schedule first."
- "Check my dashboard: do any of my accounts need reconnecting?"
Things that trip people up
- It can publish, not just draft. Publishing is one of the tools. If you want to approve everything, say "always save posts as drafts" and review them in the scheduler's calendar.
- Images need public https links. The assistant passes URLs, not files from your desktop. Instagram won't take a post without an image or video.
- TikTok wants you to choose who can see each post. With Fuxux, the assistant asks you and posts directly once you've picked; if you don't, the post lands in your TikTok inbox and you finish it in the app. Other schedulers handle this differently, so check before you rely on it.
- Time zones. Say the time zone in the prompt ("8:00 Madrid time") or check the scheduled time before you leave the chat.
- Plan limits still apply. The assistant can't post more than your scheduler plan allows. On Fuxux's Free plan that's 3 connected accounts and 5 published posts a month, and X needs a paid plan.
Schedulers with a remote MCP server
From each vendor's own docs, checked 25 October 2026 (tool counts change, so check before you pick):
| Tool | MCP server URL | How it connects | Tools |
|---|---|---|---|
| Fuxux | https://www.fuxux.com/api/mcp | Sign-in (any plan) or API key (paid plans) | 9 |
| Buffer | https://mcp.buffer.com/mcp | Sign-in or personal API key | 20 |
| Metricool | https://ai.metricool.com/mcp | Sign-in or user token | 27 |
| Pallyy | https://app.pallyy.com/mcp | Sign-in or API key | 17 |
| Typefully | https://mcp.typefully.com/mcp | Sign-in (recommended) or API key | Not stated |
| Postiz | https://mcp.postiz.com/mcp | API key | 13 |
| Post Bridge | https://www.post-bridge.com/api/mcp/mcp | Sign-in or API key | 16 |
| Publer | https://mcp.publer.com | Sign-in or API-key URL | Not stated |
| Hootsuite | https://mcp.hootsuite.com/perch (publishing) | Workspace sign-in | Not stated |
More tools isn't automatically better: a scheduler with 27 tools can do more than post, but every tool description takes up room in the assistant's context. If you only want to draft and schedule, a small set is easier for the model to use correctly.
There's a longer comparison with prices and which ones are in each directory here: https://www.fuxux.com/blog/social-media-schedulers-for-chatgpt-and-claude?ref=devto
I build Fuxux. The steps above are the same for any scheduler on the list; swap in its URL.
Top comments (0)