Twitterapi Io Mcp Server

io.github.kaitoInfraPublished by GitHub account kaitoInfrav0.2.1Updated Oct 24, 2026

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

The publisher's own server: Twitterapi

Overview

AI-generated overview

Official twitterapi.io MCP server that lets an assistant search tweets and look up Twitter/X users, followers, replies, quotes, retweeters and trends.

What you can do
Search tweets with advanced Twitter operators such as from:, since:, lang: and has:; batch-fetch tweets by ID and read replies, quote-tweets and retweeters of a tweet. Look up user profiles, extended about pages, recent timelines and mentions. List followers and followings with profile metadata, paginated via a next_cursor. Retrieve trending topics by location (WOEID).
When to use it
Useful when you want an assistant to research public Twitter/X conversations, profiles, follower lists or trending topics from natural language, without writing API code. It is read-only, so it suits analysis and monitoring rather than posting or account management.
Requirements
Runs locally over stdio, typically launched with npx from the npm package @twitterapi_io/mcp-server, so Node.js is needed. Requires a twitterapi.io account and API key supplied in the TWITTERAPI_IO_API_KEY environment variable. Network access to api.twitterapi.io.
Before you install
The API key is sent as the X-API-Key header on every tool call to api.twitterapi.io, and queries and results pass through that third-party service. Usage is billed by twitterapi.io according to its plan, so check pricing and quotas. The server is read-only and deliberately excludes posting, likes, follows, DMs and account changes.

Installation

In SourceWeft

  1. Open Twitterapi Io Mcp Server in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

twitterapi.io MCP Server

[npm version] [MIT License] [MCP Spec 2025-11-25]

Official Model Context Protocol server for twitterapi.io — Twitter / X data API for AI agents and applications.

Connect Claude Desktop, Cursor, VS Code Copilot, or any MCP client to twitterapi.io and search tweets, fetch user profiles, get followers, replies, trends, and more — all from natural language.

Features

12 read-only tools mapped 1:1 to twitterapi.io's verified production endpoints:

ToolWhat it does
search_tweetsAdvanced search with Twitter operators (from:, since:, lang:, has:, …)
get_user_infoUser profile basics by screen name
get_user_aboutExtended profile / about page
get_user_followersFollowers with full profile metadata (paginated)
get_user_followingsFollowing list with profile metadata (paginated)
get_user_last_tweetsA user's recent tweets (timeline)
get_user_mentionsTweets that mention a user
get_tweets_by_idsBatch fetch tweets by ID (up to 100)
get_tweet_repliesReplies to a tweet
get_tweet_quotesQuote-tweets of a tweet
get_tweet_retweetersUsers who retweeted a tweet
get_trendsTrending topics by location (WOEID)

Quick Start

1. Get an API key

Sign up at twitterapi.io — free tier available.

2. Configure your MCP client

Claude Desktop

Edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

json
{  "mcpServers": {    "twitterapi-io": {      "command": "npx",      "args": ["-y", "@twitterapi_io/mcp-server"],      "env": {        "TWITTERAPI_IO_API_KEY": "your_key_here"      }    }  }}

Restart Claude Desktop. The 12 tools will be available in any chat — Claude will pick the right one based on your prompt.

Cursor

Open Settings → MCP → Add new MCP Server:

json
{  "mcpServers": {    "twitterapi-io": {      "command": "npx",      "args": ["-y", "@twitterapi_io/mcp-server"],      "env": {        "TWITTERAPI_IO_API_KEY": "your_key_here"      }    }  }}
VS Code (Copilot Chat with MCP)

Add to your MCP servers config — same shape as Claude Desktop / Cursor.

Claude Code
bash
claude mcp add twitterapi-io npx -- -y @twitterapi_io/mcp-server -e TWITTERAPI_IO_API_KEY=your_key_here

3. Use it

In any MCP-enabled chat:

"Find recent tweets from @elonmusk about AI in the last week"

"Get the follower list of @sama and show me the top 20 by follower count"

"What are the current trending topics in Japan?"

Claude (or your client) will automatically pick search_tweets / get_user_followers / get_trends and call them with the right parameters.

Authentication

Authentication is via the TWITTERAPI_IO_API_KEY environment variable, injected by your MCP client. The server never stores or logs the key. Each tool call sends the key in the X-API-Key header to https://api.twitterapi.io.

Pagination

Tools that return lists (followers, replies, search results, etc.) return a next_cursor field. Pass it back as the cursor argument on the next call to page through. Each page is typically ~20 items.

Error handling

  • 429 / 5xx responses are automatically retried with exponential backoff (3 attempts, 1s/2s/4s)
  • Network timeouts: 30s per request
  • 4xx errors (other than 429) surface immediately to the LLM with the original message

Tools — full spec

Each tool's input schema is exposed via MCP's tools/list and follows JSON Schema. Run npx @twitterapi_io/mcp-server with mcp-inspector to browse interactively:

bash
npx @modelcontextprotocol/inspector npx -y @twitterapi_io/mcp-server

What's NOT included

By design, this server exposes read-only endpoints. The following are intentionally excluded to keep the server safe for autonomous agent use:

  • ❌ Posting tweets, likes, retweets, follows, DMs
  • ❌ Account login / 2FA
  • ❌ Profile / banner / avatar editing
  • ❌ Media upload
  • ❌ Account deletion
  • ❌ Realtime stream / webhook setup (does not fit the MCP request/response model)

These features are available in the full twitterapi.io REST API — use it directly if you need write access.

Spec compliance

  • Built on @modelcontextprotocol/sdk v1
  • Targets MCP spec 2025-11-25 (latest)
  • Transport: stdio (Streamable HTTP planned for v0.2+ for remote/hosted use)
  • Tested with: mcp-inspector, Claude Desktop, Cursor, Claude Code

Development

bash
git clone https://github.com/kaitoInfra/twitterapi-io-mcp-server.gitcd twitterapi-io-mcp-servernpm installnpm run buildTWITTERAPI_IO_API_KEY=xxx npm run inspect  # opens mcp-inspector

Links

License

MIT © twitterapi.io

Source: README.md at commit 490bc06

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

2
  1. v0.2.1LatestOct 6, 2026
  2. v0.1.2Sep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Twitterapi integrations