Auto Reviewers MCP Server

A Model Context Protocol (MCP) server that exposes auto-reviewer functionality for GitLab merge requests.

Installation

Install the package from npm:

npm install auto-reviewers-mcp-server

Quick Start

After installation, you can run the server directly:

node node_modules/auto-reviewers-mcp-server/dist/index.js

Or add it to your MCP configuration (see Integration section below).

Features

• suggest_reviewers: Automatically suggest reviewers based on contributors, team members, and code owners
• get_contributor_analysis: Analyze file contributors using git blame data
• get_reviewer_workload: Get current workload analysis for potential reviewers

Development Setup

For development or building from source:

1. Install dependencies:

npm install

2. Build the server:

npm run build

3. Configure environment (optional):

cp .env.example .env
# Edit .env with your GitLab URL and token

4. Run the server:

npm start

Configuration

The server requires a GitLab API token. You can provide it in two ways:

1. Environment variable: Set GITLAB_TOKEN in your environment or .env file
2. Tool parameter: Pass gitlabToken when calling the tool

Optionally set GITLAB_URL (defaults to https://gitlab.com).

Tools

suggest_reviewers

Suggests reviewers for a GitLab merge request based on:

• Git blame analysis of changed files to find previous contributors
• Team member availability with FTE-aware load balancing
• Code ownership rules from CODEOWNERS file
• Current reviewer workload across open merge requests

Parameters:

• projectId (number): GitLab project ID
• mergeRequestIid (number): Merge request internal ID
• authorUsername (string): Username of the MR author
• gitlabToken (string, optional): GitLab API token
• gitlabUrl (string, optional): GitLab instance URL

Returns:

• List of contributor reviewers with change details
• Team member suggestions with load balancing scores
• Code owner assignments by section
• Formatted comment for GitLab MR

get_contributor_analysis

Provides detailed analysis of who contributed to the changed files using git blame.

Parameters:

• projectId (number): GitLab project ID
• mergeRequestIid (number): Merge request internal ID
• gitlabToken (string, optional): GitLab API token
• gitlabUrl (string, optional): GitLab instance URL

Returns:

• List of changed files
• Contributors per file with line counts

get_reviewer_workload

Analyzes current workload of potential reviewers across open merge requests.

Parameters:

• projectId (number): GitLab project ID
• gitlabToken (string, optional): GitLab API token
• gitlabUrl (string, optional): GitLab instance URL

Returns:

• List of reviewers with open MR counts

Integration

To use this MCP server with an AI assistant, add it to your MCP configuration:

{
  "mcpServers": {
    "auto-reviewers": {
      "command": "node",
      "args": ["node_modules/auto-reviewers-mcp-server/dist/index.js"],
      "env": {
        "GITLAB_TOKEN": "your_token_here",
        "GITLAB_URL": "https://gitlab.com"
      }
    }
  }
}

If you installed the package globally, you can reference it directly:

{
  "mcpServers": {
    "auto-reviewers": {
      "command": "auto-reviewers-mcp-server",
      "env": {
        "GITLAB_TOKEN": "your_token_here",
        "GITLAB_URL": "https://gitlab.com"
      }
    }
  }
}

Team Configuration

Create a CONTRIBUTORS file in your repository root with team and FTE data:

{
  "contributors": [
    {
      "username": "developer1",
      "email": "[email protected]",
      "teams": [
        { "name": "Backend", "fte": 1.0 },
        { "name": "API", "fte": 0.5 }
      ]
    }
  ]
}

Code Owners

Create a CODEOWNERS file in your repository root (or docs/CODEOWNERS or .gitlab/CODEOWNERS):

# Backend team owns all backend code
/backend/ @backend-team

# API section requires 2 approvals
[API][2] @api-lead
/api/ @developer1 @developer2

Contributing

Contributions are welcome! Please visit the GitHub repository to:

• Report issues or bugs
• Request new features
• Submit pull requests
• View the source code

License

MIT

Support

For issues, questions, or contributions, please visit:

• Issues: GitHub Issues
• Repository: GitHub Repository