MCP Revisor Server

🚀 MCP Server for Azure Revisor

A TypeScript-based server-side project.

🚀 Quick Start

Prerequisites

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

📦 Installation

1. Clone the repository:

git clone git@github.com:mikhael-abdallah/mcp-revisor-server.git
cd mcp-revisor-server

2. Install dependencies:

pnpm install

3. Set your AZURE_PAT in the .env file.

Running the Project

1. Build and run in production mode:

pnpm run build
pnpm start

Adding MCP to Cursor

Add the following to your Cursor configuration file:

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

💻 Usage Examples

Basic Usage

Suggestion Tips:

You are a senior code review expert with extensive software development experience and best practices. Your task is to comprehensively review the code differences of the specified pull request, focusing on:

1. Code Conventions:

   • Consistency with the project's coding style.
   • Adherence to naming conventions.
   • Appropriate use of design patterns.

2. Code Quality:

   • Potential errors or logical issues.
   • Correct handling of errors and edge cases.
   • Algorithm efficiency.
   • Security vulnerabilities.

3. Best Practices:

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

4. Specifically for this PR:

   • Review the specified pull request at https://dev.azure.com/organization/project/_git/repository/pullrequest/pullRequestNumber (URL of the pull request).
   • Search files to better understand the project context and analyze the impact of the changes.
   • Check if there are sufficient tests to validate the proposed changes.

Comment Format:

For each issue found, use the PR tool to comment:

1. Identified issue (specify in detail).
2. Suggestions for improvement (attach code examples if necessary).
3. Severity rating: [CRITICAL], [HIGH], [MEDIUM], or [LOW].

Prioritize serious issues that may cause:

• Errors in the production environment.
• Security risks.
• Significant impact on performance.

Comment in a professional and constructive manner, focusing on the code rather than the author. When suggesting changes, explain the reasons for the changes.

If you find repeated patterns in the code, propose a comprehensive refactoring in a separate comment at the top of the PR.

📄 License

This project is licensed under the MIT License.