MCP Code Review Server
Related Servers
Alternatives to MCP Code Review Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceA collaborative code and markdown review tool that bridges human reviewers and AI agents, enabling both to browse files, inspect git diffs, leave structured comments, and save a final review report from the same UI in real time.23 PyPI2MIT
- FlicenseNot gradedqualityDmaintenanceA tool that integrates with GitHub and Notion to analyze and review pull requests, enabling automated code reviews and documentation in Notion.-
- FlicenseNot gradedqualityFmaintenanceA specialized code review service that provides 36+ critics for different programming aspects and 3 fixing strategies to automatically address identified issues in a two-step workflow.-
- AlicenseNot gradedqualityDmaintenanceAutomatically generates comprehensive merge request summaries from git logs, analyzing commit history and categorizing changes into structured descriptions. Provides tools to analyze git repositories, compare branches, and create detailed summaries with change categorization, impact analysis, and review time estimates.1MIT
- AlicenseNot gradedqualityCmaintenanceA local, read-only Git change review tool that provides total workspace diffs, staged/unstaged views, file-level inspection, and task-scoped snapshots for MCP-compatible clients like Codex, Claude Code, and Cursor.MIT
- FlicenseAqualityDmaintenanceAI-powered code review assistant that analyzes repositories for security vulnerabilities, performance bottlenecks, and code quality issues through natural language interactions.2-
TDQS
Scored across 3 tools
The three tools have distinct primary purposes (list changed files, generate review, list authors), but generate_code_review can also return a changed file list when file_descriptions is omitted, creating a slight functional overlap with get_changed_files. This overlap is minor because the intended workflow is clearly described, but it could cause an agent to call the wrong tool first.
All tool names follow a consistent verb_noun pattern: get_changed_files, generate_code_review, list_branch_authors. The naming is uniform in style and clearly communicates each tool's action and target.
Three tools are appropriate for a specialized code review server. Each tool serves a distinct step in the workflow (identify files, generate review, identify authors), and no tool feels redundant or excessive for the scope.
The tool surface covers the essential workflow for generating code reviews: retrieving changed files, generating the review report, and listing authors for context. There are no obvious gaps within the stated purpose of the server.