GitHub
GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.
Description from the maker (original English)
An LLM-based code review MCP server with AST-powered smart context extraction
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"selvage": {
"command": "uvx",
"args": [
"selvage"
]
}
}
}Run this in your terminal
claude mcp add selvage -- uvx selvagePaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"selvage": {
"command": "uvx",
"args": [
"selvage"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"selvage": {
"type": "stdio",
"command": "uvx",
"args": [
"selvage"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified with the GitHub account selvage-lab, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.4.1) reached the registry 9 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.
In the same category: GitHub, Desktop Commander, Cloudflare MCP
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.
MCP server for terminal commands, file operations, and process management
Cloudflare MCP servers
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Selvage: AI-Powered Code Review Automation Tool
🌐 한국어
A modern CLI tool that helps AI analyze Git diffs to improve code quality, find bugs, and identify security vulnerabilities.
🤖 AI Agents : Read our documentation at https://selvage.ai/llms.txt
▶ Watch Demo Video
Selvage: Code reviews with an edge!
No more waiting for reviews! AI instantly analyzes your code changes to provide quality improvements and bug prevention. With smart context analysis (AST-based) that's accurate and cost-effective, plus multi-turn processing for large codebases - seamlessly integrated with all Git workflows.
Table of Contents
/review skill and selvage-reviewer agent for seamless integrationRecommended Method (using uv)
# Install uv (run once)
curl -LsSf https://astral.sh/uv/install.sh | sh
uv tool install selvage
Alternative Method (using pipx)
# Install pipx (macOS)
brew install pipx
pipx install selvage
Traditional Method (pip)
# ⚠️ May cause externally-managed-environment error on some systems
pip install selvage
macOS/Linux users: If you encounter errors with pip install, please use the uv or pipx methods above.
Get an API key from OpenRouter and set it up:
export OPENROUTER_API_KEY="your_openrouter_api_key_here"
Register as MCP mode in Cursor, Claude Code, etc., to request code reviews through natural language.
Register in Cursor's MCP configuration file (path may vary depending on user environment):
Common path: ~/.cursor/mcp.json
// Method 1: Using environment variables (if already set)
{ "mcpServers": { "selvage": { "command": "uvx", "args": ["selvage", "mcp"] } } }
// Method 2: Direct specification { "mcpServers": { "selvage": { "command": "uvx", "args": ["selvage", "mcp"], "env": { "OPENROUTER_API_KEY": "your_openrouter_api_key_here" } } } }
Install the Selvage plugin from the marketplace to get the dedicated /review skill and selvage-reviewer agent:
# Step 1: Add Selvage marketplace
/plugin marketplace add selvage-lab/selvage
/plugin install selvage@selvage-lab-selvage
After installation, use the /review skill directly:
/review # Review unstaged changes
/review staged # Review staged changes /review branch main # Review against main branch /review commit abc1234 # Review from specific commit
💡 No API key required! The plugin uses
get_review_contextto leverage Claude Code's own LLM for code review, so no external API key is needed.
# Method 1: Using environment variables (if already set)
claude mcp add selvage -- uvx selvage mcp
claude mcp add selvage -e OPENROUTER_API_KEY=your_openrouter_api_key_here -- uvx selvage mcp
After restarting your IDE, request reviews from your Coding Assistant:
Please review current changes using selvage mcp
Review changes between current branch and main branch using claude-sonnet-4-thinking with selvage mcp
🎉 Done! Selvage will analyze the code, review it, and deliver results through your Coding Assistant.
For direct terminal usage:
selvage review --model claude-sonnet-4-thinking
💡 More Options: CLI Usage | Practical Usage Guide
# Basic review request
Please review current changes using selvage mcp
Review staged work using gpt-5-high with selvage mcp
Review current branch against main branch using selvage mcp
Review current branch against main branch using selvage mcp, automatically selecting appropriate model
The get_review_context tool returns structured review context so host agents can perform code reviews with their own LLM — no Selvage API key needed.
# Request agent-delegated review context
Get review context for current changes using selvage mcp, then review the code
Get review context for staged changes using selvage mcp
Get review context comparing current branch to main using selvage mcp
💡 How it works: Selvage extracts diff + AST-based Smart Context + system prompt and returns it as structured context. The host agent (Claude Code, Cursor, Antigravity, etc.) then performs the review directly with its own LLM, without needing an external API key.
Multi-model Comparison Review
Review staged work using both gpt-5-high and claude-sonnet-4-thinking with selvage mcp, then compare the results
Stepwise Code Improvement Workflow
1. Review current changes using claude-sonnet-4-thinking with selvage mcp
CI/CD Integration Scenarios
# Code quality verification before PR creation
Review changes against main branch using selvage mcp for code quality verification before PR creation
Perform comprehensive review of staged changes using selvage mcp for final check before deployment
Direct terminal usage method. While MCP mode is recommended, CLI is useful for scripts and CI/CD.
# View all settings
selvage config list
selvage config model
selvage config language
selvage review [OPTIONS]
--repo-path : Git repository path (default: current directory)--staged: Review only staged changes--target-commit : Review changes from specific commit to HEAD (e.g., abc1234)--target-branch : Review changes between current branch and specified branch (e.g., main)--model : AI model to use (e.g., claude-sonnet-4-thinking)--open-ui: Automatically launch UI after review completion--no-print: Don't output review results to terminal (terminal output enabled by default)--skip-cache: Perform new review without using cache# Review current working directory changes
selvage review
selvage review --staged
git add specific_files.py && selvage review --staged
selvage review --target-branch develop
selvage review --model gemini-2.5-flash
selvage review --target-branch main --open-ui
# Code quality verification before Pull Request creation
selvage review --target-branch main --model claude-sonnet-4-thinking
selvage review --target-branch develop --model claude-sonnet-4-thinking
selvage review --target-commit a1b2c3d --model claude-sonnet-4-thinking
# Quick feedback during development (before WIP commit)
selvage review --model gemini-2.5-flash
selvage review --staged --model claude-sonnet-4-thinking
selvage review --target-branch main --model claude-sonnet-4-thinking
# Large codebases are automatically handled
selvage review --model claude-sonnet-4 # Usage is the same, multi-turn processing automatically applied after detection
Selvage automatically handles large code changes that exceed LLM model context limits. Once usage reaches roughly 200k tokens (tiktoken basis), Large Context Mode starts automatically, so just wait for it to complete.
# Use economical models for small changes
selvage review --model gemini-2.5-flash
Review results are output directly to the terminal and automatically saved to files simultaneously.
For additional review management and re-examination, you can use the web UI:
# Manage all saved review results in web UI
selvage view
Only the beginning is shown; read the rest in the repo