Antwork vs Posteverywhere MCP
A side-by-side look at the Antwork 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 Antwork for social media work over a hosted endpoint; 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 Antwork when
- You need dedicated capabilities in the Social Media domain.
- You prefer a remote HTTP/SSE transport.
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 | 40/100 · Fair | 65/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | Freemium |
| Required env vars | None listed | POSTEVERYWHERE_API_KEY |
Tools & capabilities
Antwork tools
No tool names declared yet. Check the project README from the listing page.
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.
Antwork
{
"mcpServers": {
"antwork-2": {
"url": "https://api.antwork.io/mcp"
}
}
}
Posteverywhere MCP
{
"mcpServers": {
"posteverywhere-mcp": {
"command": "npx",
"args": [
"-y",
"@posteverywhere/mcp"
],
"env": {
"POSTEVERYWHERE_API_KEY": "YOUR_POSTEVERYWHERE_API_KEY_HERE"
}
}
}
}
Frequently asked questions
Antwork is categorized under Social Media and uses a remote HTTP/SSE transport. Posteverywhere MCP belongs to Social Media and uses a local stdio subprocess. Pick Antwork 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.
Antwork 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 antwork-2 and posteverywhere-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Antwork has a quality signal of 40/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Posteverywhere MCP has 65/100 (Great) with 4 views, 0 installs and 4 GitHub stars.