home / mcp / specialized code review tools mcp server
Provides specialized code review capabilities via critics and fixers to analyze and improve code quality.
Configuration
View docs{
"mcpServers": {
"jonels-msft-mcp-review": {
"command": "node",
"args": [
"/path/to/your/mcp-review/src/index.js"
]
}
}
}You deploy this MCP server to gain specialized code review capabilities that leverage established critic methodologies and fixing strategies. It enables a two-step workflow: analyze code with critics to identify issues, then apply targeted fixes with fixed strategies to improve code quality.
You interact with the MCP server through a compatible client in your development environment. Start a new analysis session to clear context, then request evaluations such as UI/UX reviews, security checks, data handling assessments, or performance considerations. After you obtain the critique results, choose one of the predefined fixer strategies to apply improvements directly to your codebase. This two-step pattern—analyze then fix—helps you focus on high-impact issues and track changes in a structured way.
Prerequisites you need before installing are Node.js 18.0 or higher and a development environment with VS Code.
Follow these concrete steps to set up the MCP server locally.
# 1) Clone the project with submodules to fetch critic and fixer frameworks
# Use your preferred destination path
git clone --recursive https://github.com/jonels-msft/mcp-review.git
cd mcp-review
# 2) Install dependencies
npm installConfigure your editor to run the MCP server as a local (stdio) process so the client can communicate with it. Create a server entry that points to the local server index file.
{
"mcp": {
"servers": {
"mcp_review": {
"command": "node",
"args": [
"/path/to/your/mcp-review/src/index.js"
]
}
}
}
}If you run your editor in Windows Subsystem for Linux (WSL), VS Code executes the MCP server inside the Linux environment. Use the same structure as above, but wrap the command to run inside the WSL context.
{
"mcp": {
"servers": {
"mcp_review": {
"command": "wsl",
"args": [
"node",
"/path/to/your/mcp-review/src/index.js"
]
}
}
}
}The setup may not require additional environment variables for basic operation. If your project or workflow introduces environment parameters, include them in both the global MCP settings and the per-server env mapping.
If the MCP server does not start automatically in your editor, ensure the path to your index file is correct and that Node.js is available in the environment. Restart VS Code after configuring the server entry. Check the terminal or output panel for any startup errors and confirm the server reports its status back to the client.
UI and user experience review
Color usage and accessibility review
Charts and data presentation review
SQL injection and database security review
Data validation and constraints review
Algorithm efficiency analysis
Algorithm correctness verification
Logging overhead analysis
C memory management review
C error handling patterns
Cross-platform C code review
Error handling best practices
Procedural error management
Data structure and flow analysis
Function design and organization review
Control flow analysis in procedures
Floating-point precision and associated issues review
Date/time handling correctness review
Unicode and internationalization review
SQL standard compliance analysis
POSIX compliance and portability review
Unix philosophy and interface review
Logging strategy and implementation review
Naming conventions and clarity in code
Documentation and comments quality review
Complexity and effort estimation review
Performance measurement practices review
Meson build system review
Statistical and probabilistic code review
Database design and relationships review
AI prompt engineering review
Formal logic and reasoning review
Workflow and efficiency analysis review
Add TODO comments marking issues for later fixing
Fix only low-risk issues that won’t trigger cascading changes
Fix one important issue comprehensively, even if major rearrangement is needed