Code Review

Created By
Orcus2021a year ago
A MCP tool that automates code review and leaves comments directly on GitHub PRs, with support for Notion integration for custom review guidelines.
Overview

Code Review MCP Tool

This tool is a Model Context Protocol (MCP) server that provides automated code review and leaves GitHub PR comments for any app that supports MCP integration.

Features

  • Compare code differences between two git branches

  • Compare code differences from GitHub pull request URLs

  • Add summary comments to GitHub pull requests

  • Add line-specific comments to GitHub pull requests

  • Provide detailed code review guidelines

  • Support Notion integration to retrieve review guidelines from Notion code blocks, with default guidelines as fallback Include pre-configured style and code review guidelines

Usage

Local Git Branch Review

In your MCP-compatible app, send the following command:

code review
base branch: branch/any_branch

GitHub PR Review

In your MCP-compatible app, send the following command:

code review
https://github.com/owner/repo/pull/123

After generating the review report, please:

1.  Add PR summary comment
2.  If individual files require suggested changes, use line comments.

Find all the details here: https://github.com/Orcus2021/code-review-mcp-server

Server Config

{
  "mcpServers": {
    "code-review": {
      "command": "npx",
      "args": [
        "-y",
        "code-review-mcp-server"
      ],
      "env": {
        "GITHUB_TOKEN": "github_token",
        "NOTION_API_KEY": "notion_api_key",
        "NOTION_CODE_REVIEW_GUIDELINE_CODE_BLOCK_URL": "notion_code_block_url_here",
        "NOTION_STYLE_GUIDELINE_CODE_BLOCK_URL": "notion_code_block_url_here",
        "IGNORE_PATTERNS": "pattern1,pattern2,pattern3"
      }
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Orcus2021
Star
-
Language
-
License
-
Category

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago