Azure Revisor MCP Server

by mikhael-abdallah

2 stars
298 downloads
Not rated
GitHub

Description

# Azure Revisor MCP Server A TypeScript-based server project. ## Prerequisites - Node.js (v18 or higher) - pnpm - Cursor IDE (recommended) ## Installation 1. Clone the repository: ```bash git clone git@github.com:mikhael-abdallah/mcp-revisor-server.git cd mcp-revisor-server ```…

About

# Azure Revisor MCP Server A TypeScript-based server project. ## Prerequisites - Node.js (v18 or higher) - pnpm - Cursor IDE (recommended) ## Installation 1. Clone the repository: ```bash git clone git@github.com:mikhael-abdallah/mcp-revisor-server.git cd mcp-revisor-server ``` 2. Install dependencies: ```bash pnpm…

Details

Author
mikhael-abdallah
GitHub stars
2
Downloads
298
Categories
Cloud Service

- Integrates with Azure DevOps pull requests
- Uses a structured review prompt with severity ratings
- Checks code standards, quality, and best practices
- Supports file search for project context
- Runs as an SSE-based MCP server on localhost:3000

Setting up with Highlight

This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:

  1. Download and install Highlight from highlightai.com/download
  2. Navigate to the plugins tab and select "Add Custom Plugin"
  3. Configure the plugin with the settings below
    Plugin Name Azure Revisor MCP Server
    Command (node, npx, python, etc.)

    Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.

  4. Enable "Start Automatically" if you want the plugin to start when Highlight launches

From the repository

Install Node.js v18+, pnpm, clone the repository, install dependencies, and set your Azure Personal Access Token in a .env file. Build and run with pnpm run build && pnpm start. Then add the server to Cursor IDE by specifying "url": "http://localhost:3000/sse" in the MCP server configuration.

Claude Desktop / Cursor

Paste into your MCP client config file to install this server.

{
    "mcpServers": {
        "azure revisor mcp server": {
            "azure-revisor": {
                "type": "http",
                "url": "http://localhost:3000/sse"
            }
        }
    }
}

McpServers

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

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 git@github.com: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

No reviews yet — be the first

Sign in to leave a review

Use Google, GitHub, or an email account so ratings stay tied to real people.

Email sign in

No reviews posted yet.