X Integration MCP Server

Enables interaction with X (formerly Twitter) for retrieving tweets, creating new posts, and replying to existing ones.

Local serverstdioTypeScript 73

What is the X Integration MCP server?

X Integration MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. Enables interaction with X (formerly Twitter) for retrieving tweets, creating new posts, and replying to existing ones.

What you get

A Model Context Protocol (MCP) server for X (Twitter) integration. Provides 26 tools for reading timelines, posting, searching, engagement (likes, retweets, bookmarks), user lookup, follower export, mentions, likes, articles, and lists. Designed for use with Claude desktop and other MCP-compatible clients.

  • Timeline & Search — - Home timeline, search recent posts (7-day window)
  • Post Management — - Create, reply, quote, delete posts with optional media
  • Engagement — - Like/unlike, retweet/undo, bookmark/unbookmark
  • User Data — - Mentions, liked posts, followers, following, blocks, mutes, owned lists, followed lists, and list memberships
  • User Lookup — - Get user profiles and their recent posts
  • Media Upload — - Images (PNG, JPEG, GIF, WEBP) and videos (MP4, MOV, AVI, WEBM, M4V) via v2 upload API

What the assistant can call

Once X Integration is connected, these are the calls the assistant has available:

  • Pay-per — call pricing: $0.001 / call, $0.05 / 1K tweets
  • Tier — Cost
  • Free — $0
  • Basic — $200/month
  • Pro — $5,000/month
  • Pay-Per-Use — Credit-based
  • Engagement — The Engagement tool exposed by this server
  • Users — The Users tool exposed by this server
  • Articles — The Articles tool exposed by this server

Setting it up

npm on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Configuration and credentials

You will need 8 environment variables: TWITTER_API_KEY, TWITTER_API_SECRET, TWITTER_ACCESS_TOKEN, TWITTER_ACCESS_SECRET, TWITTER_OAUTH2_ACCESS_TOKEN, TWITTER_CLIENT_ID, TWITTER_CLIENT_SECRET, TWITTER_OAUTH2_REFRESH_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

  • Node.js >= 18.0.0 - X (Twitter) Developer Account - Claude desktop app (or any MCP-compatible client)

Choosing this one

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. X Integration's toolset — Pay-per, Tier, Free and 6 more — is a fair guide to whether it matches your workflow. It is maintained by DataWhisker; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Before you rely on it

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • With 9 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch X Integration.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the x integration mcp server does with a few real requests.

Available tools

ToolWhat it does
Pay-percall pricing: $0.001 / call, $0.05 / 1K tweets
TierCost
Free$0
Basic$200/month
Pro$5,000/month
Pay-Per-UseCredit-based
EngagementThe Engagement tool exposed by this server.
UsersThe Users tool exposed by this server.
ArticlesThe Articles tool exposed by this server.

How to install the X Integration MCP server

{
  "mcpServers": {
    "x": {
      "command": "node",
      "args": ["C:/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",
        "TWITTER_OAUTH2_ACCESS_TOKEN": "your-oauth2-token"
      }
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

  • Node.js >= 18.0.0 - X (Twitter) Developer Account - Claude desktop app (or any MCP-compatible client)
VariableDescriptionRequired
TWITTER_API_KEYCredential the server authenticates with.Yes
TWITTER_API_SECRETCredential the server authenticates with.Yes
TWITTER_ACCESS_TOKENCredential the server authenticates with.Yes
TWITTER_ACCESS_SECRETCredential the server authenticates with.Yes
TWITTER_OAUTH2_ACCESS_TOKENCredential the server authenticates with.Yes
TWITTER_CLIENT_IDConfiguration value read at startup.Optional
TWITTER_CLIENT_SECRETCredential the server authenticates with.Yes
TWITTER_OAUTH2_REFRESH_TOKENCredential the server authenticates with.Yes

Example prompts to try

  • Use X Integration to Pay-per.
  • Use X Integration to Tier.
  • Use X Integration to Free.

Frequently asked questions

X Integration is a tool that allows you to interact with the X (formerly Twitter) API. You can use it to retrieve tweets, create new posts, reply to existing tweets, and automate your X presence.