twittrapi-mcp
OfficialRelated Servers
Alternatives to twittrapi-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to automate Twitter/X interactions with over 140 tools, requiring no API key.440 npm656Apache 2.0
- AlicenseCqualityBmaintenanceEnables AI agents to search, read user profiles, timelines, media, follow threads, track trends, and manage accounts on X/Twitter via GraphQL, without browser automation or paid API keys.113721 PyPI12MIT
- AlicenseAqualityDmaintenanceEnables AI agents to read, post, search, and engage with Twitter/X content, including AI-powered reply drafting and analytics.17MIT
- FlicenseNot gradedqualityDmaintenanceEnables LLM agents to interact with Twitter (X) for searching tweets, posting content with images, analyzing engagement, and extracting topics using the Twitter API.-
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to fully automate X/Twitter interactions including searching, posting, engaging, and managing multiple accounts without paid API keys.MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to automate Twitter/X actions through the X API v2, supporting over 50 tools for posting, searching, user management, and more.1-
TDQS
Scored across 30 tools
Most tools map to distinct resources or actions, and the descriptions make differences clear. There is some overlap between get_user_by_id/get_user_by_username/username_to_id and between get_community/get_community_about, but the intended use cases are mostly distinguishable.
The set is predominantly consistent snake_case with predictable verb_noun naming such as get_user_tweets and search_tweets. Minor deviations like username_to_id, users_by_ids, and tweets_by_ids are still readable and do not seriously undermine consistency.
Thirty tools is heavy for a single MCP surface, even for a broad Twitter/X data domain. Several batch, raw-JSON, and specialized variants could likely be consolidated or made optional to reduce cognitive load.
The server covers a strong read-only slice of the X API: users, tweets, social graph, lists, communities, trends, and Spaces. Some adjacent read endpoints such as likes, bookmarks, and broader list/Space detail are missing, but core workflows are covered.