TypeUI vs Voxplo
A side-by-side look at the TypeUI 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 TypeUI for architecture & design work as a local process; choose Voxplo for communication. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose TypeUI when
- You need dedicated capabilities in the Architecture & Design domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | V Voxplo | |
|---|---|---|
| Category | Architecture & Design | Communication |
| Quality signal | 47/100 · Fair | 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 | 2,134 | — |
| Directory activity | 2 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View TypeUI | View Voxplo |
Tools & capabilities
TypeUI 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.
TypeUI
{
"mcpServers": {
"typeui": {
"command": "npx",
"args": [
"-y",
"typeui.sh"
]
}
}
}
Voxplo
No confirmed install command for Voxplo yet — follow the setup steps linked from its listing page rather than a guessed package name.