x-post

X-Post MCP provides a server exposing a tool to post content directly to X (formerly Twitter) via the Model Context Protocol (MCP). The server uses Express and SSE to handle MCP tool calls, delegating AI-driven post creation to Google's Gemini models and then publishing the result to X through the official API. To interact with it, run the server and use the accompanying client to generate posts. The client connects to the MCP server, passes user prompts to Gemini for post generation, and calls the createPost tool exposed by the server to publish the content to X. This setup makes it easy to integrate automated content generation into AI workflows while ensuring posts adhere to X’s rules and length constraints.

Typical usage flow:

• Start the MCP server (bun run dev) in the server directory.
• Launch the client (bun run index.ts) to open an interactive chat interface.
• Ask the AI to draft a post; Gemini generates the content, and the MCP tool posts it to X upon confirmation.
• Use the tool to manage post length, truncation, and formatting as needed. The server handles compression to fit within X’s character limit and can be extended with additional MCP tools if required.

Prerequisites:

• Bun v1.2.5 or later installed on your machine
• X (Twitter) API credentials (API Key, API Secret, Access Token, Access Token Secret)
• Google Gemini API key

Installation steps:

1. Clone the repository:

git clone https://github.com/subhadeeproy3902/x-post-mcp.git
cd x-post-mcp

2. Install server dependencies (uses Bun):

cd server
bun install

3. Install client dependencies (optional for local testing):

cd client
bun install

4. Create environment configuration files:

• Server: create server/.env with your X API credentials (TWITTER_API_KEY, TWITTER_API_SECRET, TWITTER_ACCESS_TOKEN, TWITTER_ACCESS_SECRET)
• Client: create client/.env with GEMINI_API_KEY

5. Run the server in development mode:

cd server
bun run dev

6. In another terminal, start the client (optional for interactive testing):

cd client
bun run index.ts

Notes:

• Ensure your API keys are kept secret and not committed to version control.
• The server exposes a MCP tool named createPost to publish posts to X.
• You may adjust environment variables or configuration as needed for production deployments.

Tips and common issues:

• If you encounter authentication errors with the X API, double-check that your app permissions include Read, Write, and Direct Messages and that the tokens are correctly set.
• The Gemini API key should be kept secure; restrict it to necessary services and avoid exposing it in client-side code.
• Ensure the Bun runtime version matches the project’s prerequisites (v1.2.5+).
• When deploying, consider using a process manager and environment variable injection for secure credential management.
• If the MCP tool cannot post, check server logs for rate limits or invalid post content; ensure messages comply with X’s policies.