Code Review MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITLAB_URL | No | GitLab instance URL (default: https://gitlab.com). Required for GitLab (Self-Managed). | https://gitlab.com |
| GITHUB_TOKEN | No | Your GitHub Personal Access Token. Required for GitHub functionality. | |
| GITLAB_TOKEN | No | Your GitLab Personal Access Token. Required for GitLab functionality. | |
| CODE_REVIEW_GUIDELINES | No | Inline custom code review guidelines text. Optional (Custom Rules). | |
| CODE_REVIEW_GUIDELINES_FILE | No | Path to a file containing custom code review guidelines. Optional (Custom Rules). If set, it takes precedence over CODE_REVIEW_GUIDELINES. |
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
} |
| prompts | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| gitlab_list_mrsC | List merge requests for a given GitLab project |
| gitlab_get_mr_detailsC | Get details of a specific merge request |
| gitlab_get_mr_diffC | Get the diff of a specific merge request |
| gitlab_read_fileC | Read the content of a file at a specific ref |
| gitlab_get_project_metadataC | Fetch project metadata (README and manifests) |
| github_list_prsC | List pull requests for a given GitHub repository |
| github_get_pr_detailsC | Get details of a specific pull request |
| github_get_pr_diffC | Get the diff of a specific pull request |
| github_read_fileC | Read the content of a file at a specific ref |
| github_get_project_metadataC | Fetch project metadata (README and manifests) |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| review_merge_request | Guided code review for a GitLab Merge Request |
| review_pull_request | Guided code review for a GitHub Pull Request |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 10 tools
The tools are clearly separated by platform (GitHub vs GitLab) and action type (list, get details, get diff, read file, get metadata), with minimal overlap. However, the 'get_project_metadata' and 'read_file' tools could potentially be confused as both involve reading project content, though their specific purposes differ slightly.
All tools follow a consistent pattern of platform_prefix_verb_noun (e.g., github_get_pr_details, gitlab_list_mrs). The naming is perfectly predictable and uses snake_case uniformly throughout the entire toolset.
With 10 tools, the server is well-scoped for code review across two major platforms. Each tool has a clear purpose and contributes to the overall functionality without being excessive or insufficient for the domain.
The toolset provides comprehensive coverage for reading and reviewing code across GitHub and GitLab, including listing, viewing details, diffs, files, and metadata. A minor gap exists in the lack of tools for creating or updating reviews/comments, which are common in code review workflows, but the core review capabilities are well-covered.