Google Search Console integration for Model Context Protocol (MCP)
Nothing to run from here
Twitterapi is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
12
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Twitter/X read-only MCP server — 12 tools: search, users, tweets, followers, timelines, trends.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http kaitoinfra-twitterapi-mcp https://mcp.twitterapi.io/mcp
# 2 — ask your agent for something these tools do
# search_tweets, get_user_info, get_user_about and 9 more
Twitterapi costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
KAAll 2 servers
@kaitoinfra2 servers
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http kaitoinfra-twitterapi-mcp https://mcp.twitterapi.io/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
12 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
🎯 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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | 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 si |
| queryType | string | yes | 'Latest' returns most recent tweets first; 'Top' returns highest-engagement tweets first. Default to 'Latest' for time-sensitive queries. |
| cursor | string | no | Pagination cursor from a previous response's next_cursor field. Omit for first page. Each page returns ~20 tweets. |
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 | Required | Notes |
|---|---|---|---|
| userName | string | yes | Twitter/X screen name (handle) WITHOUT the leading @ sign. Example: 'elonmusk', not '@elonmusk'. |
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 | Required | Notes |
|---|---|---|---|
| userName | string | yes | Twitter/X screen name without @ — fetches the user's profile 'about' / bio page. |
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 | Required | Notes |
|---|---|---|---|
| userName | string | yes | Twitter/X screen name without @ — fetches followers of this user. |
| cursor | string | no | Pagination cursor from previous response's next_cursor. Omit for first page. |
| pageSize | integer | no | Followers per page (default 200, max 200). Each follower includes full profile metadata (name, bio, follower count, etc.). |
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 | Required | Notes |
|---|---|---|---|
| userName | string | yes | Twitter/X screen name without @ — fetches accounts this user follows. |
| cursor | string | no | Pagination cursor; omit for first page. |
| pageSize | integer | no | Followings per page (default 200, max 200). Each includes full profile metadata. |
⚠️ 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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| userName | string | no | Twitter/X screen name without @ (e.g. 'elonmusk'). Provide EITHER userName OR userId. |
| userId | string | no | Twitter/X numeric user ID (e.g. '44196397'). Provide EITHER userName OR userId. Prefer userId if known — handles can change. |
| cursor | string | no | Pagination cursor; omit for first page. |
| includeReplies | boolean | no | Include the user's reply tweets in addition to top-level tweets. Default false — only top-level tweets. |
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 | Required | Notes |
|---|---|---|---|
| userName | string | yes | Twitter/X screen name without @ — fetches tweets that mention this user (@userName). |
| sinceTime | integer | no | Unix timestamp (seconds) lower bound — only mentions after this time. Omit for no lower bound. |
| untilTime | integer | no | Unix timestamp (seconds) upper bound. Omit for no upper bound. |
| cursor | string | no | Pagination cursor; omit for first page (~20 per page). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| tweet_ids | string | yes | Comma-separated tweet IDs (e.g. '1234567890,9876543210'). Batch fetch up to 100 tweets in one call. Tweet IDs are numeric strings. |
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 | Required | Notes |
|---|---|---|---|
| tweetId | string | yes | Numeric ID of the tweet to fetch replies for. |
| cursor | string | no | Pagination cursor; omit for first page (~20 replies per page). |
| queryType | string | no | 'Latest' or 'Top' — sort order of replies. Default 'Latest'. |
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 | Required | Notes |
|---|---|---|---|
| tweetId | string | yes | Numeric ID of the tweet to fetch quote-tweets for. |
| sinceTime | integer | no | Unix timestamp (seconds) lower bound. |
| untilTime | integer | no | Unix timestamp (seconds) upper bound. |
| includeReplies | boolean | no | Include reply-type quote-tweets in addition to top-level. Default false. |
| cursor | string | no | Pagination cursor; omit for first page (~20 per page). |
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).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| tweetId | string | yes | Numeric ID of the tweet to fetch retweeters for. |
| cursor | string | no | Pagination cursor; omit for first page (~100 per page). |
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 | Required | Notes |
|---|---|---|---|
| woeid | integer | yes | 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. |
| count | integer | no | Max trends to return (default API behavior; may be silently capped by API). |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Twitterapi or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.1.0.
0.1.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Twitterapi can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.