Cloud · MODEL CONTEXT PROTOCOL
Azure Revisor MCP Server
Azure Revisor MCP Server is a community-listed Model Context Protocol server. Review the source repository before installation.
WHAT IT CONNECTS
What Azure Revisor MCP Server gives an AI Agent
The source catalog does not include a structured feature list. Review the repository documentation before use.
SECURITY
An MCP listing is not a security review
An MCP server may receive model context, credentials, local files, or permission to call external systems. Review its code, requested environment variables, network behavior, package provenance, and maintenance status before connecting it to an agent.
README
Repository documentation
A TypeScript-based server project.
- Node.js (v18 or higher)
- pnpm
- Cursor IDE (recommended)
- Clone the repository:
git clone git@github.com:mikhael-abdallah/mcp-revisor-server.git
cd mcp-revisor-server- Install dependencies:
pnpm install- Set your AZURE_PAT in a
.envfile
- Build and run in production mode:
pnpm run build
pnpm start{
"mcpServers": {
"azure-revisor": {
"url": "http://localhost:3000/sse"
}
}
}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:
- Code standards:
- Consistency with the project's coding style
- Compliance with naming conventions
- Appropriate use of design patterns
- Code quality:
- Potential bugs or logic errors
- Proper handling of errors and edge cases
- Efficiency of algorithms
- Potential security issues
- Best practices:
- SOLID principles
- Clean and readable code
- DRY (Don't Repeat Yourself)
- Separation of concerns
- 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:
- Problem identified (be specific)
- Suggestion for improvement (with code example when applicable)
- 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.
This project is licensed under the MIT License
COMMUNITY