Repocrunch vs Netdata
A side-by-side look at the Repocrunch and Netdata MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Repocrunch for monitoring work as a local process; choose Netdata for monitoring. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Repocrunch when
- You need dedicated capabilities in the Monitoring domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Monitoring | Monitoring |
| Quality signal | 47/100 · Fair | 41/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 | 9 | 81,060 |
| Directory activity | 2 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Repocrunch | View Netdata |
Tools & capabilities
Repocrunch tools
No tool names declared yet. Check the project README from the listing page.
Netdata 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.
Repocrunch
{
"mcpServers": {
"kimwwk-repocrunch": {
"command": "uvx",
"args": [
"repocrunch"
]
}
}
}
Netdata
No confirmed install command for Netdata yet — follow the setup steps linked from its listing page rather than a guessed package name.