Log inSubmit server
TwitterAPIs logo

TwitterAPIs

Access Twitter/X search, profiles, timelines, audience data, follower graphs, conversations, lists, and account actions through MCP.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install TwitterAPIs

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "twitterapis": {
      "command": "npx",
      "args": [
        "-y",
        "@twitterapis/mcp@latest"
      ],
      "env": {
        "TWITTERAPIS_KEY": "YOUR_VALUE_HERE",
        "TWITTERAPIS_BASE_URL": "YOUR_VALUE_HERE",
        "TWITTERAPIS_TIMEOUT_MS": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Install not yet sandbox-tested— the server itself is confirmed live (we called its tools/list endpoint). The stdio install command is a separate, ongoing check.

Overview

TwitterAPIs MCP server connects AI agents to twitterapis.com for reading and writing Twitter/X data through MCP tools. It covers advanced tweet search, profile and account-status lookups, timelines, media, followers, relationships, conversations, threads, quotes, retweeters, and list members. Public reads use an API key, while account-specific reads and most write actions require a linked X session or per-call credentials. Reach for it when an agent needs structured Twitter/X research, audience analysis, monitoring, or account operations without a direct X developer account.

Use cases

  • Search recent posts using X operators and engagement filters
  • Analyze followers, following lists, verified audiences, and mutual connections
  • Inspect tweet threads, replies, quotes, retweeters, and media
  • Monitor profiles, account status, mentions, and audience characteristics
  • Publish or engage with posts from a linked X account

Key features

  • Advanced tweet and user search
  • Profile, About, status, and affiliation lookups
  • Cursor-paginated timelines and follower graphs
  • Tweet details, threads, replies, quotes, and retweeters
  • Audience country and likely-bot summaries
  • Authenticated Twitter/X account actions

Tools113

What TwitterAPIs lets your agent do. Expand a tool for its parameters.

Verified live~62.2k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

19/22 checks healthy over the last 90d

What it can do

From the 113 tools this server returned when we ran it; 113 declare their own safety hints.

Can delete or modify data · 25Handles credentials · 52Makes network requests · 101Read-only tools · 88
Network at startup3 connections
Files written at startupNone
Install scriptsNone
npm provenanceNot published
Package age115 days
Maintainers1

Observed 2026-10-17 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 6d ago via OSV.dev · @twitterapis/mcp@latest (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars6Stargazers on the source repository.
npm downloads1.3kPackage downloads in the last 30 days.
Last commit3d agoMost recent push to the default branch.
Tools exposed113Callable tools this server registers over MCP.
Directory activity8 viewsConfig copies, upvotes, and views on AllMCPs.

How TwitterAPIs works

What TwitterAPIs MCP server does

TwitterAPIs exposes Twitter/X data and account operations to MCP-compatible AI clients through the TwitterAPIs API. Its read tools cover tweet discovery, user lookup, profile transparency data, posting histories, media, mentions, likes, follower graphs, follow relationships, audience summaries, tweet conversations, threads, quotes, retweeters, and list membership.

The server also supports writing and authenticated account actions through the broader TwitterAPIs interface, including posting, replying, liking, retweeting, and following. Public data reads can run with an API key. Actions performed as an X account require a linked session or inline credentials.

How it works

Install and run the npm package with npx -y @twitterapis/mcp@latest. Each MCP tool maps to a REST endpoint at api.twitterapis.com, and the server does not retain state. Most read calls cost $0.0008; complete-history and complete-replies calls cost $0.0024, while thread retrieval costs $0.0040. The API also offers a $0.50 starting credit balance for new accounts without requiring a card.

Many endpoints accept either a username or numeric user ID. Tweet lookups accept an ID or full URL. Cursor-based tools return a cursor for retrieving later pages. Read responses can generally be reduced with comma-separated fields paths or the compact option, which is useful when an agent needs to limit response size.

Several endpoints distinguish incomplete results from completed retrieval. Large timeline and reply tools return continuation metadata, so consumers should inspect next_cursor, has_more, or is_complete rather than treating the number of returned records as proof that the full history was retrieved.

Setup and configuration

The required TWITTERAPIS_KEY value comes from the TwitterAPIs dashboard. The server can be configured in Claude Desktop, Cursor, Windsurf, or VS Code using an stdio entry that runs the package with npx. Claude Code can instead connect to the hosted MCP endpoint at https://api.twitterapis.com/mcp.

Optional configuration includes TWITTERAPIS_BASE_URL, which changes the API host, and TWITTERAPIS_TIMEOUT_MS, which sets the per-request timeout. The default timeout is 30,000 milliseconds.

Public reads need only the API key. Account-only reads and most write operations require an X session linked through the API key, either by registering X cookies or logging in with an X username and password. A call can also provide auth_token and ct0 inline, with optional proxy and user-agent values, for one-off authenticated operations. The service recommends a residential proxy for writes because X may soft-block writes from datacenter IP addresses.

Tools and capabilities

  • Search recent tweets with operators such as from:, to:, date bounds, language, engagement thresholds, and link or reply filters.
  • Find users, retrieve complete public profiles, inspect account status, and read structured About information individually or in batches of up to 100 accounts.
  • Retrieve timelines, replies, media, mentions, likes, followers, following lists, verified followers, affiliates, and mutual follow relationships.
  • Examine tweet details, direct replies, same-author threads, retweeters, quote tweets, and members of an X List.
  • Summarize sampled followers or retweeters by country and estimate likely-bot share using documented profile signals.
  • Use write and authenticated account actions through a linked X session, including posting, replying, liking, retweeting, and following.

Limitations and notes

Search-backed quote retrieval may not equal the tweet's authoritative quote count because search indexing, protected accounts, deletions, suspensions, and regional withholding affect coverage. The response reports coverage metadata for this case.

User timelines can contain retweets and replies, and each item includes flags that let a caller distinguish them. A protected account is considered alive by the account-status tool. Hidden Likes tabs may return no liked tweets. Batch endpoints permit only one active batch per API key at a time; concurrent calls can receive a batch_in_progress response. The audience bot percentage is a heuristic based on profile signals, not a definitive classification.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about TwitterAPIs

TwitterAPIs is an MCP server that connects AI clients to Twitter/X through twitterapis.com. Its main tools search tweets and users, retrieve profiles, timelines, followers, conversations, threads, quotes, and lists, and support authenticated account actions such as posting, replying, liking, retweeting, and following.

Run `npx -y @twitterapis/mcp@latest` and configure the `TWITTERAPIS_KEY` environment variable with a key from the TwitterAPIs dashboard. The README includes stdio configurations for Claude Desktop, Cursor, Windsurf, and VS Code.

Yes, TwitterAPIs works with Cursor through an stdio MCP configuration. Add the server to `~/.cursor/mcp.json` or Cursor's MCP settings, run the package with `npx`, and provide `TWITTERAPIS_KEY` in the server environment.

No, the server uses a TwitterAPIs API key rather than requiring a direct X developer account. Public reads work with that key; account-only reads and most write actions additionally require a linked X session or inline session credentials.

Pass the returned pagination cursor back to the same tool to request the next page. For complete timeline and reply tools, inspect `next_cursor`, `has_more`, or `is_complete`, because a response count alone does not prove that retrieval finished.

Related MCP servers

All in Social Media All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewTwitterAPIs AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/twitterapis?style=directory)](https://allmcps.com/mcp/twitterapis)
HTML Embed
<a href="https://allmcps.com/mcp/twitterapis"><img src="https://allmcps.com/api/badge/twitterapis?style=directory" alt="TwitterAPIs on AllMCPs" /></a>