Node Code Review MCP

A Node.js implementation of the Model Context Protocol (MCP) server for code review operations, supporting both GitHub and GitLab platforms.

📖 中文文档: README-zh.md | 快速开始 | 功能对比

Features

• 🔍 Fetch pull request/merge request details

• 📄 Get code diffs for PRs or commits

• 💬 Add review comments

• 🔍 Basic code quality analysis

• 🔧 Configurable via command line arguments

• 🌐 Support for both GitHub and GitLab APIs

Installation

Via NPM (when published)

Local Development

Configuration

Environment Variables

Copy env.example to .env and configure:

Command Line Arguments

MCP Configuration

Add to your MCP client configuration (e.g., Claude Desktop):

Using NPX (Recommended)

Using Local Installation

For GitLab

Available Tools

fetch_pull_request

Fetch pull request/merge request details.

Parameters:

• repository (string): Repository in format "owner/repo" or GitLab project path like "group/project" (aliases: projectId, project_path)

• pullRequestNumber (number): Pull request number

• provider (string, optional): "github" or "gitlab" (default: "gitlab")

fetch_code_diff

Fetch code diff for a pull request or commit.

Parameters:

• repository (string): Repository in format "owner/repo" or GitLab project path like "group/project"

• pullRequestNumber (number, optional): Pull request number

• commitSha (string, optional): Commit SHA

• filePath (string, optional): Specific file path to get diff for

• provider (string, optional): "github" or "gitlab" (default: "gitlab")

add_review_comment

Add a review comment to a pull request.

Parameters:

• repository (string): Repository in format "owner/repo" or GitLab project path like "group/project"

• pullRequestNumber (number): Pull request number

• body (string): Comment body

• filePath (string, optional): File path for line comment

• line (number, optional): Line number for line comment

• provider (string, optional): "github" or "gitlab" (default: "gitlab")

analyze_code_quality

Analyze code quality and provide suggestions with detailed metrics.

Parameters:

• code (string): Code content to analyze

• language (string): Programming language (javascript, typescript, python, java, go, etc.)

• rules (array, optional): Specific rules to check

get_repository_info

Get repository information.

Parameters:

• repository (string): Repository in format "owner/repo" or GitLab project path like "group/project"

• provider (string, optional): "github" or "gitlab" (default: "gitlab")

analyze_files_batch

Analyze multiple files for code quality issues.

Parameters:

• files (array): Array of file objects with path, content, and language properties

• rules (array, optional): Specific rules to apply to all files

get_pull_request_files

Get list of files changed in a pull request.

Parameters:

• repository (string): Repository in format "owner/repo" or GitLab project path like "group/project"

• pullRequestNumber (number): Pull request number

• provider (string, optional): "github" or "gitlab" (default: "gitlab")

get_supported_languages

Get list of supported programming languages for code analysis.

get_language_rules

Get available analysis rules for a specific language.

Parameters:

• language (string): Programming language

get_server_config

Get current server configuration and health status.

create_merge_request 🆕

Create a new GitLab merge request from a source branch with enhanced error handling.

Parameters:

• projectId (string): GitLab project ID or path

  • Numeric ID (recommended): "12345"

  • Project path: "group/project" or "group/subgroup/project"

• sourceBranch (string): Source branch name (e.g., "feature/new-feature")

• targetBranch (string, optional): Target branch name (defaults to "main")

• title (string, optional): Merge request title (auto-generated from branch name if not provided)

• description (string, optional): Merge request description

• assigneeId (number, optional): User ID to assign the merge request to

• reviewerIds (array, optional): Array of user IDs to request reviews from

• deleteSourceBranch (boolean, optional): Whether to delete source branch when MR is merged

• squash (boolean, optional): Whether to squash commits when merging

Enhanced Error Handling:

• Project ID validation with detailed error messages

• Automatic project verification before MR creation

• Comprehensive troubleshooting guidance for common errors (404, 401, 403, etc.)

• Support for both numeric IDs and project paths

Example:

Auto-generated Titles: The tool automatically generates conventional commit-style titles based on branch prefixes:

• feature/ → feat:

• bugfix/ → fix:

• hotfix/ → fix:

• docs/ → docs:

• refactor/ → refactor:

get_current_branch 🆕

Get current Git branch and repository information.

Parameters:

• workingDirectory (string, optional): Working directory path (defaults to current directory)

Example:

Returns:

get_project_info 🆕

Get current GitLab project information from Git remotes.

Parameters:

• workingDirectory (string, optional): Working directory path (defaults to current directory)

• remoteName (string, optional): Git remote name (defaults to "origin")

Example:

Returns:

API Token Setup

GitHub

1. Go to GitHub Settings > Developer settings > Personal access tokens

2. Generate a new token with appropriate permissions:

   • repo scope for private repositories

   • public_repo scope for public repositories only

GitLab

1. Go to GitLab User Settings > Access Tokens

2. Create a personal access token with:

   • api scope for full API access

   • read_api scope for read-only access

Development

License

MIT License - see LICENSE file for details.