Vexa vs Voxplo
A side-by-side look at the Vexa and Voxplo MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Vexa for communication work over a hosted endpoint; choose Voxplo for communication. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Vexa when
- You need dedicated capabilities in the Communication domain.
- You prefer a remote HTTP/SSE transport.
- You have the keys it needs:
API_KEY, API_BASE, TRANSCRIBE_ENABLED, RUNTIME_BACKEND.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | V Voxplo | |
|---|---|---|
| Category | Communication | Communication |
| Quality signal | 48/100 · Fair | 37/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Remote HTTP/SSE | — |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | API_KEYAPI_BASETRANSCRIBE_ENABLEDRUNTIME_BACKEND | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 2,905 | — |
| Directory activity | 2 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Vexa | View Voxplo |
Tools & capabilities
Vexa tools
No tool names declared yet. Check the project README from the listing page.
Voxplo tools
No tool names declared yet. Check the project README from 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.
Vexa
{
"mcpServers": {
"vexa": {
"url": "https://api.cloud.vexa.ai/bots"
}
}
}
Voxplo
No confirmed install command for Voxplo yet — follow the setup steps linked from its listing page rather than a guessed package name.