Twitter MCP Server
Related Servers
Alternatives to Twitter MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceProvides AI agents with comprehensive Twitter functionality through the Model Context Protocol standard, enabling reading tweets, posting content, managing interactions, and accessing timeline data with robust error handling.11 npm20MIT
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that enables AI models and applications to interact directly with Twitter/X, providing capabilities to create posts, reply to tweets, retrieve user data, and manage account actions.8 npm11MIT
- AlicenseBqualityDmaintenanceA Model Context Protocol server that enables AI agents to interact with Twitter without direct API access, supporting tweet operations, user interactions, and Grok AI integration.141,402 npm32MIT
- 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 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.11 npmMIT
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that enables AI assistants to interact with Twitter functionality using cookie-based authentication, allowing for timeline access, tweet management, user information retrieval, and search capabilities.16-
TDQS
Scored across 53 tools
Most tools have distinct purposes, but there is significant overlap in some areas, such as multiple tweet search tools (advancedTweetSearch, historicalTweetSearch, searchTweets) and several analytics tools (e.g., analyzeFollowerDemographics, userGrowthAnalytics, userInfluenceMetrics) that could cause confusion. Descriptions help differentiate them, but the sheer number of similar tools increases ambiguity.
Tool names generally follow a consistent verb_noun pattern (e.g., postTweet, getUserInfo, likeTweet), with only minor deviations like 'addUserToList' (which could be 'addUserToList' is consistent in structure but uses 'add' instead of a more standard verb like 'create'). Overall, the naming is predictable and readable across the set.
With 53 tools, this server is overly comprehensive for a Twitter API wrapper, making it heavy and potentially overwhelming. The scope includes many niche analytics and advanced features that might be better grouped or omitted, as typical MCP servers for social media have 10-30 tools. This count feels excessive and could hinder usability.
The tool set provides complete coverage for Twitter operations, including CRUD for tweets, users, lists, and direct messages, along with advanced features like analytics, search, and engagement tracking. There are no obvious gaps; agents can perform all core and extended workflows without dead ends.