X

Provides an MCP server to interact with the X platform using MCP clients, handling authentication and rate-limited API access.

typescript

GitHub Stars

typescript

Language

6 months ago

First Indexed

2 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "siddheshutd-x-mcp-server": {
      "command": "node",
      "args": [
        "/ABSOLUTE/PATH/TO/PARENT/FOLDER/x-mcp-server/build/index.js"
      ],
      "env": {
        "X_API_KEY": "YOUR_API_KEY",
        "X_ACCESS_TOKEN": "YOUR_ACCESS_TOKEN",
        "X_API_KEY_SECRET": "YOUR_API_KEY_SECRET",
        "X_ACCESS_TOKEN_SECRET": "YOUR_ACCESS_TOKEN_SECRET"
      }
    }
  }
}

You run an MCP server that lets MCP clients on the X platform talk to the X ecosystem, enabling you to send queries and receive responses through clients like Claude, Cursor AI, Windsurf AI, and others. This server handles authentication and rate-limited API access so your clients can work with X data and actions seamlessly.

How to use

Connect your MCP client to the X MCP Server to start interacting with the X platform. You will configure your client to point to the local MCP server (the one you run on your machine) and provide the required API credentials. Once connected, you can issue requests through your MCP client as if you were directly using the X APIs, while the server handles authentication, request routing, and rate limit considerations.

How to install

Prerequisites: Node.js version 18 or higher, npm version 8 or higher, and your X Developer API keys.

Step 1: Clone the project and install dependencies.

git clone <repository-url>
cd x-mcp-server
npm install

Step 2: Build the project to generate the runtime bundle.

npm run build

Additional configuration and usage notes

You will run the MCP server locally and connect MCP clients by supplying environment variables that hold your X API credentials. The server is designed to run as a local stdio process that your MCP clients start and manage.

Two example MCP client configurations are shown below. They assume you will replace the placeholder paths with your actual project path where the server runtime is built.

{
  "x-mcp-server": {
    "command": "node",
    "args": [
      "/ABSOLUTE/PATH/TO/PARENT/FOLDER/x-mcp-server/build/index.js"
    ],
    "env": {
      "X_API_KEY": "your-x-api-key",
      "X_API_KEY_SECRET": "your-x-api-key-secret",
      "X_ACCESS_TOKEN": "your-x-access-token",
      "X_ACCESS_TOKEN_SECRET": "your-x-access-token-secret"
    }
  }
}

For Windsurf AI, you would configure a similar stdio entry within its MCP configuration file, using the same runtime path and environment variables.

{
  "mcpServers": {
    "x-mcp-server": {
      "command": "node",
      "args": [
        "/ABSOLUTE/PATH/TO/PARENT/FOLDER/x-mcp-server/build/index.js"
      ],
      "env": {
        "X_API_KEY": "your-x-api-key",
        "X_API_KEY_SECRET": "your-x-api-key-secret",
        "X_ACCESS_TOKEN": "your-x-access-token",
        "X_ACCESS_TOKEN_SECRET": "your-x-access-token-secret"
      }
    }
  }
}

Built by

VeilStrat

AI signals for GTM teams