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.
MCP server for Substack — read posts, manage drafts, publish Notes, get comments, and upload images. Safe by design: cannot publish or delete posts.
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
44/100 (Fair)
49/100 (Fair)
Install path
Remote · high
npx · high
Engagement
4 0 0 16
1 0 0 153
Tools
Read published posts, drafts, comments, sections, and analyticsCreate and update draft posts (private, no publish or delete)Publish short-form Notes immediately (no draft state)Upload images returning publicly accessible CDN URLsList scheduled posts (read-only, scheduling manual in Substack)
