Twitter Username Chan… vs Posteverywhere MCP | AllMCPs
Side-by-Side Model Context Protocol Comparison
Twitter Username Changes MCP vs Posteverywhere MCP
In-depth architectural comparison of the Twitter Username Changes MCP and Posteverywhere MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Twitter Username Changes MCP
Social Media · Local stdio
Quality: 28/100 (Emerging) | Auth: No auth required
Posteverywhere MCP
Social Media · Local stdio
Quality: 64/100 (Good) | Auth: API Key required
Verdict Summary: Choose Twitter Username Changes MCP if you need specialized Social Media tools running via a local process. Choose Posteverywhere MCP if your workspace requires Social Media integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Twitter Username Changes MCP when:
You need dedicated capabilities in the Social Media domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: Historical username lookup by current screen name, query_username_changes tool, Prompt template for query formulation.
An MCP server that tracks the historical changes of Twitter usernames.
Hosted MCP server to schedule and publish across 11 social platforms (Instagram, LinkedIn, TikTok, X, YouTube, Facebook, Threads, Pinterest, Bluesky, Discord, Telegram). 32 tools covering posts, campaigns, bulk operations, media, analytics, webhooks, and AI captions. Connect with one URL, or run locally via npx -y @posteverywhere/mcp.
Category & Scope
Tools & Capabilities Breakdown
Twitter Username Changes MCP Tools (5)
Historical username lookup by current screen name
query_username_changes tool
Prompt template for query formulation
Python 3.10+ support
Minimal dependencies using mcp and requests
Posteverywhere MCP Tools (15)
list_accounts
list all connected social accounts and their health status
get_account
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Twitter Username Changes MCP is categorized under Social Media and uses a local stdio subprocess. In contrast, Posteverywhere MCP belongs to Social Media using local stdio subprocess. Select Twitter Username Changes MCP when you need capabilities focused on social media and Posteverywhere MCP when you require tools for social media.
get details for a specific account (token expiry, can-post status)
list_posts
list posts filtered by status (`scheduled`, `published`, `failed`, `draft`) or platform. Drafts include their target accounts + per-platform content so you can review them before publishing.
get_post
get full details for a single post including all destinations (for drafts, the saved accounts + per-platform content)
create_post
publish now, schedule for later, **or save as a draft for human review** (`draft: true`)
schedule_post
publish or schedule a **draft** (the approval step — pass `scheduled_for`, or `publish_now: true`)
update_post
modify a scheduled or draft post (content, schedule time, accounts)
delete_post
delete a scheduled or draft post
get_post_results
per-platform publishing results, errors, and live URLs