# Twitter/X MCP Server for Claude and Cursor | TwitterAPIs

Canonical: https://www.twitterapis.com/mcp
Description: Plug the TwitterAPIs Twitter/X API into Claude and Cursor as native tools. Search tweets, profiles, followers, and threads. $0.0008 per call.
Generated: 2026-09-14T03:00:38.028Z

---

1.  [Home](/)
2.  / MCP Server

 MCP SERVER

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

## What is the Twitter (X) MCP server?

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. The billed rate is $0.0008 per read call; $0.04 per 1,000 tweets is derived from it at a full 20-tweet page, the default page size rather than a guaranteed yield. Per our own spec, 62 of 109 endpoints bill that rate (source: [twitterapis.com/pricing](/pricing)).

`$npx -y @twitterapis/mcp@latest`

Works in Claude Desktop, Cursor, and any MCP client.

[Start Free](/signup?utm_source=aio&utm_medium=organic&utm_campaign=aeo-mcp)[View the docs](https://docs.twitterapis.com)[Use the REST API now](/twitter-search-api)

## 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_search`

### Pull 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_tweets`

### Reconstruct 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_replies`

### Build 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_followers`

### Sync 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_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 review before sending.

`twitter_user_mentions`

## The 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 only

-   `twitter_advanced_search`Advanced search with operators, filters, and date ranges
-   `twitter_tweet_detail`Look up a single tweet by ID with full metadata
-   `twitter_tweet_replies`Pull the replies under a tweet with pagination
-   `twitter_tweet_retweeters`List the accounts that retweeted a tweet
-   `twitter_tweet_thread`Reconstruct a full self-thread from a tweet ID

### User and graph tools

TWITTERAPIS\_KEY only

-   `twitter_user_info`Profile, bio, follower and following counts for a handle
-   `twitter_user_tweets`Pull a handle's recent posts
-   `twitter_user_mentions`Read an account's mentions (a to:username search)
-   `twitter_user_followers`List an account's followers with pagination
-   `twitter_user_following`List the accounts a handle follows
-   `twitter_user_verified_followers`List an account's verified followers

### Additional read tools

TWITTERAPIS\_KEY only

-   `twitter_user_search`Search for users by keyword or handle fragment
-   `twitter_user_info_by_id`Look up a user profile by numeric user ID
-   `twitter_user_tweets_and_replies`Pull a handle's tweets and replies together
-   `twitter_user_media`List a user's media (images and video) tweets
-   `twitter_list_members`List the members of an X list by list ID

### Write actions

Linked X session

-   `twitter_create_tweet`Post a tweet, reply, or quote
-   `twitter_favorite_tweet`Like a tweet (undo with twitter\_unfavorite\_tweet)
-   `twitter_retweet`Retweet a post (undo with twitter\_unretweet)
-   `twitter_follow_user`Follow an account (undo with twitter\_unfollow\_user)
-   `twitter_dm_send`Send a direct message to a user

Want the read tools without the MCP layer? They wrap the same endpoints behind our [Twitter search API](/twitter-search-api) and [Twitter scraper](/twitter-scraper), callable over plain HTTP. Every tool call bills at the standard [pricing](/pricing) of $0.0008 per read, and you only need a [Twitter API key](/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.

claude\_desktop\_config.jsonCursor / Windsurf mcp.jsonCline (VS Code)Claude Code CLI

```
{
  "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.

### What is the Model Context Protocol (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.

### How does the TwitterAPIs MCP server compare to the official X API?

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.

### What does it cost to use the MCP server?

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.

### Which MCP clients does this work with?

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.

### Can the MCP server post tweets or write to X?

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.

### How can I give Claude Twitter access today?

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.

### How do I get started?

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.

### Is the TwitterAPIs MCP server available yet?

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.

### How is the TwitterAPIs MCP server different from X's official MCP server?

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, which is about $0.04 per 1,000 tweets when a call returns a full 20-tweet page, 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.

### Do I need a TwitterAPIs API key?

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.

### What can I read through the MCP server?

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.

### Is there a rate limit on the MCP server?

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.

### Is there a free Twitter MCP server?

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.

[

![blog.donweb.com logo](https://img.logo.dev/donweb.com?token=pk_N5RgaIDWS9ix_HS6obPOag&size=64&format=png&retina=true)

Publishing tweets without paying for the X API (Spanish)

blog.donweb.com

](https://blog.donweb.com/publicar-tweets-sin-pagar-api-x/)[

![glama.ai logo](https://img.logo.dev/glama.ai?token=pk_N5RgaIDWS9ix_HS6obPOag&size=64&format=png&retina=true)

TwitterAPIs MCP server on Glama

glama.ai

](https://glama.ai/mcp/servers/TwitterAPIs/twitterapis-mcp)

### 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.

[Get an API key](/signup?utm_source=aio&utm_medium=organic&utm_campaign=aeo-mcp)[Browse the docs](https://docs.twitterapis.com)

[

TwitterAPIs ](/)

The cheapest pay-as-you-go Twitter and X API. $0.0008 per call, which works out to $0.04 per 1,000 tweets on a full 20-tweet page. No subscriptions and no developer account.

## Product / API

-   [Pricing](/pricing)
-   [Cost Calculator](/twitter-api-cost-calculator)
-   [Rate Limits](/twitter-api-rate-limits)
-   [MCP Server](/mcp)
-   [Integrations](/integrations)
-   [Language Clients](/sdk)
-   [Changelog](/changelog)
-   [Status](/status)

## Developers

-   [Documentation](https://docs.twitterapis.com)
-   [API Reference](https://docs.twitterapis.com/docs/reference/search/tweet-advanced-search)
-   [User Info](https://docs.twitterapis.com/docs/reference/user-reads/user-info)
-   [User Tweets](https://docs.twitterapis.com/docs/reference/user-reads/user-tweets)
-   [Advanced Search](https://docs.twitterapis.com/docs/reference/search/tweet-advanced-search)
-   [Verified Followers](https://docs.twitterapis.com/docs/reference/follower-graph/user-verified-followers)

## Resources / Compare

-   [Answers](/answers)
-   [Reviews](/reviews)
-   [Free Tools](/tools)
-   [Twitter ID Finder](/tools/twitter-id-finder)
-   [Get a Twitter API Key](/twitter-api-key)
-   [Official X API Comparison](/twitter-api-pricing)
-   [Twitter API Use Cases](/twitter-api-usecases)
-   [Twitter API Alternatives](/twitter-api-alternatives)
-   [Twitter Unofficial API](/twitter-unofficial-api)
-   [Twitter Free API](/twitter-free-api)
-   [TwitterAPIs vs twitterapi.io](/twitterapis-vs-twitterapi-io)
-   [TwitterAPIs vs GetXAPI](/twitterapis-vs-getxapi)
-   [TwitterAPIs vs TweetAPI](/twitterapis-vs-tweetapi)
-   [TwitterAPIs vs TwexAPI](/twitterapis-vs-twexapi)
-   [TwitterAPIs vs RapidAPI](/twitterapis-vs-rapidapi)

## Legal

-   [About](/about)
-   [Security](/security)
-   [Trust](/privacy-and-data-handling)
-   [Terms of Service](/terms-of-service)
-   [Affiliates](/affiliates)
-   [Contact](/contact)
-   [Jobs](/jobs)

© 2026 TwitterAPIs. All rights reserved.

TwitterAPIs is an independent third-party API for developers and researchers. Not affiliated with, endorsed by, or sponsored by X Corp.

All systems operational