Maguyva vs Codehelper
A side-by-side look at the Maguyva and Codehelper MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Maguyva for developer tools work as a local process; choose Codehelper for developer tools. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Maguyva when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
MAGUYVA_API_KEY.
Choose Codehelper when
- You need dedicated capabilities in the Developer Tools domain.
- Its auth model fits you: No auth required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 40/100 · Fair | 35/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | MAGUYVA_API_KEY | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 3 | 2 |
| Directory activity | 0 views 0 installs 0 upvotes | 4 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Maguyva | View Codehelper |
Tools & capabilities
Maguyva tools
No tool names declared yet. Check the project README from the listing page.
Codehelper 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.
Maguyva
{
"mcpServers": {
"maguyva": {
"command": "npx",
"args": [
"-y",
"@maguyva/mcp"
],
"env": {
"MAGUYVA_API_KEY": "YOUR_MAGUYVA_API_KEY_HERE"
}
}
}
}
Codehelper
No confirmed install command for Codehelper yet — follow the setup steps linked from its listing page rather than a guessed package name.