In-depth architectural comparison of the TwitterAPIs 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
TwitterAPIs
Social Media · Local stdio
Quality: 52/100 (Good) | Auth: No auth required
Posteverywhere MCP
Social Media · Local stdio
Quality: 64/100 (Good) | Auth: API Key required
Verdict Summary: Choose TwitterAPIs 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 TwitterAPIs 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).
Official MCP server for twitterapis.com. Read and write Twitter/X: search, users, tweets, DMs.
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.
Search tweets with X operators (`from:`, `min_faves:`, `since:`, `filter:links`, etc.)
twitter_user_search
Find user accounts by name or keyword
twitter_user_info
Full profile by handle (bio, counts, verification, location)
twitter_user_info_by_id
Full profile by numeric user id
twitter_user_status
Is an account alive, suspended, or deleted
twitter_user_about
A user's structured About object (category, professional/business labels, verification + identity-verification flags, joined date, and X's 'About this account' transparency panel)
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).
TwitterAPIs is categorized under Social Media and uses a local stdio subprocess. In contrast, Posteverywhere MCP belongs to Social Media using local stdio subprocess. Select TwitterAPIs when you need capabilities focused on social media and Posteverywhere MCP when you require tools for social media.
Follow relationship between two user ids (who follows whom)
twitter_user_tweets
A user's recent original tweets (replies excluded)
twitter_user_tweets_and_replies
A user's full timeline (tweets + replies)
twitter_user_tweets_complete
A large batch of a user's tweet history per call (see [paging note](#paging-twitter_user_tweets_complete))
twitter_user_media
Images and videos a user has posted
+68 more tools listed on main page
Posteverywhere MCP Tools (15)
list_accounts
list all connected social accounts and their health status
get_account
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