Twitter MCP Server

MCP (Model Context Protocol) server to interact with Twitter/X directly from any MCP-compatible AI assistant (like opencode). Uses your Twitter session cookies for authentication — no API keys needed.

Features

• Post, delete, like, and retweet tweets

• Search tweets by keyword

• View home timeline, user timeline, and tweet details

• Get current trending topics

• Look up user profiles

• Follow/unfollow users

• Authenticated user profile info

Related MCP server: Twitter/X MCP Server

Quick Start

1. Get your Twitter cookies

1. Open Twitter/X in your browser (logged in)

2. Open DevTools (F12) → Application → Cookies → https://x.com

3. Copy the values for auth_token and ct0

2. Configure

cp .env.example .env

Edit .env:

TWITTER_AUTH_TOKEN=seu_auth_token_aqui
TWITTER_CT0=seu_ct0_aqui

3. Install dependencies

pip install -r requirements.txt

4. Run

python server.py

The server will start and listen on stdio, ready for MCP connections.

Register with opencode

Add to ~/.config/opencode/opencode.jsonc:

{
  "mcpServers": {
    "twitter": {
      "command": "python3",
      "args": ["/path/to/twitter-mcp/server.py"],
      "env": {
        "TWITTER_AUTH_TOKEN": "seu_token",
        "TWITTER_CT0": "seu_ct0"
      }
    }
  }
}

Register with Claude Desktop

Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

{
  "mcpServers": {
    "twitter": {
      "command": "python3",
      "args": ["/caminho/para/twitter-mcp/server.py"],
      "env": {
        "TWITTER_AUTH_TOKEN": "seu_token",
        "TWITTER_CT0": "seu_ct0"
      }
    }
  }
}

Register with Codex (by Cursor)

Create/edit ~/.codex/config.json:

{
  "mcpServers": {
    "twitter": {
      "command": "python3",
      "args": ["/caminho/para/twitter-mcp/server.py"],
      "env": {
        "TWITTER_AUTH_TOKEN": "seu_token",
        "TWITTER_CT0": "seu_ct0"
      }
    }
  }
}

Tools

How it works

The server authenticates via auth_token and ct0 session cookies, then makes requests directly to the Twitter/X internal GraphQL API. Query IDs are extracted from the official Twitter web client bundle, so no API keys or OAuth are needed.

Tests

python -m pytest test_twitter.py -v

CI

On every push to main, GitHub Actions runs all tests and automatically creates a tag (v1.YYYYMMDD.HHMM).

Project structure

├── server.py           # MCP server entry point (12 tools via FastMCP)
├── twitter_client.py   # HTTP client for Twitter GraphQL API
├── auth.py             # Authentication via session cookies
├── test_twitter.py     # Tests (16 tests, mocked API)
├── requirements.txt    # Python dependencies
├── .env.example        # Cookie config template
├── .github/workflows/  # CI pipeline
└── README.md