TwitterAPIs MCP Server

Official MCP server for twitterapis.com. Read and write Twitter/X: search, users, tweets, DMs.

Local serverstdio

What is the TwitterAPIs MCP server?

Most developer tooling work still happens through a UI a human drives. TwitterAPIs MCP server moves it into the conversation instead. Official MCP server for twitterapis.com. Read and write Twitter/X: search, users, tweets, DMs.

The short version

Official Model Context Protocol server for twitterapis.com, the Twitter / X API as native tools for Claude, Cursor, Windsurf, and any MCP client. Reads (search, profiles, timelines, followers, DMs) plus write actions (post, like, retweet, follow).

The tools it exposes

The server publishes 3 tools. What each one is for:

  • Cursor — The Cursor tool exposed by this server
  • Windsurf — The Windsurf tool exposed by this server
  • Reads — The Reads tool exposed by this server

What it needs from you

Configuration is passed through the environment: TWITTERAPIS_KEY, TWITTERAPIS_TIMEOUT_MS, YOUR_API_KEY, TWITTERAPIS_BASE_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Getting it running

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

How it compares

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. TwitterAPIs's toolset — Cursor, Windsurf, Reads — is a fair guide to whether it matches your workflow. It is maintained by TwitterAPIs; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Things to watch

  • 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.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
CursorThe Cursor tool exposed by this server.
WindsurfThe Windsurf tool exposed by this server.
ReadsThe Reads tool exposed by this server.

How to install the TwitterAPIs MCP server

{
  "mcpServers": {
    "twitterapis": {
      "command": "npx",
      "args": ["-y", "@twitterapis/mcp@latest"],
      "env": { "TWITTERAPIS_KEY": "YOUR_API_KEY" }
    }
  }
}

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

Configuration

VariableDescriptionRequired
TWITTERAPIS_KEYCredential the server authenticates with.Yes
TWITTERAPIS_TIMEOUT_MSConfiguration value read at startup.Optional
YOUR_API_KEYCredential the server authenticates with.Yes
TWITTERAPIS_BASE_URLEndpoint or connection string the server talks to.Yes

Example prompts to try

  • Use TwitterAPIs to Cursor.
  • Use TwitterAPIs to Windsurf.
  • Use TwitterAPIs to Reads.

Frequently asked questions

It connects TwitterAPIs to MCP-compatible AI assistants such as Claude and Cursor, exposing 3 tools (Cursor, Windsurf, Reads) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with TwitterAPIs directly.