Log inSubmit server
Codereviewbuddy logo

Codereviewbuddy

Manage GitHub pull-request reviews, CI checks, comment threads, and stacked-PR activity through MCP tools.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Codereviewbuddy

Pick your client, then add it in one click or paste the config.

STDIOPython
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "codereviewbuddy": {
      "command": "uvx",
      "args": [
        "codereviewbuddy"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

We couldn’t confirm it starts correctly

We ran the install command but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

uvx codereviewbuddy

No response to initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 19d ago.

Overview

The codereviewbuddy MCP server connects AI coding agents to GitHub pull-request review infrastructure through the GitHub CLI. It provides tools for summarizing review status, triaging actionable threads, retrieving conversation history, replying to comments, and checking or diagnosing CI. Stack activity, unresolved threads on merged PRs, PR description quality, and active configuration are also available. Reach for it when an agent needs a structured workflow for reviewing, fixing, and verifying GitHub pull requests.

Use cases

  • Triage actionable review threads before editing code
  • Reply to GitHub reviewer and bot comments
  • Diagnose failed CI runs and extract error lines
  • Check whether a PR stack is settled before proceeding
  • Audit merged PRs for unresolved review threads

Key features

  • GitHub review comment triage and replies
  • Structured PR and CI status tools
  • Stack activity timeline with settled state
  • PR description quality checks
  • Recovery guidance and next-action hints
  • Typed FastMCP output schemas

Tools10

What Codereviewbuddy lets your agent do. Expand a tool for its parameters.

Self-reported~210 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

Not checked yetLast checked Today

We have not completed a health check for this listing yet.

0/12 checks healthy over the last 57d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 16d ago via OSV.dev · codereviewbuddy (PyPI)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

Last commit5mo agoMost recent push to the default branch.
Install checkInconclusiveDidn't respond in our test window — often a slow first install.
Tools exposed10Callable tools this server registers over MCP.
Directory activity2 viewsConfig copies, upvotes, and views on AllMCPs.

How Codereviewbuddy works

What codereviewbuddy MCP server does

The codereviewbuddy MCP server gives AI coding agents structured access to GitHub pull-request review work. It covers review status, actionable inline comments, thread history, replies, CI results, stacked-PR activity, and selected pull-request hygiene checks.

A typical workflow starts with summarize_review_status for a lightweight view across a PR stack. The agent can then use triage_review_comments to find inline threads that still need action, followed by get_thread for complete conversation history. reply_to_comment supports inline review threads, PR-level reviews, and bot issue comments by routing each identifier type to the corresponding GitHub API operation.

The server also handles review follow-up outside the current PR. list_recent_unresolved scans recently merged pull requests for review threads that were not resolved, while review_pr_descriptions checks for issues such as an empty body, boilerplate content, or missing linked issues.

How it works

The codereviewbuddy MCP server runs through FastMCP and returns typed Pydantic models with JSON Schema rather than unstructured tool output. It uses the local gh CLI for GitHub authentication, so a personal access token or .env file is not required by the server. Before starting it, install and authenticate GitHub CLI with gh auth login.

Project context is detected from MCP roots sent by the client. This allows separate client windows to work with different projects without adding a repository environment variable. Tool responses can include next_steps, explanations for empty results, direct GitHub comment URLs, and recovery guidance for authentication, rate-limit, missing-resource, workspace, GraphQL, or configuration errors.

The server also exposes a read-only review resource at pr://{owner}/{repo}/{pr_number}/reviews. Its prompts include review_stack, pr_review_checklist, and ship_stack for guided review and pre-merge workflows.

Setup and configuration

Python 3.14 or newer, uv, and an authenticated GitHub CLI installation are required. The simplest launch command is:

bash
uvx codereviewbuddy@latest

Permanent installation is available with uv tool install codereviewbuddy. The project includes an installer for Claude Desktop, Claude Code, Cursor, and Windsurf, plus a command that prints or copies generic MCP JSON configuration. Restart the client after changing its MCP configuration.

Configuration is optional. Settings use CRB_* environment variables in the MCP client's env block, with double underscores separating nested settings. Supported examples include CRB_OWNER_LOGINS, CRB_PR_DESCRIPTIONS__ENABLED, and CRB_SELF_IMPROVEMENT__ENABLED.

Tools and capabilities

The codereviewbuddy MCP server exposes these tools:

  • summarize_review_status and stack_activity provide overview and chronological stack information; stack_activity includes a settled flag.
  • triage_review_comments filters for actionable inline threads and supplies GitHub URLs.
  • get_thread retrieves a full thread by node ID.
  • reply_to_comment replies to inline, PR-level, or bot comments.
  • diagnose_ci identifies failed runs, jobs, steps, and error lines in one call.
  • check_ci_status reports whether a PR's CI is passing, failing, or pending.
  • list_recent_unresolved finds unresolved review threads on recently merged PRs.
  • review_pr_descriptions checks pull-request description quality.
  • show_config displays active settings with explanations.

FastMCP also provides progress reporting where supported by the client, plus middleware for error handling, timing logs, and request/response logging.

Limitations and notes

The server depends on GitHub CLI authentication and a compatible local Python runtime. It is designed around GitHub's pull-request review infrastructure, so its comment operations use GitHub identifier formats such as PRRT_, PRR_, and IC_. Client support for progress display, structured output, tool filtering, or other FastMCP features may vary.

When using a locally checked-out source version, launch it with uv run --directory so the client uses the repository's dependencies. If FastMCP reports a missing fastmcp.server.tasks.routing module, the documented remedies are to use codereviewbuddy@latest, run from the source checkout with uv, or reinstall the tool to refresh cached dependencies.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Codereviewbuddy

codereviewbuddy is an MCP server that connects AI coding agents to GitHub pull-request review infrastructure through the gh CLI. Its main tools summarize review status, triage and retrieve threads, reply to comments, check or diagnose CI, and inspect stack activity, unresolved threads, descriptions, and configuration.

Install it with `uvx codereviewbuddy@latest` or permanently with `uv tool install codereviewbuddy`. The included installer can configure Claude Desktop, Claude Code, Cursor, and Windsurf, or generate generic MCP JSON configuration.

codereviewbuddy uses the GitHub CLI for authentication, so no personal access token or `.env` file is required. Install `gh` and complete `gh auth login` before starting the MCP server.

Yes, codereviewbuddy provides an installer command for Cursor. Run `uvx codereviewbuddy install cursor`, then restart the MCP client after installation.

Use `diagnose_ci` to locate the failed run, identify failed jobs and steps, and extract error lines in one call. Use `check_ci_status` when you only need a pass, fail, or pending result before merging.

Related MCP servers

All in Version Control All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewCodereviewbuddy AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/codereviewbuddy?style=directory)](https://allmcps.com/mcp/codereviewbuddy)
HTML Embed
<a href="https://allmcps.com/mcp/codereviewbuddy"><img src="https://allmcps.com/api/badge/codereviewbuddy?style=directory" alt="Codereviewbuddy on AllMCPs" /></a>