Side-by-side comparison of two Model Context Protocol servers — install paths, tools, quality signals, and directory engagement so you can pick the right one for Claude, Cursor, and other MCP clients.
Twitter/X MCP server with 34 tools — post tweets, search, read timelines, manage engagement, upload media. No API keys needed, uses browser cookies. Pay per call from $0.001 via x402 micropayments.
Multi-account X (Twitter) automation with no X API key: it drives a real Chrome session using your own cookies. 33 tools for posting, replies, keyword search, engagement, single-tweet reads that return images as MCP content, per-account personas, proxy pools, and a persistent scheduled-action queue. Draft-approval mode is on by default, so write tools return a draft and nothing goes live until you call approvedraft. Listed on the official MCP Registry. Install: pip install x-use-mcp, then x-use init and x-use mcp.
Quality signal
45/100 (Fair)
49/100 (Fair)
Install path
npx · high
npx · high
Engagement
3 0 0 15
1 0 0 153
Tools
247 Twitter/X tools covering reading, posting, engagement, and mediaSupports MCP stdio, REST API with x402 micropayments, and ACP protocolsNo Twitter API keys or developer account requiredUses browser cookies or encrypted credentials for authenticationPay-per-call pricing with resource-based billing cheaper than official X APILocal execution for MCP with auto-detected cookies and stateless REST server
