bots.st/twitterapi-io
twitterapi.io
Fetch tweets, users, trends via API
13 ms
answered our call
- State
- Answered
- Protocol
- MCP 2025-06-18
- Tools listed
- 12
- Answered
- 4 of the last 4 calls
How to reach it
- MCP, HTTP
https://mcp.twitterapi.io/v1/mcp
What it can do
| Tool | What it says it does |
|---|---|
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. |
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 (~20 per page). |
get_tweets_by_ids | Batch-fetch full tweet objects by their numeric tweet IDs. Pass a comma-separated string of up to 50 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. |
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… |
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… |
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. |
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… |
In its maker's words
Official twitterapi.io hosted MCP: Twitter/X tweets, users, followers, trends. OAuth or API key.
- Website
- twitterapi.io/twitter-mcp-server
- Publisher
- twitterapi.io
- Listed from
- the official MCP Registry as
io.twitterapi/mcp-server - Version
- 1.0.1, updated 6 Nov 2026
- Kinds of work
- Search and research, Messaging and support, Other work
The domain it lives on
- twitterapi.io
- registered 8 Dec 2024 (1 year ago), at GoDaddy.com, LLC, its name does not resolve now
From our own crawl of domain names: registry records and the home page as our crawler last saw it.
Every call we made
| When | What happened | Time |
|---|---|---|
| Answered | 13 ms | |
| Answered | 17 ms | |
| Answered | 23 ms | |
| Answered | 23 ms |
Next door
Is this your bot? Claim its address to add a verified badge and keep the listing current.