io.github.kaitoInfra/twitterapi-mcp-server is a remote MCP server that gives an AI agent 12 tools, among them get_trends, get_tweet_quotes, get_tweet_replies. It answers at https://mcp.twitterapi.io/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 11 September 2026; the last check, on 22 October 2026, succeeded.
Twitter/X read-only MCP server — 12 tools: search, users, tweets, followers, timelines, trends.
Description as the publisher wrote it.
| Tool | What 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 Inputs: woeid, count |
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). Inputs: tweetId, sinceTime, untilTime, includeReplies, cursor |
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. Inputs: tweetId, cursor, queryType |
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). Inputs: tweetId, cursor |
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 dat Inputs: tweet_ids |
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 f Inputs: userName |
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 f Inputs: userName, cursor, pageSize |
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). Inputs: userName, cursor, pageSize |
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 Inputs: userName |
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 **s Inputs: userName, userId, cursor, includeReplies |
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 since Inputs: userName, sinceTime, untilTime, 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:2 Inputs: query, queryType, cursor |
Every block below points at https://mcp.twitterapi.io/mcp. Pick your client and copy.
claude mcp add --transport http io-github-kaitoinfra-twitterapi https://mcp.twitterapi.io/mcp
{
"mcpServers": {
"io-github-kaitoinfra-twitterapi": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://mcp.twitterapi.io/mcp"]
}
}
}{
"mcpServers": {
"io-github-kaitoinfra-twitterapi": {
"url": "https://mcp.twitterapi.io/mcp"
}
}
}{
"servers": {
"io-github-kaitoinfra-twitterapi": {
"type": "http",
"url": "https://mcp.twitterapi.io/mcp"
}
}
}{
"context_servers": {
"io-github-kaitoinfra-twitterapi": {
"url": "https://mcp.twitterapi.io/mcp"
}
}
}{
"mcpServers": {
"io-github-kaitoinfra-twitterapi": {
"serverUrl": "https://mcp.twitterapi.io/mcp"
}
}
}{
"mcpServers": {
"io-github-kaitoinfra-twitterapi": {
"url": "https://mcp.twitterapi.io/mcp"
}
}
}name: io.github.kaitoInfra/twitterapi-mcp-server
version: 0.0.1
schema: v1
mcpServers:
- name: io.github.kaitoInfra/twitterapi-mcp-server
type: streamable-http
url: https://mcp.twitterapi.io/mcp{
"mcpServers": {
"io-github-kaitoinfra-twitterapi": {
"httpUrl": "https://mcp.twitterapi.io/mcp"
}
}
}{
"mcpServers": {
"io-github-kaitoinfra-twitterapi": {
"type": "http",
"url": "https://mcp.twitterapi.io/mcp"
}
}
}{
"mcpServers": {
"io-github-kaitoinfra-twitterapi": {
"url": "https://mcp.twitterapi.io/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fmcp.twitterapi.io%2Fmcp&type=streamable_http&id=io-github-kaitoinfra-twitterapi&name=io.github.kaitoInfra/twitterapi-mcp-server
It answered our last check on 22 October 2026 in 174 ms. Over 6 checks since 11 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.
12, as returned by the server's own tools/list on 14 September 2026: get_trends, get_tweet_quotes, get_tweet_replies, get_tweet_retweeters, get_tweets_by_ids, get_user_about, get_user_followers, get_user_followings, and 4 more.
It answered our last check on 22 October 2026 in 174 ms. Over 6 checks since 11 September 2026 it answered 6.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://mcp.twitterapi.io/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: io.github.kaitoinfra. Endpoint host: mcp.twitterapi.io. ARD identifier: urn:air:io.github.kaitoinfra:mcp:twitterapi-mcp-server.
First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.