Azure PR MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_pr_commentsB | Retrieves comments from an Azure DevOps Pull Request with their metadata. Optionally filter by comment status (active, fixed, closed, etc.). |
| check_azure_cliA | Checks if Azure CLI is installed and the user is authenticated |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have completely distinct purposes: one retrieves PR comments, the other checks Azure CLI installation and authentication. No overlap.
Both tools follow a consistent verb_noun pattern using snake_case (get_pr_comments, check_azure_cli), which is predictable and clear.
With only 2 tools for a server named 'Azure PR MCP Server', the tool count is far too low to cover the expected scope of pull request operations. The server feels incomplete.
The domain is Azure PR management, but only one PR-related tool exists (get comments). Missing essential operations like listing, creating, updating, or merging pull requests, leaving significant gaps.