Git 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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_staged_filesC | Retrieve the list of staged files in a git repository |
| get_diffC | Retrieve the diff of staged files in a git repository |
| get_file_contentA | Retrieve the content of a file in a git repository. Use it when the diff doesn't provide enough context. |
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 3 tools
The tools have distinct purposes: get_diff retrieves diff content, get_file_content provides full file content for context, and get_staged_files lists staged files. While get_diff and get_file_content could be confused for overlapping file content retrieval, the descriptions clarify that get_file_content is for supplemental context when diff is insufficient, maintaining reasonable separation.
All tool names follow a consistent verb_noun pattern with 'get_' prefix: get_diff, get_file_content, get_staged_files. This uniformity makes the tool set predictable and easy to understand, with no deviations in naming style.
With only 3 tools, the set feels thin for a code review domain, which typically involves more operations like commenting, approving, or managing reviews. While the tools cover basic retrieval needs, the count is borderline low for the apparent scope, limiting functionality.
The tool set is severely incomplete for code review workflows. It only provides retrieval operations (get_diff, get_file_content, get_staged_files) but lacks essential actions like creating comments, submitting reviews, or managing pull requests. This creates significant gaps that will cause agent failures in performing full code review tasks.