1Social vs Posteverywhere MCP
A side-by-side look at the 1Social and Posteverywhere MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose 1Social for social media work as a local process; choose Posteverywhere MCP for social media as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose 1Social when
- You need dedicated capabilities in the Social Media domain.
- You prefer a local stdio subprocess transport.
- You want tools like
list_accounts, preview_post, publish_post.
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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Social Media | Social Media |
| Quality signal | 49/100 · Fair | 67/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | Freemium |
| Required env vars | None listed | POSTEVERYWHERE_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 5 |
| Directory activity | 1 views 0 installs 0 upvotes | 4 views 0 installs 0 upvotes |
| Tools | 10 | 15 |
| Full listing | View 1Social | View Posteverywhere MCP |
Tools & capabilities
1Social tools 10
list_accountsConnected accounts, what each network accepts, current plan, remaining quota. Call it first — channel ids come from here.preview_postFree dry run: per-network limits, media requirements, threading behaviour, quota cost. Nothing is published.publish_postPublishes now, or schedules up to 30 days ahead. Returns a per-network receipt. Takes an `idempotencyKey`.list_postsPosts with their delivery outcome per network — delivered, failed with a reason, cancelled, or `unknown` — plus stored engagement metrics.update_postEdits a post that has not been sent yet. The networks have no edit endpoint, so it withdraws and replaces.cancel_postUnschedules a post and releases the quota it reserved.delete_postDeletes from 1Social and attempts removal from each network. See [What deletion can and cannot do](#what-deletion-can-and-cannot-do).retry_deliveryRetries one failed network, leaving the successful ones alone. Refused for permanent failures.upload_mediaPre-signed upload target, for clients that cannot attach a file to a tool call.confirm_deliveryRecords **your** answer about a delivery whose outcome was unknown: is the post live on that network or not?
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
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.
1Social
{
"mcpServers": {
"1social": {
"command": "npx",
"args": [
"-y",
"@lobehub/market-cli"
]
}
}
}
Posteverywhere MCP
{
"mcpServers": {
"posteverywhere-mcp": {
"command": "npx",
"args": [
"-y",
"@posteverywhere/mcp"
],
"env": {
"POSTEVERYWHERE_API_KEY": "YOUR_POSTEVERYWHERE_API_KEY_HERE"
}
}
}
}
Frequently asked questions
1Social is categorized under Social Media and uses a local stdio subprocess. Posteverywhere MCP belongs to Social Media and uses a local stdio subprocess. Pick 1Social for social media work and Posteverywhere MCP 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.
1Social has no declared pricing — check the project's own site. Posteverywhere MCP is listed as freemium — a free tier with paid plans. Auth: api key required. 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 1social and posteverywhere-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, 1Social has a quality signal of 49/100 (Fair) with 1 views, 0 installs and 0 GitHub stars. Posteverywhere MCP has 67/100 (Great) with 4 views, 0 installs and 5 GitHub stars.