TweetAPI MCP
OfficialRelated Servers
Alternatives to TweetAPI MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to read public X (Twitter) data without the paid official API, including tweet and user search, profiles, timelines, media, replies, retweeters, followers, lists, and trends. All tools are read-only and rotate across multiple scraping accounts with proxy and rate-limit support.MIT
- AlicenseNot gradedqualityDmaintenanceProvides AI agents and coding assistants with Twitter data access including tweets, user profiles, followers, and search functionality.MIT
- AlicenseNot gradedqualityBmaintenanceProvides read-only access to public X (Twitter) data, including profiles, tweets, timelines, threads, followers, and search, for developers and AI agents.1MIT
- 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.10011MIT
- 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.-
TDQS
Scored across 5 tools
The SDK guidance and tool catalog tools are clearly distinct, but docs_search, endpoint_lookup, and docs_get_page all retrieve documentation and have overlapping boundaries. An agent may struggle to choose between search-by-keyword and endpoint lookup, or between lookup and fetching a full page.
All tools use a consistent tweetapi_ prefix and snake_case, which makes the set readable and grouped. However, patterns vary between resource_action (docs_search), resource_verb_noun (docs_get_page), and noun_noun (sdk_guidance, tool_catalog).
Five tools is well-scoped for a documentation and SDK guidance server. Each tool has a plausible role: search, lookup, full-page retrieval, SDK help, and tool discovery.
The surface covers documentation search, endpoint discovery, full endpoint sections, SDK guidance, and a machine-readable catalog. A minor gap is the lack of an explicit list-all-endpoints or browse operation, though endpoint_lookup partially covers discovery.