Twitter/X API MCP: Search Tweets, Users, Followers (TwitterAPI.io) is an MCP server published by io.twitterapi, hosted at mcp.twitterapi.io. When last checked on 2026-11-21 it was working: it answers and lists its tools. It declares 12 tools, including search_tweets, get_user_info, get_user_about, get_user_followers, get_user_followings.
Official twitterapi.io hosted MCP: Twitter/X tweets, users, followers, trends. OAuth or API key.
5 connections through 4 shared values. Tap any node.
🎯 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.
| Parameter | Type | Description |
|---|---|---|
| query * | string | Twitter advanced search query string. Supports operators: from:USER, to:USER, since:YYYY-MM-DD, until:YYYY-MM-DD, lang:en, filter:replies, -filter:retweets, has:images, etc. Example: 'from:elonmusk since:2026-01-01 has:images' |
None yet. Changes appear after a server's second daily check.
Squares are this server's values; dots are other servers sharing them. A shared address or publisher is a lead, not proof of a common operator.
Inferred from the host name and headers: what a server runs on, not who runs it.
| cursor | string | Pagination cursor from a previous response's next_cursor field. Omit for first page. Each page returns ~20 tweets. |
| queryType * | string | 'Latest' returns most recent tweets first; 'Top' returns highest-engagement tweets first. Default to 'Latest' for time-sensitive queries. |
{
"name": "search_tweets",
"title": "Search Tweets",
"description": "🎯 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:\n • 'tweets from January 2026' → query='from:elonmusk since:2026-01-01 until:2026-02-01'\n • 'tweets between X and Y' → 'from:USER since:X until:Y'\n • 'tweets last week / last month' → translate to since:/until: dates\n • 'tweets containing keyword X by user Y' → 'from:Y X'\n • 'older tweets' / 'archive' / 'in 2025' → use date range, not pagination\n\nDate format: YYYY-MM-DD (UTC midnight). 'until:' is exclusive (until:2026-02-01 = up to Jan 31).\n\nGeneral: 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.",
"inputSchema": {
"type": "object",
"required": [
"query",
"queryType"
],
"properties": {
"query": {
"type": "string",
"description": "Twitter advanced search query string. Supports operators: from:USER, to:USER, since:YYYY-MM-DD, until:YYYY-MM-DD, lang:en, filter:replies, -filter:retweets, has:images, etc. Example: 'from:elonmusk since:2026-01-01 has:images'"
},
"cursor": {
"type": "string",
"description": "Pagination cursor from a previous response's next_cursor field. Omit for first page. Each page returns ~20 tweets."
},
"queryType": {
"enum": [
"Latest",
"Top"
],
"type": "string",
"description": "'Latest' returns most recent tweets first; 'Top' returns highest-engagement tweets first. Default to 'Latest' for time-sensitive queries."
}
}
},
"annotations": {
"title": "Search Tweets",
"readOnlyHint": true,
"openWorldHint": true,
"idempotentHint": true,
"destructiveHint": false
}
}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.
| Parameter | Type | Description |
|---|---|---|
| userName * | string | Twitter/X screen name (handle) WITHOUT the leading @ sign. Example: 'elonmusk', not '@elonmusk'. |
{
"name": "get_user_info",
"title": "Get User Profile",
"description": "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.",
"inputSchema": {
"type": "object",
"required": [
"userName"
],
"properties": {
"userName": {
"type": "string",
"description": "Twitter/X screen name (handle) WITHOUT the leading @ sign. Example: 'elonmusk', not '@elonmusk'."
}
}
},
"annotations": {
"title": "Get User Profile",
"readOnlyHint": true,
"openWorldHint": true,
"idempotentHint": true,
"destructiveHint": false
}
}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.
| Parameter | Type | Description |
|---|---|---|
| userName * | string | Twitter/X screen name without @ — fetches the user's profile 'about' / bio page. |
{
"name": "get_user_about",
"title": "Get User About Page",
"description": "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.",
"inputSchema": {
"type": "object",
"required": [
"userName"
],
"properties": {
"userName": {
"type": "string",
"description": "Twitter/X screen name without @ — fetches the user's profile 'about' / bio page."
}
}
},
"annotations": {
"title": "Get User About Page",
"readOnlyHint": true,
"openWorldHint": true,
"idempotentHint": true,
"destructiveHint": false
}
}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.
| Parameter | Type | Description |
|---|---|---|
| cursor | string | Pagination cursor from previous response's next_cursor. Omit for first page. |
| pageSize | integer | Followers per page (default 200, max 200). Each follower includes full profile metadata (name, bio, follower count, etc.). |
| userName * | string | Twitter/X screen name without @ — fetches followers of this user. |
{
"name": "get_user_followers",
"title": "Get User Followers",
"description": "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.",
"inputSchema": {
"type": "object",
"required": [
"userName"
],
"properties": {
"cursor": {
"type": "string",
"description": "Pagination cursor from previous response's next_cursor. Omit for first page."
},
"pageSize": {
"type": "integer",
"maximum": 200,
"minimum": 1,
"description": "Followers per page (default 200, max 200). Each follower includes full profile metadata (name, bio, follower count, etc.)."
},
"userName": {
"type": "string",
"description": "Twitter/X screen name without @ — fetches followers of this user."
}
}
},
"annotations": {
"title": "Get User Followers",
"readOnlyHint": true,
"openWorldHint": true,
"idempotentHint": true,
"destructiveHint": false
}
}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).
| Parameter | Type | Description |
|---|---|---|
| cursor | string | Pagination cursor; omit for first page. |
| pageSize | integer | Followings per page (default 200, max 200). Each includes full profile metadata. |
| userName * | string | Twitter/X screen name without @ — fetches accounts this user follows. |
{
"name": "get_user_followings",
"title": "Get User Followings",
"description": "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).",
"inputSchema": {
"type": "object",
"required": [
"userName"
],
"properties": {
"cursor": {
"type": "string",
"description": "Pagination cursor; omit for first page."
},
"pageSize": {
"type": "integer",
"maximum": 200,
"minimum": 1,
"description": "Followings per page (default 200, max 200). Each includes full profile metadata."
},
"userName": {
"type": "string",
"description": "Twitter/X screen name without @ — fetches accounts this user follows."
}
}
},
"annotations": {
"title": "Get User Followings",
"readOnlyHint": true,
"openWorldHint": true,
"idempotentHint": true,
"destructiveHint": false
}
}⚠️ 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).
| Parameter | Type | Description |
|---|---|---|
| cursor | string | Pagination cursor; omit for first page. |
| userId | string | Twitter/X numeric user ID (e.g. '44196397'). Provide EITHER userName OR userId. Prefer userId if known — handles can change. |
| userName | string | Twitter/X screen name without @ (e.g. 'elonmusk'). Provide EITHER userName OR userId. |
| includeReplies | boolean | Include the user's reply tweets in addition to top-level tweets. Default false — only top-level tweets. |
{
"name": "get_user_last_tweets",
"title": "Get User's Recent Tweets",
"description": "⚠️ 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'.\n\nFetch 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).",
"inputSchema": {
"type": "object",
"properties": {
"cursor": {
"type": "string",
"description": "Pagination cursor; omit for first page."
},
"userId": {
"type": "string",
"description": "Twitter/X numeric user ID (e.g. '44196397'). Provide EITHER userName OR userId. Prefer userId if known — handles can change."
},
"userName": {
"type": "string",
"description": "Twitter/X screen name without @ (e.g. 'elonmusk'). Provide EITHER userName OR userId."
},
"includeReplies": {
"type": "boolean",
"description": "Include the user's reply tweets in addition to top-level tweets. Default false — only top-level tweets."
}
}
},
"annotations": {
"title": "Get User's Recent Tweets",
"readOnlyHint": true,
"openWorldHint": true,
"idempotentHint": true,
"destructiveHint": false
}
}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.
| Parameter | Type | Description |
|---|---|---|
| cursor | string | Pagination cursor; omit for first page (~20 per page). |
| userName * | string | Twitter/X screen name without @ — fetches tweets that mention this user (@userName). |
| sinceTime | integer | Unix timestamp (seconds) lower bound — only mentions after this time. Omit for no lower bound. |
| untilTime | integer | Unix timestamp (seconds) upper bound. Omit for no upper bound. |
{
"name": "get_user_mentions",
"title": "Get Mentions of a User",
"description": "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.",
"inputSchema": {
"type": "object",
"required": [
"userName"
],
"properties": {
"cursor": {
"type": "string",
"description": "Pagination cursor; omit for first page (~20 per page)."
},
"userName": {
"type": "string",
"description": "Twitter/X screen name without @ — fetches tweets that mention this user (@userName)."
},
"sinceTime": {
"type": "integer",
"description": "Unix timestamp (seconds) lower bound — only mentions after this time. Omit for no lower bound."
},
"untilTime": {
"type": "integer",
"description": "Unix timestamp (seconds) upper bound. Omit for no upper bound."
}
}
},
"annotations": {
"title": "Get Mentions of a User",
"readOnlyHint": true,
"openWorldHint": true,
"idempotentHint": true,
"destructiveHint": false
}
}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.
| Parameter | Type | Description |
|---|---|---|
| tweet_ids * | string | Comma-separated tweet IDs (e.g. '1234567890,9876543210'). Batch fetch up to 50 tweets in one call. Tweet IDs are numeric strings. |
{
"name": "get_tweets_by_ids",
"title": "Batch Get Tweets by IDs",
"description": "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.",
"inputSchema": {
"type": "object",
"required": [
"tweet_ids"
],
"properties": {
"tweet_ids": {
"type": "string",
"description": "Comma-separated tweet IDs (e.g. '1234567890,9876543210'). Batch fetch up to 50 tweets in one call. Tweet IDs are numeric strings."
}
}
},
"annotations": {
"title": "Batch Get Tweets by IDs",
"readOnlyHint": true,
"openWorldHint": true,
"idempotentHint": true,
"destructiveHint": false
}
}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.
| Parameter | Type | Description |
|---|---|---|
| cursor | string | Pagination cursor; omit for first page (~20 replies per page). |
| tweetId * | string | Numeric ID of the tweet to fetch replies for. |
| queryType | string | 'Latest' or 'Top' — sort order of replies. Default 'Latest'. |
{
"name": "get_tweet_replies",
"title": "Get Tweet Replies",
"description": "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.",
"inputSchema": {
"type": "object",
"required": [
"tweetId"
],
"properties": {
"cursor": {
"type": "string",
"description": "Pagination cursor; omit for first page (~20 replies per page)."
},
"tweetId": {
"type": "string",
"description": "Numeric ID of the tweet to fetch replies for."
},
"queryType": {
"enum": [
"Latest",
"Top"
],
"type": "string",
"description": "'Latest' or 'Top' — sort order of replies. Default 'Latest'."
}
}
},
"annotations": {
"title": "Get Tweet Replies",
"readOnlyHint": true,
"openWorldHint": true,
"idempotentHint": true,
"destructiveHint": false
}
}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).
| Parameter | Type | Description |
|---|---|---|
| cursor | string | Pagination cursor; omit for first page (~20 per page). |
| tweetId * | string | Numeric ID of the tweet to fetch quote-tweets for. |
| sinceTime | integer | Unix timestamp (seconds) lower bound. |
| untilTime | integer | Unix timestamp (seconds) upper bound. |
| includeReplies | boolean | Include reply-type quote-tweets in addition to top-level. Default false. |
{
"name": "get_tweet_quotes",
"title": "Get Tweet Quotes",
"description": "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).",
"inputSchema": {
"type": "object",
"required": [
"tweetId"
],
"properties": {
"cursor": {
"type": "string",
"description": "Pagination cursor; omit for first page (~20 per page)."
},
"tweetId": {
"type": "string",
"description": "Numeric ID of the tweet to fetch quote-tweets for."
},
"sinceTime": {
"type": "integer",
"description": "Unix timestamp (seconds) lower bound."
},
"untilTime": {
"type": "integer",
"description": "Unix timestamp (seconds) upper bound."
},
"includeReplies": {
"type": "boolean",
"description": "Include reply-type quote-tweets in addition to top-level. Default false."
}
}
},
"annotations": {
"title": "Get Tweet Quotes",
"readOnlyHint": true,
"openWorldHint": true,
"idempotentHint": true,
"destructiveHint": false
}
}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).
| Parameter | Type | Description |
|---|---|---|
| cursor | string | Pagination cursor; omit for first page (~20 per page). |
| tweetId * | string | Numeric ID of the tweet to fetch retweeters for. |
{
"name": "get_tweet_retweeters",
"title": "Get Tweet Retweeters",
"description": "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).",
"inputSchema": {
"type": "object",
"required": [
"tweetId"
],
"properties": {
"cursor": {
"type": "string",
"description": "Pagination cursor; omit for first page (~20 per page)."
},
"tweetId": {
"type": "string",
"description": "Numeric ID of the tweet to fetch retweeters for."
}
}
},
"annotations": {
"title": "Get Tweet Retweeters",
"readOnlyHint": true,
"openWorldHint": true,
"idempotentHint": true,
"destructiveHint": false
}
}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.
| Parameter | Type | Description |
|---|---|---|
| count | integer | Max trends to return (default API behavior; may be silently capped by API). |
| woeid * | integer | Yahoo Where-On-Earth ID for the location. Common values: 1 = Worldwide, 23424977 = USA, 23424975 = UK, 23424856 = Japan. Use 1 for global trends if unsure. |
{
"name": "get_trends",
"title": "Get Trending Topics",
"description": "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.",
"inputSchema": {
"type": "object",
"required": [
"woeid"
],
"properties": {
"count": {
"type": "integer",
"maximum": 50,
"minimum": 1,
"description": "Max trends to return (default API behavior; may be silently capped by API)."
},
"woeid": {
"type": "integer",
"description": "Yahoo Where-On-Earth ID for the location. Common values: 1 = Worldwide, 23424977 = USA, 23424975 = UK, 23424856 = Japan. Use 1 for global trends if unsure."
}
}
},
"annotations": {
"title": "Get Trending Topics",
"readOnlyHint": true,
"openWorldHint": true,
"idempotentHint": true,
"destructiveHint": false
}
}twitterapi.io MCP server. Read-only access to Twitter/X data via 12 tools (search tweets, user lookup, followers, replies, trends, etc.). Auth: paste your twitterapi.io API key as the Bearer token. Get one free at https://twitterapi.io.
Names, descriptions and schemas were written by the server and are shown as data.