AI Code Review MCP Server
Related Servers
Alternatives to AI Code Review MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to interact with GitHub repositories, issues, pull requests, code, and more through a comprehensive set of tools.-
- FlicenseBqualityDmaintenanceEnables 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.1099 npm-
- AlicenseAqualityBmaintenanceConnects AI assistants to GitHub repositories, pull requests, issues, commits, and code search while enabling repository visibility controls, CI/CD monitoring, sandboxed local filesystem access, and code quality/security analysis.131MIT
- AlicenseAqualityNot gradedmaintenanceEnables 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-
- FlicenseNot gradedqualityNot gradedmaintenanceEnables 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.-
- AlicenseBqualityBmaintenanceEnables AI agents to interact with GitHub (search repos, read files, issues, PRs), analyze code for quality and issues, and manage tasks with priority sorting.7MIT
TDQS
Scored across 7 tools
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.
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.
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.
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.