MCP SERVER
Twitter / X MCP Server for Claude, Cursor, and Any MCP Client
The TwitterAPIs MCP Server is a Model Context Protocol server that gives Claude Desktop, Cursor, Cline, and any MCP-compatible agent native access to the Twitter/X API. Search tweets, read profiles, followers, threads, and lists, and post, reply, like, retweet, or follow from a linked account, all with a single bearer token. Read calls cost $0.0008; write actions bill from $0.0008 (tweet creation $0.0016), the same rates as the direct REST API.
Every rate here is the pricing TwitterAPIs publishes, $0.0008 per read call and $0.04 per 1,000 tweets (source: twitterapis.com/pricing).
Works in Claude Desktop, Cursor, and any MCP client.
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.
twitter_advanced_searchPull a handle's recent posts into Cursor
Wire a slash command in Cursor that hands a handle to the twitter_user_tweets tool. The MCP layer fetches the latest posts and returns them for drafting or analysis.
twitter_user_tweetsReconstruct a full thread with a Claude agent
Hand Claude a tweet ID and have it pull the entire conversation. The twitter_tweet_thread and twitter_tweet_replies tools return the full reply tree for summarization.
twitter_tweet_thread, twitter_tweet_repliesBuild a Twitter analytics dashboard with Claude Artifacts
Hand Claude a handle and a date range. The agent calls twitter_user_info, twitter_user_followers, and twitter_user_tweets, then renders a Recharts dashboard in an Artifact.
twitter_user_info, twitter_user_followersSync followers to Notion through Claude
Schedule a Claude agent to call twitter_user_followers, dedupe against your Notion DB, and append new rows. No glue code, no Zapier middleware.
twitter_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.
twitter_user_mentionsThe tools the server exposes
The server maps the TwitterAPIs Twitter/X API onto MCP tools. Below are the ones agents reach for most. Read tools run on your API key alone, no OAuth screen and no X developer account; write actions act as a linked X account. Each one wraps an endpoint you can also call over REST directly.
Search and tweet tools
TWITTERAPIS_KEY onlytwitter_advanced_searchAdvanced search with operators, filters, and date rangestwitter_tweet_detailLook up a single tweet by ID with full metadatatwitter_tweet_repliesPull the replies under a tweet with paginationtwitter_tweet_retweetersList the accounts that retweeted a tweettwitter_tweet_threadReconstruct a full self-thread from a tweet ID
User and graph tools
TWITTERAPIS_KEY onlytwitter_user_infoProfile, bio, follower and following counts for a handletwitter_user_tweetsPull a handle's recent poststwitter_user_mentionsRead an account's mentions (a to:username search)twitter_user_followersList an account's followers with paginationtwitter_user_followingList the accounts a handle followstwitter_user_verified_followersList an account's verified followers
Additional read tools
TWITTERAPIS_KEY onlytwitter_user_searchSearch for users by keyword or handle fragmenttwitter_user_info_by_idLook up a user profile by numeric user IDtwitter_user_tweets_and_repliesPull a handle's tweets and replies togethertwitter_user_mediaList a user's media (images and video) tweetstwitter_list_membersList the members of an X list by list ID
Write actions
Linked X sessiontwitter_create_tweetPost a tweet, reply, or quotetwitter_favorite_tweetLike a tweet (undo with twitter_unfavorite_tweet)twitter_retweetRetweet a post (undo with twitter_unretweet)twitter_follow_userFollow an account (undo with twitter_unfollow_user)twitter_dm_sendSend a direct message to a user
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 use 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.
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 (live on npm)
- One line to install and 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.
- Write actions (post, like, retweet, follow, DM) act as a linked X account, billed from $0.0008.
- Pay per call from $0.0008, no monthly subscription and no tier gate on read endpoints.
- Open-sourced on GitHub. The same read endpoints are also callable over REST with the same key.
Setup for Claude Desktop, Cursor, Windsurf, Cline
The same config block works across every MCP client. Every read tool needs only your TWITTERAPIS_KEY, 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 turns the TwitterAPIs Twitter/X API into MCP tools so Claude can search tweets, fetch profiles, list followers, read threads, post, 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. The MCP server adds zero overhead beyond your existing TwitterAPIs API key. Same endpoints and pricing as calling TwitterAPIs directly, just exposed as MCP tools.
Nothing extra for the server itself. Every tool call hits the underlying TwitterAPIs endpoint and is 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.
Yes. Alongside the read tools, the server exposes write actions: create a tweet (reply or quote), like, retweet, bookmark, follow, and send a DM. Write actions act as a linked X account (or per-call inline credentials) rather than just your API key, and because X soft-blocks writes from datacenter IPs they run through a residential proxy. Tweet creation is $0.0016 per call and the simpler write actions are $0.0008.
Install the MCP server with npx -y @twitterapis/mcp@latest, add the config block to your MCP client (Claude Desktop, Cursor, or Cline), and restart the client. The tools appear automatically. You can also call the TwitterAPIs REST endpoints directly: each one is a single HTTP GET with an Authorization: Bearer TWITTERAPIS_KEY header, no X developer account and no OAuth screen.
Sign up at twitterapis.com/signup, generate an API key from the dashboard, and run npx -y @twitterapis/mcp@latest. Drop your key into the TWITTERAPIS_KEY env var in your MCP client config. Email emma@twitterapis.com if you have questions.
Yes. The MCP server is published on npm as @twitterapis/mcp and open-sourced on GitHub. Install it with npx -y @twitterapis/mcp@latest and drop a small config block into your MCP client. You can also call every endpoint directly over plain HTTP with your bearer key; see the Twitter search API and Twitter scraper pages.
X shipped its own hosted MCP server at api.x.com/mcp in June 2026, and it is a good fit if you already run on the official X API: it authenticates with your own X developer credentials over OAuth 2.0 and bills on X's own API pricing, which has no free tier and needs an approved developer account. The TwitterAPIs MCP server is built for the case where you do not want that setup. It authenticates with a single bearer token from signup, needs no X developer account and no OAuth flow, exposes the full read and write toolset (search, profiles, the follower graph, threads, plus post, like, retweet, and DM), and bills pay-per-call from $0.0008 per request, about $0.04 per 1,000 tweets, with a $0.50 starting credit. Use X's server if you want the platform-native option and already pay for the X API; use this one for the cheapest pay-as-you-go path to Twitter and X data inside an agent without a developer-account review.
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 reads the key at startup and forwards it on every tool call. The same key works against the REST endpoints too.
The server exposes the TwitterAPIs read surface as MCP tools: advanced tweet search (twitter_advanced_search), single-tweet detail (twitter_tweet_detail), replies, retweeters, threads, user info and search, user timelines, mentions, the follower and following graph, verified followers, and list members. Every call is gated by your TwitterAPIs API key.
The MCP server itself is 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, email emma@twitterapis.com and we will raise the ceiling.
The TwitterAPIs MCP server is free to install. 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 server is published on npm as @twitterapis/mcp and open-sourced on GitHub.
Ready to give Claude a Twitter/X brain?
Install the MCP server with one command, or call the read endpoints over REST directly. $0.50 free credits cover the first 625 calls.