Posteverywhere MCP vs SocialHive
A side-by-side look at the Posteverywhere MCP and SocialHive MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Posteverywhere MCP for social media work as a local process; choose SocialHive for social media over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Posteverywhere MCP when
- You need dedicated capabilities in the Social Media domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
POSTEVERYWHERE_API_KEY. - You want tools like
list_accounts, get_account, list_posts.
Choose SocialHive when
- You need dedicated capabilities in the Social Media domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
list_channels, get_connected_social_accounts, list_posts.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Social Media | Social Media |
| Quality signal | 67/100 · Great | 57/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | API key required | Not declared |
| Pricing | Freemium | Not declared |
| Required env vars | POSTEVERYWHERE_API_KEY | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 5 | 0 |
| Directory activity | 4 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 15 | 24 |
| Full listing | View Posteverywhere MCP | View SocialHive |
Tools & capabilities
Posteverywhere MCP tools 15
list_accountslist all connected social accounts and their health statusget_accountget details for a specific account (token expiry, can-post status)list_postslist 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_postget full details for a single post including all destinations (for drafts, the saved accounts + per-platform content)create_postpublish now, schedule for later, **or save as a draft for human review** (`draft: true`)schedule_postpublish or schedule a **draft** (the approval step — pass `scheduled_for`, or `publish_now: true`)update_postmodify a scheduled or draft post (content, schedule time, accounts)delete_postdelete a scheduled or draft postget_post_resultsper-platform publishing results, errors, and live URLsretry_failed_postretry every failed destination of a postlist_medialist files in your media libraryget_mediaget media file details and processing status- +3 more on the listing page
SocialHive tools 24
list_channelsList the social accounts connected to this workspace with their ids, platform, handle, health, and automationEnabled status. Use channel ids when creating posts.get_connected_social_accountsGet all connected social media accounts (LinkedIn, X, YouTube, Instagram, Facebook, TikTok, Threads) for the workspace with account IDs, platforms, connection status, and automationEnabled status.list_postsList posts in the workspace, newest first. Filter by status (draft, pending_approval, scheduled, published, failed) or free text.get_postGet one post with its body, per-channel variants, status and metrics.list_articlesList long-form articles in the workspace library with their id, title, status, word count, summary, and last updated time.get_articleGet full details and Markdown body of an article in the workspace library by its ID.get_analyticsWorkspace performance for the last N days: impressions, engagements, posts, follower change, top posts and recommended posting slots.list_sourcesList content data sources (RSS feeds, sitemaps, web pages, documents) with counts of unused items.search_source_itemsFetch recent items from one data source (title, url, excerpt). Use them as raw material for posts.list_workflowsList automation workflows with status and last run.list_node_typesCatalog of workflow node types (triggers, sources, AI, control, destinations) with their config schemas. Read before calling propose_workflow.generate_textWrite social copy in the workspace brand voice. Returns one or more variants. Metered (free daily allowance, then 1 credit).- +12 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Posteverywhere MCP
{
"mcpServers": {
"posteverywhere-mcp": {
"command": "npx",
"args": [
"-y",
"@posteverywhere/mcp"
],
"env": {
"POSTEVERYWHERE_API_KEY": "YOUR_POSTEVERYWHERE_API_KEY_HERE"
}
}
}
}
SocialHive
{
"mcpServers": {
"socialhive": {
"url": "https://platform.socialhive.pro/api/mcp"
}
}
}
Frequently asked questions
Posteverywhere MCP is categorized under Social Media and uses a local stdio subprocess. SocialHive belongs to Social Media and uses a remote HTTP/SSE transport. Pick Posteverywhere MCP for social media work and SocialHive for social media.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Posteverywhere MCP is listed as freemium — a free tier with paid plans. Auth: api key required. SocialHive has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add posteverywhere-mcp and socialhive as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Posteverywhere MCP has a quality signal of 67/100 (Great) with 4 views, 0 installs and 5 GitHub stars. SocialHive has 57/100 (Good) with 0 views, 0 installs and 0 GitHub stars.