Codereviewbuddy vs Uploads.sh
A side-by-side look at the Codereviewbuddy and Uploads.sh MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Codereviewbuddy for version control work as a local process; choose Uploads.sh for version control as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Codereviewbuddy when
- You need dedicated capabilities in the Version Control domain.
- You prefer a local stdio subprocess transport.
- You want tools like
summarize_review_status, triage_review_comments, get_thread.
Choose Uploads.sh when
- You need dedicated capabilities in the Version Control domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Version Control | Version Control |
| Quality signal | 34/100 · Emerging | 47/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | 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 | 19 |
| Directory activity | 1 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 10 | Not listed |
| Full listing | View Codereviewbuddy | View Uploads.sh |
Tools & capabilities
Codereviewbuddy tools 10
summarize_review_statusLightweight stack-wide overview — start heretriage_review_commentsOnly actionable inline threads needing attentionget_threadFull thread details by node ID — use after triage for conversation historyreply_to_commentReply to inline threads (`PRRT_`), PR-level reviews (`PRR_`), or bot comments (`IC_`)diagnose_ciDiagnose CI failures — finds the failed run, jobs, steps, and error lines in one callcheck_ci_statusLightweight CI pass/fail/pending check for a PR — use before mergingstack_activityChronological activity feed across a PR stack with a `settled` flaglist_recent_unresolvedScan recently merged PRs for unresolved review threadsreview_pr_descriptionsAnalyze PR descriptions for quality issues (empty body, boilerplate, missing linked issues)show_configShow active configuration with human-readable explanation
Uploads.sh 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.
Codereviewbuddy
{
"mcpServers": {
"codereviewbuddy": {
"command": "uvx",
"args": [
"codereviewbuddy"
]
}
}
}
Uploads.sh
{
"mcpServers": {
"uploads-sh": {
"command": "npx",
"args": [
"-y",
"@buildinternet/uploads"
]
}
}
}
Frequently asked questions
Codereviewbuddy is categorized under Version Control and uses a local stdio subprocess. Uploads.sh belongs to Version Control and uses a local stdio subprocess. Pick Codereviewbuddy for version control work and Uploads.sh for version control.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Codereviewbuddy has no declared pricing — check the project's own site. Uploads.sh has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add codereviewbuddy and uploads-sh as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Codereviewbuddy has a quality signal of 34/100 (Emerging) with 1 views, 0 installs and 0 GitHub stars. Uploads.sh has 47/100 (Fair) with 1 views, 0 installs and 19 GitHub stars.