MCP SERVER
Twitter / X MCP Server for Claude, Cursor, and Any MCP Client
Plug the TwitterAPIs Twitter/X read API into Claude Desktop and Cursor as native tools. Search tweets, read profiles, followers, threads, and lists, all behind one bearer token. Pay per call from $0.0008.
$npx -y @twitterapis/mcp@latestThe MCP server is not published yet. Until it ships, call every endpoint directly over REST with the same bearer key.
What you can build with six lines of config
The TwitterAPIs read endpoints become native tools 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_searchPull a handle's recent posts into Cursor
Wire a slash command in Cursor that hands a handle to the user/tweets endpoint. The MCP layer fetches the latest posts and returns them for drafting or analysis.
user/tweetsReconstruct a full thread with a Claude agent
Hand Claude a tweet ID and have it pull the entire conversation. The tweet/thread and tweet/replies endpoints return the full reply tree for summarization.
tweet/thread, tweet/repliesBuild 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/followersSync 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/followersMention 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 review before sending.
user/mentionsThe tools the server will expose
The server will map the TwitterAPIs Twitter/X read API onto MCP tools. Below are the ones agents will reach for most. Every tool runs on your API key alone, no OAuth screen and no X developer account. Each one wraps a read endpoint you can already call over REST today.
Read tweets and search
TWITTERAPIS_KEY onlysearch_tweetsAdvanced search with operators, filters, and date rangesget_tweetLook up a single tweet by ID with full metadataget_user_tweetsPull a handle's recent posts and repliesget_mentionsRead an account's mentions (a "to:username" search)
Read users and graph
TWITTERAPIS_KEY onlyget_userProfile, bio, follower and following counts for a handleget_followersList an account's followers with paginationget_followingList the accounts a handle followsget_verified_followersList an account's verified followers
Read threads and lists
TWITTERAPIS_KEY onlyget_repliesPull the replies under a tweet with paginationget_retweetersList the accounts that retweeted a tweetget_threadReconstruct a full self-thread from a tweet IDget_list_membersList the members of an X list
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. Every tool call bills at the standard pricing of $0.0008 per read, and you only need a Twitter API key in the env block to get started.
Build your own MCP server, or wait for ours
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 against the TwitterAPIs server we are building.
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.
The TwitterAPIs MCP server (not yet released)
- One line to install and one API key in the env block, no developer-account review, once it ships.
- Read tools will work with just your key. No OAuth screen to wire up for search, profiles, and followers.
- Pay per call from $0.0008, no monthly subscription and no tier gate on read endpoints.
- Available today as REST endpoints, so you can start now and swap in the MCP server when it lands.
Planned setup for Claude Desktop, Cursor, Windsurf, Cline
This is the config the server will use once it is published, the same block across every MCP client. The package is not on npm yet, so it will not resolve today; it is here as a preview of how setup will look. Every read tool will need only your TWITTERAPIS_KEY, with no OAuth screen and no X developer account.
{
"mcpServers": {
"twitterapis": {
"command": "npx",
"args": ["-y", "@twitterapis/mcp@latest"],
"env": { "TWITTERAPIS_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 TwitterAPIs MCP server will turn the TwitterAPIs Twitter/X read API into MCP tools so Claude can search tweets, fetch profiles, list followers, read threads, and more.
The official X (Twitter) API requires a paid subscription, a developer-account application, and an OAuth flow per user. TwitterAPIs is pay-per-call from $0.0008 per request, with no subscriptions and no developer-account review, and the MCP server will add zero overhead beyond your existing TwitterAPIs API key. Same endpoints and pricing as calling TwitterAPIs directly, just exposed as MCP tools.
Yes. Sign up at twitterapis.com/signup (Google or email), generate an API key from the dashboard, then drop it into the env block of your MCP client config (TWITTERAPIS_KEY). The MCP server will read the key at startup and forward it on every tool call. The same key already works against the REST endpoints today.
The server will expose the TwitterAPIs read surface as MCP tools: advanced tweet search, single-tweet detail, replies, retweeters, threads, user info and search, user timelines, mentions, affiliates, the follower and following graph, verified followers, and list members. Every call is gated by your TwitterAPIs API key. All of these are already available as REST endpoints today.
Until the MCP server ships, point any Claude or Cursor agent at the TwitterAPIs REST endpoints. Each one is a single HTTP GET with an Authorization: Bearer TWITTERAPIS_KEY header, no X developer account and no OAuth screen, since read access runs on your TwitterAPIs key. When the MCP server is published you will be able to add it with one config block instead.
Sign up at twitterapis.com/signup or message TwitterAPIs on Telegram and we will let you know when the package lands on npm. You can start building against the REST endpoints with the same key in the meantime.
Not yet. The MCP server is in active development and is not published to npm or open-sourced on GitHub. This page is a preview of how it will work. Until it ships, you can do everything it will do by calling the TwitterAPIs read endpoints directly over plain HTTP with your bearer key, see the Twitter search API and Twitter scraper pages.
Nothing extra for the server itself. Every tool call will hit the underlying TwitterAPIs endpoint and be billed at the standard rate of $0.0008 per read call (search, profile, followers, threads). Your first $0.50 in calls are on the house.
Any client that implements the MCP spec: Claude Desktop, Cursor, Cline (VS Code), Continue, and any MCP-compatible runtime, including custom agents built on the Anthropic SDK with the MCP transport layer.
The MCP server itself will be unmetered. The underlying TwitterAPIs 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 TwitterAPIs MCP server will be free to install once it ships; it is not published yet. Calls are billed per request from $0.0008, and your first $0.50 in usage is free, which covers about 625 read calls before you add a cent. Most open-source Twitter MCP servers are 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. TwitterAPIs has no monthly cap and no tier gates on read endpoints.
Where to find us
TwitterAPIs is listed across developer marketplaces and covered in the community. The MCP registry and npm listings will go live when the server ships.
Ready to give Claude a Twitter/X brain?
Sign up and start calling the read endpoints over REST today. The MCP server is on the way. $0.50 free credits cover the first 625 calls.