Reviewer MCP
Utilizes .env files for environment configuration to set up AI providers and their specific settings.
Enables code review functionality by analyzing Git diffs with focus on security, performance, style, or logic.
Supports generating technical specifications in Markdown format as one of the output options.
Integrates with npm for running project commands including tests, linting, and builds through standardized tools.
Provides integration with Ollama to use local AI models as an alternative to cloud providers, supporting all tools including specification generation and code review.
Integrates with OpenAI's API as one of the AI providers, allowing use of models like o1-preview for specification generation, code review, and other development tools.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Reviewer MCP review this code diff for security issues"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Reviewer MCP
An MCP (Model Context Protocol) service that provides AI-powered development workflow tools. It supports multiple AI providers (OpenAI and Ollama) and offers standardized tools for specification generation, code review, and project management.
Features
Specification Generation: Create detailed technical specifications from prompts
Specification Review: Review specifications for completeness and provide critical feedback
Code Review: Analyze code changes with focus on security, performance, style, or logic
Test Runner: Execute tests with LLM-friendly formatted output
Linter: Run linters with structured output formatting
Pluggable AI Providers: Support for both OpenAI and Ollama (local models)
Related MCP server: Foundry MCP
Installation
npm install
npm run buildConfiguration
Environment Variables
Create a .env file based on .env.example:
# AI Provider Configuration
AI_PROVIDER=openai # Options: openai, ollama
# OpenAI Configuration
OPENAI_API_KEY=your_api_key_here
OPENAI_MODEL=o1-preview
# Ollama Configuration (for local models)
OLLAMA_BASE_URL=http://localhost:11434
OLLAMA_MODEL=llama2Project Configuration
Create a .reviewer.json file in your project root to customize commands:
{
"testCommand": "npm test",
"lintCommand": "npm run lint",
"buildCommand": "npm run build",
"aiProvider": "ollama",
"ollamaModel": "codellama"
}Using with Claude Desktop
Add the following to your Claude Desktop configuration:
{
"mcpServers": {
"reviewer": {
"command": "node",
"args": ["/path/to/reviewer-mcp/dist/index.js"],
"env": {
"OPENAI_API_KEY": "your-api-key-here"
}
}
}
}Using with Ollama
Install Ollama: https://ollama.ai
Pull a model:
ollama pull llama2orollama pull codellamaSet
AI_PROVIDER=ollamain your.envfileThe service will use your local Ollama instance
Available Tools
generate_spec
Generate a technical specification document.
Parameters:
prompt(required): Description of what specification to generatecontext(optional): Additional context or requirementsformat(optional): Output format - "markdown" or "structured"
review_spec
Review a specification for completeness and provide critical feedback.
Parameters:
spec(required): The specification document to reviewfocusAreas(optional): Array of specific areas to focus the review on
review_code
Review code changes and provide feedback.
Parameters:
diff(required): Git diff or code changes to reviewcontext(optional): Context about the changesreviewType(optional): Type of review - "security", "performance", "style", "logic", or "all"
run_tests
Run standardized tests for the project.
Parameters:
testCommand(optional): Test command to run (defaults to configured command)pattern(optional): Test file pattern to matchwatch(optional): Run tests in watch mode
run_linter
Run standardized linter for the project.
Parameters:
lintCommand(optional): Lint command to run (defaults to configured command)fix(optional): Attempt to fix issues automaticallyfiles(optional): Array of specific files to lint
Development
# Run in development mode
npm run dev
# Run tests
npm test
# Run unit tests only
npm run test:unit
# Run integration tests (requires Ollama)
npm run test:integration
# Type checking
npm run typecheck
# Linting
npm run lintEnd-to-End Testing
The project includes a comprehensive e2e test that validates the full workflow using a real Ollama instance:
Install and start Ollama: https://ollama.ai
Pull a model:
ollama pull llama2Run the test:
npm run test:e2e
The e2e test demonstrates:
Specification generation
Specification review
Code creation
Code review
Linting
Test execution
All using real AI responses from your local Ollama instance.
License
MIT
Available Tools
8 toolsgenerate_specC
Generate a specification document using OpenAI O3 model
Inputs: prompt (required), context, format.
memoryA
Store and retrieve temporary key-value pairs in memory (data is lost on MCP server restart)
Inputs: action (required), key, value, tags, +1 more.
musicC
Control Spotify for background music (macOS only)
Inputs: action (required), uri, volume, mood.
notifyC
Provide audio notifications to users (macOS only)
Inputs: message (required), type, voice, rate.
review_codeC
Review code changes and provide feedback
Inputs: diff (required), context, reviewType.
review_specB
Review a specification for completeness and provide critical feedback
Inputs: spec (required), focusAreas.
run_linterC
Run standardized linter for the project
Inputs: fix, files.
run_testsB
Run standardized tests for the project (with coverage when no pattern specified)
Inputs: pattern.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 8 tools
Most tools have distinct purposes, such as generate_spec for document creation, review_code for code feedback, and run_tests for testing. However, review_code and run_linter could be confused as both involve code quality checks, though their descriptions clarify that review_code provides feedback while run_linter runs a standardized tool. Overall, the overlap is minimal and manageable.
All tool names follow a consistent verb_noun pattern, such as generate_spec, review_code, run_tests, and notify. There are no deviations in naming conventions, making the set predictable and easy to understand. This consistency enhances usability and reduces cognitive load for agents.
With 8 tools, the count is well-scoped for a server focused on code review and development tasks. Each tool serves a specific function, such as specification handling, code review, testing, and utilities like notifications and music. This number is neither too sparse nor overwhelming, fitting the server's purpose effectively.
The tool set covers key aspects of code review and development, including specification generation, code review, linting, and testing. However, there are notable gaps, such as the lack of tools for updating or deleting specifications, managing review history, or integrating with version control systems. These omissions could limit workflow coverage and cause agent inefficiencies.
Maintenance
Related MCP Connectors
8 AI services via MCP: content, code, image, docs, data extraction, translation, SEO, email.
One MCP server for the services your AI needs: memory, files, Microsoft 365, kanban and more.
GitHub Copilot MCP: code, repo, PR, workflow tools for AI assistants.
MCP server for your apps' tools and custom tools, plus hosted AI agents and approval-gated workflows
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceAn AI-powered MCP server that provides development tools for code analysis, documentation, and project management including code pattern extraction, humorous code reviews, TODO scanning, and PRD generation.7 npmISC
- AlicenseNot gradedqualityDmaintenanceEnables spec-driven development workflows with AI assistants, providing tools for managing specification lifecycles, task dependencies, code navigation, testing, and automated reviews through a unified CLI and MCP interface.4MIT
- AlicenseNot gradedqualityDmaintenanceAn AI-native specification framework that enables deep requirements analysis and structured project planning through intelligent Q\&A workflows. The MCP server provides tools for project initialization, requirement analysis, and the generation of living documentation like development plans and architecture specs.27 npmApache 2.0
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to research, plan, generate requirements, create starter projects, analyze codebases, and execute multi-step software development workflows through MCP tools.58 npmMIT