code-review-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| analyze_fileA | 分析单个文件的代码质量、复杂度和安全问题。 会运行所有适用的规则：
Args: file_path: 要分析的文件路径（相对于项目根目录或绝对路径） |
| review_diffA | 审查当前 git 仓库中未提交的变更（staged + unstaged）。 对 diff 中的新增行做以下检测：
|
| check_projectA | 扫描项目目录的代码质量概况。 遍历项目下所有支持的源代码文件（Python/JS/TS/Java/Go/Rust 等）， 对每个文件运行完整规则集，最后汇总：
Args: directory: 要扫描的项目目录路径，默认为当前目录 |
| list_rulesA | 列出所有已注册的代码审查规则，便于 AI 选择性调用。 返回每条规则的 ID、名称、描述、类别和默认严重级别。 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool targets a distinct aspect of code review: single file analysis, full project scan, listing rules, and diff review. No functional overlap.
All tool names follow a consistent verb_noun pattern with underscores (analyze_file, check_project, list_rules, review_diff), making them predictable.
4 tools is concise and well-scoped for a code review server, covering all essential operations without excess.
Covers single file analysis, project-wide scanning, rule listing, and diff review. Missing a tool to fetch raw file content, but that is a minor gap for the intended domain.