X (Twitter) MCP Server

The all-in-one MCP server for X (Twitter). Plug any AI agent — Claude, Cursor, ChatGPT, VS Code, or your own — into a single endpoint and pull live data from any public X account: profile, followers, tweets, replies, and keyword search.

What you get

• Full profile metadata — user ID, display name, bio, follower/following/tweet counts, blue verification, location, website, profile picture, and banner
• Followers list — paginated, with username, display name, bio, blue verification, follower counts, and profile picture for every account
• User timeline — most recent tweets from any public user, with full engagement counts (likes, retweets, replies, quotes, views, bookmarks) and quote/retweet relationships
• Replies to a tweet — every reply on a thread, sorted by Likes / Latest / Relevance, with author and engagement data
• Keyword search — search public tweets with X advanced search operators (from:, since:, until:, lang:, min_faves:, etc.)
• One endpoint, five tools — no glue code, no per-tool integrations, no scraping infrastructure to maintain

Use cases

• AI agents and assistants that need X data without building a custom scraper
• Brand monitoring and social listening — track mentions, replies, and sentiment in real time
• Lead generation and account vetting — pull bio, follower counts, and engagement signals in bulk
• Influencer discovery and outreach — search by topic, then enrich profiles
• Competitor monitoring — follow tweet activity, audience growth, and reply threads
• Trend research and news tracking with keyword + advanced search operators

Tools exposed

Tool	Returns
get-profile	Profile metadata for up to 20 usernames per call
get-followers	Paginated follower list for a username
get-tweets	Paginated user timeline (most recent tweets) for a username
get-replies	Paginated replies to a specific tweet
search-tweets	Paginated keyword / advanced-search results

How to use

Use Apify's hosted MCP gateway — it generates ready-to-paste config snippets for Claude Desktop, Cursor, VS Code, ChatGPT, and any other MCP-compatible client:

mcp.apify.com/?tools=seemuapps/x-mcp

Open the link, sign in, and copy the snippet for your client.

Where to get your Apify API token

Go to console.apify.com/settings/integrations and copy your Personal API token. (Sign in or create a free account if you haven't already.)

The token authorizes calls to the MCP server and is what Apify uses to bill you for tool calls.

Pricing (pay-per-event)

Tool	Event	Charged
get-profile	profile-lookup	Once per profile successfully returned
get-followers	user-result	Once per follower returned
get-tweets	tweet-result	Once per tweet returned
get-replies	reply-result	Once per reply returned
search-tweets	tweet-result	Once per tweet returned

Failed calls are not charged. Partial failures (e.g. one bad username in a batch) are reported per-item without aborting the whole call.

Pagination

get-followers, get-tweets, get-replies, and search-tweets all accept maxItems (default 200) and an optional pageId cursor. Each response includes a nextPageId — pass it as pageId on the next call to fetch the following page. When nextPageId is null, the list is exhausted.

{
  "tweets": [ { "tweetId": "...", "text": "...", ... } ],
  "nextPageId": "DAABCgABG..."
}

When running a tool directly (without an MCP client), the cursor is also written to the run's Key-value store under the NEXT_PAGE_ID key for easy chaining across runs.

Notes

• Only public X accounts and tweets are supported. Protected accounts return profile metadata only.
• Usernames are accepted with or without leading @, and full https://x.com/<user> URLs are also recognised.
• For get-replies, the default sort order is Likes — Relevance often returns very few results, and Latest is reverse-chronological.
• For search-tweets, see X's advanced search operator reference for the full query syntax.