A side-by-side look at the Antwork and PostLake 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 PostLake for social media over a hosted endpoint. You can also run both side by side in one mcpServers block.
POSTLAKE_API_KEY.Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Social Media | Social Media |
| Quality signal | 40/100 · Fair | 41/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Remote HTTP/SSE |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | POSTLAKE_API_KEY |
| Verified owner | Community listing |
No tool names declared yet. Check the project README from the listing page.
No tool names declared yet. Check the project README from the listing page.
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.
{
"mcpServers": {
"antwork-2": {
"url": "https://api.antwork.io/mcp"
}
}
}
{
"mcpServers": {
"postlake": {
"url": "https://api.postlake.dev/mcp"
}
}
}
| GitHub stars | 0 | 2 |
|---|
| Directory activity | 0 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
|---|
| Tools | Not listed | Not listed |
|---|
| Full listing | View Antwork | View PostLake |
|---|