A side-by-side look at the Postbase and Fetchwire Social Data MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Postbase for social media work as a local process; choose Fetchwire Social Data for social media. You can also run both side by side in one mcpServers block.
Rows where the two servers differ are marked.
| Spec | P Postbase | F Fetchwire Social Data |
|---|---|---|
| Category | Social Media | Social Media |
| Quality signal | 33/100 · Emerging | 37/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | — | — |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Postbase | View Fetchwire Social Data |
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": {
"postbase": {
"command": "npx",
"args": [
"@postbasehq/mcp"
]
}
}
}
No confirmed install command for Fetchwire Social Data yet — follow the setup steps linked from its listing page rather than a guessed package name.