Code Review MCP Server
Related Servers
Alternatives to Code Review MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables pull request review, risk rating, and improvement suggestions directly inside MCP clients by pasting a GitLab/GitHub URL; it can post review comments back to the PR/MR.MIT
- AlicenseNot gradedqualityCmaintenanceEnables automated code review and GitHub PR commenting through MCP integration.293 npm9MIT
- FlicenseNot gradedqualityDmaintenanceEnables automated AI-powered code review for pull requests across GitHub, GitLab, Bitbucket, and Azure DevOps via webhooks, and manual code review through MCP tools using Groq, Claude, or GPT-4.1-
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to run security and code review on pull requests and diffs, exposing review_pr and review_diff capabilities with local-first analyzers and LLM explanations.2MIT
- AlicenseBqualityCmaintenanceEnables code review operations on GitHub and GitLab, including fetching pull/merge requests, viewing diffs, adding comments, analyzing code quality, and creating merge requests directly from your MCP client.159 npm4MIT
- FlicenseNot gradedqualityBmaintenanceEnables automated semantic analysis of Git pull request diffs to detect breaking REST/GraphQL API schema changes, integrating with MCP-compatible clients for AI-driven code review.8-
TDQS
Scored across 3 tools
review_code is broad and overlaps with suggest_improvements (both provide code quality feedback) and partially with analyze_security. The descriptions help but do not fully draw clear boundaries between general review and targeted analysis.
All three tools follow a consistent verb_noun snake_case pattern: review_code, analyze_security, suggest_improvements. The convention is predictable and readable.
Three tools is reasonable for a focused code-review server, with each targeting a distinct analysis angle. It is slightly thin for a full code-review workflow (e.g., no diff retrieval or comment posting), but not problematic.
The surface covers three common analysis types but lacks lifecycle operations such as fetching code changes, retrieving diffs, or posting review comments. These gaps may force agents to combine with other tools to complete a review workflow.