DataWhisker X MCP Server

About

DataWhisker’s X MCP Server connects AI assistants to X API workflows such as reading timeline content and creating posts.

Key Features

• Bring supported X reading and posting tools into an assistant.
• Use a TypeScript integration with the configured X account.

Use Cases

Retrieve X data in an agent workflow using the selected provider and credentials.

Limitations

X API permissions and pricing can change. Check the provider’s current access requirements rather than relying on old pricing tables in the repository.

Sources

• Project documentation: https://github.com/DataWhisker/x-mcp-server

MCP Setup

Prerequisites

• Node.js 18+ and npm.

Access requirements

• X developer account and credentials authorized for the requested operations.

Client setup

Claude Desktop

Transport: stdio

{
  "mcpServers": {
    "x": {
      "command": "node",
      "args": [
        "/absolute/path/to/x-mcp-server/build/index.js"
      ],
      "env": {
        "TWITTER_API_KEY": "YOUR_API_KEY",
        "TWITTER_API_SECRET": "YOUR_API_SECRET",
        "TWITTER_ACCESS_TOKEN": "YOUR_ACCESS_TOKEN",
        "TWITTER_ACCESS_SECRET": "YOUR_ACCESS_SECRET"
      }
    }
  }
}

• Clone https://github.com/DataWhisker/x-mcp-server.git
• Run npm install and npm run build.
• Configure the X app and OAuth 1.0a user credentials, then replace the executable path.

The README also documents an OAuth 2.0 token for operations needing that authorization path.

Environment variables

• TWITTER_API_KEY
• TWITTER_API_SECRET
• TWITTER_ACCESS_TOKEN
• TWITTER_ACCESS_SECRET
• TWITTER_OAUTH2_ACCESS_TOKEN (operation-dependent)

Setup docs: https://github.com/DataWhisker/x-mcp-server