Skip to main content
Glama
AI Code Review MCP Server

AI Code Review MCP Server

AI Code Review MCP Server

Simple MCP server for GitHub and FileSystem integration with AI agents (Copilot, Claude, etc.)

πŸš€ Quick Start

1. Install Dependencies

npm install

2. Test MCP Server

node src/index.js

3. Use with Copilot

  1. Restart VS Code (close and reopen)

  2. Open Copilot Chat and ask:

    • "List my GitHub repositories"

    • "Show pull requests in owner/repo"

    • "Read README.md file"

    • "List files in current directory"

Related MCP server: GitHub MCP Server

πŸ› οΈ Available Tools

GitHub Tools

  • github_list_repos - List your repositories

  • github_list_prs - List pull requests

  • github_get_pr - Get PR details

  • github_get_pr_diff - Get PR diff for review

FileSystem Tools

  • fs_read_file - Read file contents

  • fs_list_files - List directory contents

  • fs_search_files - Search files by pattern

βš™οΈ Configuration

Edit .mcp/config.json:

{
  "mcpServers": {
    "ai-code-review": {
      "env": {
        "GITHUB_PERSONAL_ACCESS_TOKEN": "your_token_here",
        "WORKSPACE_PATH": "/path/to/workspace"
      }
    }
  }
}

πŸ“ Usage Examples

With Copilot Chat:

  • "List my GitHub repositories"

  • "Show me PR #123 in owner/repo"

  • "Read the package.json file"

With Other Agents:

The MCP server implements Model Context Protocol, compatible with:

  • GitHub Copilot

  • Claude Desktop

  • Any MCP-compatible AI agent

πŸ”’ Security

  • GitHub token stored in config (add .mcp/ to .gitignore)

  • FileSystem access restricted to workspace path

  • Path traversal protection built-in

Available Tools

7 tools
fs_list_filesC

List files in a directory

Inputs: path.

fs_read_fileC

Read file contents from workspace

Inputs: path (required).

fs_search_filesC

Search for files by pattern (e.g., *.js, *.py)

Inputs: pattern (required), path.

github_get_prC

Get pull request details

Inputs: owner (required), repo (required), pr_number (required).

github_get_pr_diffC

Get pull request diff for code review

Inputs: owner (required), repo (required), pr_number (required).

github_list_prsC

List pull requests in a repository

Inputs: owner (required), repo (required), state.

github_list_reposC

List GitHub repositories for authenticated user

Inputs: per_page.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3/5.0

    Scored across 7 tools

    Disambiguation4/5

    The tools are mostly distinct with clear purposes, but there is some potential overlap between fs_list_files and fs_search_files, as both involve listing files, which could cause minor confusion. However, their descriptions clarify that one lists all files while the other searches by pattern, helping to mitigate ambiguity.

    Naming Consistency3/5

    The naming is mixed, with fs_* tools using a prefix and github_* tools using a different prefix, but within each group, the verb_noun pattern is consistent (e.g., fs_list_files, github_get_pr). This mixed convention reduces overall consistency, though it remains readable and functional.

    Tool Count4/5

    With 7 tools, the count is reasonable for an AI code review server, covering file system operations and GitHub PR interactions. It is slightly lean but well-scoped, as each tool serves a specific purpose without obvious bloat or redundancy.

    Completeness3/5

    The tool surface has notable gaps for a code review domain, such as missing tools for creating or updating PRs, commenting on code, or analyzing code quality directly. While it covers basic file and PR retrieval, it lacks full lifecycle coverage, which could limit agent effectiveness in comprehensive code review workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables AI assistants to interact with local Git repositories for operations like status, commits, branching, and diffs, plus GitHub API integration for managing pull requests when authenticated.
      -
    • A
      license
      A
      quality
      Not graded
      maintenance
      Enables AI agents to interact with GitHub repositories through the GitHub REST API for managing files, issues, and repository metadata. It supports both read operations like searching code and write operations such as creating repositories and updating issue comments.
      9
      -
    • A
      license
      B
      quality
      D
      maintenance
      Enables AI assistants to inspect local Git repositories and interact with the GitHub API for reading commits, diffs, files, issues, comments, pull requests, and project boards.
      10
      133 npm
      ISC