Code Review MCP Server
Related Servers
Alternatives to Code Review MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to review GitHub pull requests and GitLab merge requests by fetching PR/MR details and diffs, with optional file-type filtering, and posting inline, general, or batched review comments. Supports self-hosted GitLab and custom project-specific review rules through stdio, SSE, or WebSocket transports.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to autonomously review GitHub Pull Requests by listing PRs, retrieving diffs, and submitting structured reviews.ISC
- FlicenseAqualityDmaintenanceEnables LLM clients to list, read, review, and comment on GitHub pull requests, turning an AI assistant into a fully capable code reviewer.61-
- AlicenseAqualityCmaintenanceEnables AI assistants to review GitHub and GitLab pull requests and merge requests, supporting multiple transports and custom review rules.721 PyPI5MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to perform comprehensive GitHub pull request code reviews, including analysis of code patterns, complexity, and security issues, while managing review comments and ensuring compliance with team coding standards.2MIT
- AlicenseNot gradedqualityDmaintenanceProvides AI agents with a secure PR review gateway through 9 MCP tools for managing pull requests, including context retrieval, diff, checks, and merge with two-layer access control.15 npmMIT
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.