Twitter / X MCP Server for Claude, Cursor, and Any MCP Client

Plug the full GetXAPI Twitter/X API into Claude Desktop and Cursor as native tools. Search, post, DMs, followers, and more, all behind one bearer token. One-line install, pay per call from $0.001.

Start Free View the docs GitHub

What you can build with six lines of config

Every GetXAPI endpoint becomes a native tool inside your MCP client. No glue code, no OAuth flow, no scope review.

Ask Claude to find tweets on any topic

Type "find recent posts about MCP servers" in Claude Desktop and the agent calls the advanced search endpoint and summarizes the results in-line.

tweet/advanced_search

Have Cursor post a tweet on your behalf

Wire a slash command in Cursor that hands a draft to the tweet/create endpoint. The MCP layer signs the request, posts the tweet, and returns the new tweet ID.

tweet/create

Triage your DMs with a Claude agent

Ask Claude to read the inbox, classify each conversation, and reply to the high-signal ones using your tone. The dm/list and dm/send endpoints power the loop.

dm/list, dm/send

Build a Twitter analytics dashboard with Claude Artifacts

Hand Claude a handle and a date range. The agent pulls the user profile, follower list, and recent posts, then renders a Recharts dashboard in an Artifact.

user/info, user/followers

Sync followers to Notion through Claude

Schedule a Claude agent to call user/followers, dedupe against your Notion DB, and append new rows. No glue code, no Zapier middleware.

user/followers

Mention monitor that drafts replies

Run a Cursor or Claude agent that watches mentions every 30 minutes, ranks by signal, and drafts a reply you can send with one keystroke.

tweet/mentions, tweet/create

The tools the server exposes

The server maps the full GetXAPI Twitter/X API onto MCP tools. Below are the ones agents reach for most. Read tools run on your API key alone; write tools post and message as your X account.

Read tweets and search

GETXAPI_KEY only

search_tweetsAdvanced search with operators, filters, and date ranges
get_tweetLook up a single tweet by ID with full metadata
get_user_tweetsPull a handle's recent posts and replies
get_mentionsFetch posts that mention an account

Read users and graph

GETXAPI_KEY only

get_userProfile, bio, follower and following counts for a handle
get_followersList an account's followers with pagination
get_followingList the accounts a handle follows

Post and engage

X account auth

create_tweetPost a tweet, reply, or quote and return the new ID
delete_tweetRemove one of your own tweets by ID
favorite_tweetLike or unlike a tweet
retweetRetweet or undo a retweet
bookmark_tweetAdd or remove a bookmark

Direct messages

X account auth

send_dmSend a direct message to a user
list_dmsList recent DM conversations
get_dm_conversationRead the messages in one DM thread

Want the read tools without the MCP layer? They wrap the same endpoints behind our Twitter search API and Twitter scraper, callable over plain HTTP.

Build your own MCP server, or use this one

Most Twitter MCP servers on GitHub are thin wrappers over the official X API. They work, but you inherit the X API setup and its limits. Here is the honest trade-off.

Roll your own on the official X API

Apply for an X developer account and wait for approval.
Set up OAuth 1.0a or OAuth 2.0 with PKCE, manage token refresh, and store secrets per user.
Live inside tier limits: the free tier sits near 100 reads a month, and the like and follow endpoints were pulled from it in 2025. Basic is $200 a month.
Maintain rate-limit handling and the v1.1 to v2 fallbacks yourself.

Use the GetXAPI MCP server

One line to install, one API key in the env block, no developer-account review.
Read tools work with just your key. No OAuth screen to wire up for search, profiles, and followers.
Pay per call from $0.001, no monthly subscription and no tier gate on read endpoints.
Open source on GitHub, so you can read every line, fork it, or extend the tool set.

Setup for Claude Desktop, Cursor, Windsurf, Cline

The server block is identical across every MCP client. Pick your tab below, paste it into the client config (or run the one-line Claude Code command), restart, and the Twitter/X tools show up automatically. Read tools need only GETXAPI_KEY; post, like, and DM tools use your registered X account auth.

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

FAQ

Everything developers ask before they switch their X API stack to MCP.

MCP is an open protocol from Anthropic for connecting AI assistants to external tools and data. An MCP server exposes a set of tools (with typed inputs and outputs) that any compliant client (Claude Desktop, Cursor, Cline, Continue, others) can call during a conversation. The GetXAPI MCP server turns the full GetXAPI Twitter/X API into MCP tools so Claude can search, post, fetch profiles, list followers, send DMs, and more.

Nothing extra. The MCP server is open source on GitHub and free to install. Every tool call hits the underlying GetXAPI endpoint and is billed at the standard rate: $0.001 per read (search, profile, followers), $0.002 per write (post, DM, delete), $0.005 to $0.01 for Article endpoints. Your first $0.10 in calls are on the house.

Any client that implements the MCP spec. Verified: Claude Desktop, Cursor, Cline (VS Code), Continue. Should work in any MCP-compatible runtime, including custom agents built on the Anthropic SDK with the MCP transport layer.

The MCP server itself is unmetered. The underlying GetXAPI API applies standard per-account fair-use limits that are well above what an interactive Claude or Cursor session can hit. If you are running a high-throughput batch agent, contact us on Telegram and we will raise the ceiling.

The GetXAPI MCP server is open source and free to install from npm or GitHub. Calls are billed per request from $0.001, and your first $0.10 in usage is free, which covers about 100 read calls before you add a cent. Most open-source Twitter MCP servers are also free to run but sit on top of the official X API, where the free tier caps you near 100 reads a month and removed the like and follow endpoints in 2025. GetXAPI has no monthly cap and no tier gates on read endpoints.

The official X (Twitter) API requires a paid subscription, a developer-account application, and an OAuth flow per user. GetXAPI is pay-per-call from $0.001 per request, with no subscriptions and no developer-account review, and the MCP server adds zero overhead beyond your existing GetXAPI API key. Same endpoints and pricing as calling GetXAPI directly, just exposed as MCP tools.

Yes. Sign up at getxapi.com/signup (Google or email), generate an API key from the dashboard, then drop it into the env block of your MCP client config (GETXAPI_KEY). The MCP server reads the key at startup and forwards it on every tool call.

Yes. The server exposes tweet/create, tweet/delete, dm/send, dm/list, dm/conversation, and the full retweet/favorite/bookmark set. Every write call is gated by your API key and tied to the X account whose auth_token is registered to your GetXAPI account.

Open claude_desktop_config.json, paste the getxapi block (command npx, args -y @getxapi/mcp@latest, env GETXAPI_KEY), save, and restart Claude Desktop. The Twitter/X tools show up automatically in the next conversation. On Claude Code, run claude mcp add getxapi npx -y @getxapi/mcp@latest --scope user --env GETXAPI_KEY=YOUR_API_KEY instead. No X developer account and no OAuth screen in either path, since read access runs on your GetXAPI key.

File an issue on the GitHub repo or message bozad on Telegram. The MCP server is open source and ships updates whenever the underlying GetXAPI API gets new endpoints.