twitterapi-io-mcp-server
Related Servers
Alternatives to twitterapi-io-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceMCP server for interacting with the X platform (Twitter) via MCP clients like Claude, Cursor AI, and Windsurf AI.208 npm6MIT
- AlicenseAqualityBmaintenanceMCP server for the Twitter/X read API, enabling search, user profiles, tweets, followers, and more via natural language.94984 npmMIT

X API FastMCP Serverofficial
FlicenseNot gradedqualityFmaintenanceA local MCP server that exposes the X API (formerly Twitter API) as tools, enabling operations like posting, searching, user management, and more via natural language commands.856-- AlicenseNot gradedqualityAmaintenanceEnables AI agents to search live public X/Twitter posts and fetch recent posts from user profiles without API keys, using zero-configuration local MCP tools for Claude, Cursor, and Pi.13 npm1MIT
- AlicenseAqualityFmaintenanceA Model Context Protocol (MCP) server that provides access to Twitter data through the TwitterAPI.io service, enabling Claude and other MCP clients to interact with Twitter's ecosystem without requiring Twitter developer account approval.113 npm4MIT
- AlicenseNot gradedqualityDmaintenanceModel Context Protocol server that enables programmatic interaction with Twitter API, allowing users to post tweets, search for content, and retrieve user timelines through standardized MCP tools.7 npmMIT
TDQS
Scored across 12 tools
Each tool targets a distinct entity and action: trends, tweet interactions (quotes, replies, retweeters, batch fetch), user details (info, about, followers, followings, last tweets, mentions), and search. Descriptions explicitly clarify boundaries, e.g., get_user_last_tweets vs. search_tweets for date queries.
All tools follow the verb_noun pattern with prefixes 'get_' or 'search_'. The naming is predictable and clear: get_<entity>_<detail> for most, with search_tweets as a minor but acceptable variation.
12 tools cover a comprehensive set of Twitter read operations without excess. The count is well-balanced, each tool serves a clear purpose, and the scope fits a focused Twitter data retrieval server.
The surface covers essential read operations: trends, tweet data, user profiles, followers/followings, mentions, and search. Minor gaps exist (e.g., no dedicated single tweet fetch or reply threading), but workarounds like get_tweets_by_ids and get_tweet_replies suffice.