Provides an MCP server that integrates X API to read timelines, post, and manage tweets with built-in rate limiting.
Configuration
View docs{
"mcpServers": {
"datawhisker-x-mcp-server": {
"command": "node",
"args": [
"%USERPROFILE%/Projects/MCP Basket/x-server/build/index.js"
],
"env": {
"TWITTER_API_KEY": "paste-your-api-key-here",
"TWITTER_API_SECRET": "paste-your-api-key-secret-here",
"TWITTER_ACCESS_TOKEN": "paste-your-access-token-here",
"TWITTER_ACCESS_SECRET": "paste-your-access-token-secret-here"
}
}
}
}You run an MCP server that connects to X (Twitter) to read your home timeline, post tweets, reply with optional images, and manage your tweets, all with built-in rate limiting and TypeScript safety. This server lets you compose and automate Twitter actions from an MCP client while handling credentials securely.
Once the server is running, you can perform common Twitter actions from your MCP client. Get your home timeline to read recent tweets, create new tweets with optional images, reply to existing tweets with optional images, and delete tweets. The server handles rate limits on the free X API tier and provides a straightforward workflow for posting and reading content.
Prerequisites: Node.js v16 or higher and a Claude desktop installation that will host the MCP server.
Clone the project, install dependencies, and build the server with these commands.
Configuration details, security considerations, examples, and troubleshooting are provided below to help you set up and operate your MCP server smoothly.
Retrieve tweets from your home timeline with an optional limit (default 20, max 100).
Post a new tweet with optional image attachment. Supports text content and image_path pointing to PNG, JPEG, GIF, or WEBP.
Post a reply to a specific tweet with optional image attachment. Requires the target tweet_id and text content.
Delete a tweet by its tweet_id.