What is Mcp Revisor Server

mcp-revisor-server is a TypeScript-based server project designed to facilitate code review processes in software development, particularly in Azure environments.

Use cases

Use cases include automated code reviews for pull requests, ensuring compliance with coding standards, and enhancing code quality through systematic reviews.

How to use

To use mcp-revisor-server, clone the repository, install dependencies using pnpm, set your Azure Personal Access Token in a .env file, and run the project in production mode using the provided commands.

Key features

Key features include integration with Azure for pull request reviews, adherence to coding standards, code quality checks, and best practices enforcement during code reviews.

Where to use

mcp-revisor-server is primarily used in software development environments, especially those utilizing Azure DevOps for version control and code review processes.

Azure Revisor MCP Server

A TypeScript-based server project.

Prerequisites

• Node.js (v18 or higher)
• pnpm
• Cursor IDE (recommended)

Installation

1. Clone the repository:

git clone [email protected]:mikhael-abdallah/mcp-revisor-server.git
cd mcp-revisor-server

2. Install dependencies:

pnpm install

3. Set your AZURE_PAT in a .env file

Running the Project

1. Build and run in production mode:

pnpm run build
pnpm start

Adding MCP to Cursor

{
  "mcpServers": {
    "azure-revisor": {
      "url": "http://localhost:3000/sse"
    }
  }
}

Using

SuggestedPrompt:
You are a senior code reviewer with extensive software development experience and best practices. Your task is to thoroughly review the diff of the mentioned pull request, focusing on:

1. Code standards:

• Consistency with the project’s coding style
• Compliance with naming conventions
• Appropriate use of design patterns

2. Code quality:

• Potential bugs or logic errors
• Proper handling of errors and edge cases
• Efficiency of algorithms
• Potential security issues

3. Best practices:

• SOLID principles
• Clean and readable code
• DRY (Don’t Repeat Yourself)
• Separation of concerns

4. Specific to this PR:

• Review the pull request https://dev.azure.com/organization/project/_git/repository/pullrequest/pullRequestNumber (Url for the pull request)
• Search files to better understand the project context and analyze the impact of changes
• Check if there are adequate tests for the changes proposals

Comment format:
For each issue found, make a comment on the PR using the tool:

1. Problem identified (be specific)
2. Suggestion for improvement (with code example when applicable)
3. Severity rating: [CRITICAL], [HIGH], [MEDIUM] or [LOW]

Prioritize critical issues that can:

• Cause bugs in production
• Compromise security
• Significantly impact performance

Adopt a professional and constructive tone, focusing on the code and not the author. When suggesting changes, explain the reason for the proposed improvement.

If you find repetitive patterns in the code, suggest comprehensive refactorings in a separate comment at the top of the PR.

License

This project is licensed under the MIT License