A side-by-side look at the Matrix — MAPPING and McuBuddy MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Matrix — MAPPING for embedded system work; choose McuBuddy for embedded system as a local process. You can also run both side by side in one mcpServers block.
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Embedded System | Embedded System |
| Quality signal | 29/100 · Emerging | 40/100 · Fair |
| Install command | Not confirmed yet | Confirmed |
| 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 | 0 | 8 |
| Directory activity | 0 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Matrix — MAPPING | View McuBuddy |
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.
No confirmed install command for Matrix — MAPPING yet — follow the setup steps linked from its listing page rather than a guessed package name.
{
"mcpServers": {
"mcubuddy": {
"command": "uvx",
"args": [
"McuBuddy"
]
}
}
}