mcpbeat Sign in

Twitterapi MCP Server

by twitterapi Your server? Claim it
answering

Twitterapi is answering right now. Last checked 9 min ago. It exposes 12 tools. Last commit 7 Oct 2026.

Official twitterapi.io hosted MCP: Twitter/X tweets, users, followers, trends. OAuth or API key.

Uptime history 10 days of history
10 days agonow
100.0%
Uptime 24h
92 of 92 checks
12
Tools
read from the server
68 ms
Response time
average over 24h
1
Stars
last commit 7 Oct 2026

Nothing serious here today

Today is the operative word: we check Twitterapi every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 9 min ago.

run in your terminal
claude mcp add mcp-server --transport http https://mcp.twitterapi.io/v1/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "mcp-server": {
      "url": "https://mcp.twitterapi.io/v1/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.mcp-server]
url = "https://mcp.twitterapi.io/v1/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "mcp-server": {
      "url": "https://mcp.twitterapi.io/v1/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "mcp-server": {
      "url": "https://mcp.twitterapi.io/v1/mcp"
    }
  }
}

Available tools 12

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

user
get_user_about
Fetch the extended 'about' / profile page data for a Twitter/X user by screen name. Returns extra profile metadata beyond what get_user_info gives (when available). Use get_user_info first; only call this if you need additional about-page fields.
get_user_followers
Fetch followers of a Twitter/X user in reverse chronological order (newest first), each with full profile metadata (name, bio, follower count, verified status, etc.). Paginates via cursor. Use this to analyze who follows an account, build follower audiences, or sample for competitive analysis. For large accounts use pagination; you will not get all followers in one call.
get_user_followings
Fetch the accounts a Twitter/X user follows, with full profile metadata. Paginates via cursor. Use this to map a user's interest graph (who they follow signals what they care about).
get_user_info
Fetch basic profile info for a Twitter/X user by their screen name (handle). Returns user ID, display name, bio, follower/following counts, verified status, profile picture, banner, location, website, and account creation date. Use this as the starting point for any user analysis.
get_user_last_tweets
⚠️ ONLY for 'latest / recent / what's new' queries about a user. DO NOT use for date-range queries (e.g. 'tweets from January 2026', 'tweets last week', 'tweets between X and Y', 'tweets in 2025'). For specific dates / older tweets, use **search_tweets** with query like 'from:elonmusk since:2026-01-01 until:2026-02-01'. Fetch the MOST RECENT tweets posted by a Twitter/X user, sorted by created_at descending (newest first). Provide EITHER userName (screen name, no @) OR userId (numeric). Use userId when known — handles can change. Set includeReplies=true to include the user's reply tweets in addition to top-level tweets. Paginates via cursor (~20 per page).
get_user_mentions
Fetch tweets that mention a specific Twitter/X user (i.e. tweets containing @userName). Useful for brand monitoring, sentiment tracking on a public figure, or finding conversations involving an account. Supports time-bound queries via sinceTime/untilTime (Unix seconds). Paginates via cursor.
tweet
get_tweet_quotes
Fetch quote-tweets (tweets that quote the given tweetId). Useful for finding commentary on a tweet, measuring reach beyond direct replies. Supports time bounds (sinceTime/untilTime, Unix seconds). Paginates via cursor (~20 per page).
get_tweet_replies
Fetch replies to a specific tweet. Pass the numeric tweetId of the root tweet; returns top-level replies (about 20 per page) with full tweet objects. Use this for thread analysis, sentiment on a viral post, or building reply trees.
get_tweet_retweeters
Fetch users who retweeted a specific tweet (the simple 'retweet' action, not quote-tweets — for those use get_tweet_quotes). Returns user profiles with metadata. Paginates via cursor (~100 per page).
tweets
get_tweets_by_ids
Batch-fetch full tweet objects by their numeric tweet IDs. Pass a comma-separated string of up to 100 IDs. Use this when you already have specific tweet IDs (e.g., from a search result, a URL, or a webhook event) and need the full tweet data — author, text, engagement counts, media, etc.
search_tweets
🎯 PRIMARY CHOICE for date-range / historical / keyword-based tweet queries. Use this (NOT get_user_last_tweets) whenever user asks about a SPECIFIC TIME RANGE or historical tweets: • 'tweets from January 2026' → query='from:elonmusk since:2026-01-01 until:2026-02-01' • 'tweets between X and Y' → 'from:USER since:X until:Y' • 'tweets last week / last month' → translate to since:/until: dates • 'tweets containing keyword X by user Y' → 'from:Y X' • 'older tweets' / 'archive' / 'in 2025' → use date range, not pagination Date format: YYYY-MM-DD (UTC midnight). 'until:' is exclusive (until:2026-02-01 = up to Jan 31). General: Search Twitter/X for tweets matching a query. Supports the full Twitter advanced search syntax (from:, to:, since:, until:, lang:, filter:, has:, -, OR, etc). Returns ~20 tweets per page in reverse chronological order ('Latest') or by engagement ('Top'). Use this for keyword research, monitoring mentions of a brand/topic, finding tweets in a date range, or any open-ended tweet discovery.
trends
get_trends
Fetch current trending topics/hashtags for a location. Pass a Yahoo Where-On-Earth ID (woeid). Common: 1=Worldwide, 23424977=USA, 23424975=UK, 23424856=Japan, 23424848=India, 23424881=South Korea. Use woeid=1 for global trends if you don't know a specific location.

Endpoints

URLTransportStateLatencyChecked
https://mcp.twitterapi.io/v1/mcp streamable-http answering 61 ms 9 min ago

Alternatives to Twitterapi

same job, measured the same way
Twitterapi Io MCP Server
by kaitoinfra

Official twitterapi.io MCP server (npm, stdio): Twitter/X tweets, users, followers, trends.

157 installs/wk local only
TwtAPI
by tonygjj

Hosted Twitter/X tools for search, users, timelines, followers, trends, and research.

answering
TwitterAPIs
by twitterapis

Official MCP server for twitterapis.com. Read and write Twitter/X: search, users, tweets, DMs.

137 installs/wk answering
Twitterapi MCP Server
by kaitoinfra

Twitter/X read-only MCP server — 12 tools: search, users, tweets, followers, timelines, trends.

12 tools answering
X Twitter
by jojapi

X (twitter): x, xapi, Twitter, twitter api, twitters ,tweets, tw, twttr, FollowerIds, friendsIds.

107 tools answering
X Twitter Data
by superagnt

X (Twitter) data for AI agents: tweets, profiles, followers, search, trends + social listening.

answering
ScrapeBadger
by scrape-badger

Twitter/X scraping for AI agents: profiles, tweets, followers, trends, lists and communities.

114 installs/wk local only
X (Twitter) Trends MCP
by trendsmcp

Twitter (X) trends over time, with growth for any keyword. Free key at trendsmcp.ai

4 tools answering

Twitterapi — questions

Answers built from our own checks of this server.

What can Twitterapi do?
It exposes 12 tools, read directly from the server on our last check. Among them: get_trends, get_tweet_quotes, get_tweet_replies, get_tweet_retweeters, get_tweets_by_ids, get_user_about and 6 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
What is Twitterapi mostly used for?
Its tools cluster around user, tweet and tweets. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is Twitterapi working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 68 ms. The bar chart above shows every period we have measured.
How do I connect Twitterapi?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Twitterapi need an API key?
No. Twitterapi completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 12 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Twitterapi?
It answers our handshake in 68 ms on average, which is faster than 92% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Twitterapi open source?
Yes — it is published under the MIT licence, written in TypeScript and 1 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.