Social-media MCP server
A fixed set of posting and scheduling tools for an agent.
What it is
MCP, the Model Context Protocol, is how an agent such as Claude Code gets new tools. This server gives an agent a fixed list of social-media actions instead of open access to an account. Every input is checked against a Zod schema, and each post is checked against the platform's character limit before anything is sent.
By the numbers
What it means for your team
An MCP server is how a team gives its agent a short, specific list of actions, such as drafting and scheduling posts, instead of the keys to an account. With an approval step on top, a person still decides what gets published.
Status
Only X posting works; the Bluesky and Threads options return “not yet implemented”. It was used for under two weeks, and of 18 scheduled posts, 1 went out and 6 failed. Claude Code's entry for it still points at the folder it lived in before a move, so no agent has it connected today; the fix is one path.
Posting
A post or a thread goes to X through xurl, X's official command-line client for its v2 API. A thread is posted as a chain of replies, and a post can be deleted by its ID.
Limits before sending
The schemas cap a post at 500 characters and a thread at 25 posts, and each platform's own limit, 280 characters on X, is checked before any call.
Drafts and schedule
Drafts and scheduled posts are saved as JSON files. A separate script publishes the scheduled posts that are due and records whether each one went out.
Checked on 2026-10-08
The server started from its folder and listed all 12 of its tools over MCP. Nothing was posted.