Labsco
MCP SERVER

X (Twitter)

by vidhupv

Draft, thread and publish to X from a Claude conversation.

Social Media Accounts & Posting
Summary
Drafts first, publishing on purpose.

The thing that makes this safe to leave connected is that writing and posting are separate steps — the model can compose a whole thread and nothing goes out until you tell it to publish.

What it is

A small local MCP server that creates, manages and publishes X posts through chat. Drafts live on your side until you say to publish, so composing and posting are two separate decisions.

What you get
  • Posts written from the conversation, single or as a thread on one topic
  • Drafts kept rather than posted — list them, publish the one you meant, delete the ones you did not
  • Installation either through Smithery in one command, or by cloning and pointing the client at the directory
Requirements

`uv` installed globally, and four X credentials in the client config: `TWITTER_API_KEY`, `TWITTER_API_SECRET`, `TWITTER_ACCESS_TOKEN`, `TWITTER_ACCESS_TOKEN_SECRET`. Create a project in the X developer portal, set User Authentication to Read and Write with the Web App type, callback `http://localhost/`, then generate the keys and tokens.

Setup effort

One command plus a key — npx -y @smithery/cli install x-mcp --client claude, then supply credentials