Twitter MCP

Prerequisites

• Node.js 18 or higher
• npm or npx
• Twitter Developer Account with API credentials
• Claude Desktop App

Remove old dependencies

rm -rf node_modules package-lock.json

Installation

Step 1: Run the installer

Start the setup flow with:

npx @muhammadsiddiq/twitter-mcp

The installer guides you through every question and writes the correct MCP config for the client you choose.

Step 5: Finish setup

After the questions are answered, the installer writes the config automatically and tells you to restart the selected client.

Local Development Setup

1. Clone the repository:

git clone https://github.com/genaiwithms/twitter-mcp.git
cd twitter-mcp

2. Install dependencies:

npm install

3. Build the project:

npm run build

1. Set up environment:

Create a .env file in the project root:

API_KEY=your_api_key
API_SECRET_KEY=your_api_secret
ACCESS_TOKEN=your_access_token
ACCESS_TOKEN_SECRET=your_access_token_secret

1. Run locally:

Update your Claude config to use local build:

{
  "mcpServers": {
    "twitter": {
      "command": "node",
      "args": ["${absolute_path_to_project}/build/index.js"],
      "envFile": ".env"
    }
  }
}

6. Development commands: ```bash

Build for production

npm run build

Reinstall

npm install

Rebuild

npm run build ```

5. Server Not Responding in Claude

Problem: MCP server not connecting to Claude.

Solutions: - Restart Claude Desktop completely - Check config file syntax is valid JSON - Verify file path in config matches actual location - Check Node.js is installed: node --version - Look for errors in Claude's logs

Quick Start

The easiest way to use this MCP server is through the interactive installer:

npx @muhammadsiddiq/twitter-mcp

Usage

Once configured, you can interact with Twitter through natural language commands to Claude.

Configuration

Step 4: Optional search backend keys

The installer then asks whether you want to add optional read-only search backends for search_tweets.

If you say yes, it can collect:

• XQuik / Hermes Tweet API key
• GetXAPI API key

These are optional. If you skip them, the server still works with the Twitter OAuth credentials.

Getting an Xquik / Hermes Tweet token

1. Sign in at dashboard.xquik.com.
2. Open Account > API Keys.
3. Create an API key for this MCP server and copy it once.
4. Store that value as XQUIK_API_KEY in your MCP config or shell environment.
5. If your deployment uses the Hermes Tweet naming, set the same value as HERMES_TWEET_API_KEY instead.
6. Leave XQUIK_BASE_URL unset unless your team runs a compatible non-default deployment.
7. Restart your client and call search_tweets to verify read-only search.

Keep the key out of Git, chat prompts, screenshots, and shared config files. The key only changes search_tweets; posting and replying still use the Twitter OAuth variables.

Getting a GetXAPI token

1. Sign in at getxapi.com.
2. Create an API key for this MCP server and copy it once.
3. Store that value as GETXAPI_API_KEY in your MCP config or shell environment.
4. Leave GETXAPI_BASE_URL unset unless your team runs a compatible non-default deployment.
5. Restart your client and call search_tweets to verify read-only search.

Environment Variables

Posting tools require Twitter OAuth credentials. search_tweets can use Twitter OAuth credentials, the optional Hermes Tweet/Xquik read-only backend, or the optional GetXAPI read-only backend.

API Reference

Troubleshooting

Can't find Connectors in Settings? - Make sure you're using the latest version of Claude Desktop - Try restarting the application

Path not working? - Use the full absolute path (complete path from root) - Avoid spaces in folder names, or use quotes around the path - Check that the directory actually exists on your computer

Changes not taking effect? - Make sure you completely closed Claude Desktop (check system tray/menu bar) - Wait a few seconds before reopening - Restart your computer if issues persist

Troubleshooting