x-agent-mcp
Related Servers
Alternatives to x-agent-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants and agents to interact with X (Twitter) using cookie-based authentication, covering posting and replying to tweets, reading tweet replies, searching tweets, sending and reading direct messages, and fetching user profiles and tweet engagement data. Also supports liking, retweeting, and deleting tweets, and works with MCP clients such as Claude Desktop and Cursor.34MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to automate Twitter/X tasks (scraping, posting, following, etc.) via 140+ MCP tools, no API key required.440 npm1Apache 2.0
- FlicenseNot gradedqualityNot gradedmaintenanceConnects AI assistants to Twitter/X using cookie-based authentication to read timelines, search tweets, and perform actions like posting and liking. It leverages Twitter's internal GraphQL API to provide full functionality without requiring a developer account.19 npm-
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to connect directly to X (Twitter) and perform actions such as posting, replying, liking, retweeting, searching, and reading timelines using session-cookie authentication.MIT
- 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
- AlicenseAqualityCmaintenanceExposes the Twitter/X API as native MCP tools, letting agents search tweets and users, pull profiles, timelines, followers, lists, communities, and trends, and read account-scoped data like bookmarks, DMs, and home timeline. It also performs write actions such as posting, liking, retweeting, following, and their reversals, using an API key with optional linked or per-call X account credentials.99317 npmMIT
TDQS
Scored across 24 tools
Every tool has a clearly distinct purpose. Even similar tools like get_tweet and get_thread are differentiated by output format (raw vs. clean), and post_tweet, quote_tweet, and retweet are distinct actions.
Most tool names follow a clear verb_noun pattern (get_user, post_tweet, like_tweet, send_dm). One deviation: 'home_timeline' lacks the get_ prefix, but the pattern is otherwise consistent.
24 tools is on the higher end but well-justified for a full-featured X/Twitter client covering tweets, interactions, DMs, follows, search, and timelines. The count feels comprehensive without being bloated.
Core X operations are well covered: tweet lifecycle, likes, retweets, bookmarks, follows, DMs, search, and notifications. Minor gaps exist (e.g., no get_bookmarks or get_dm_thread), but these are not critical to the primary workflows.