How do I use Azure PR MCP Server?

1. Click on "Install Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Azure PR MCP Server list active comments for PR 123 in myorg/myproject/myrepo" That's it! The server will respond to your query, and you can continue using it as needed. Here is a step-by-step guide with screenshots.

Azure PR MCP Server

by tacone

Overview Schema Related Servers Score Discussions

TypeScript

Local

Azure PR MCP Server

A Model Context Protocol (MCP) server for reviewing Azure DevOps Pull Request comments using the Azure CLI.

🔒 Readonly.

🤖 Made by the AI for the AI.

Features

✅ Azure CLI Validation - Automatically checks for Azure CLI availability
🔐 Authentication Handling - Verifies Azure CLI authentication status
💬 PR Comment Retrieval - Fetches PR comments with full metadata
🔍 Status Filtering - Filter comments by status (active, fixed, closed, etc.)
🧪 Unit Tests - Comprehensive test coverage using Vitest

Related MCP server: Azure DevOps MCP Server

Prerequisites

Node.js >= 18
pnpm >= 9.0.0
Azure CLI - Installation guide
Azure DevOps Organization - Access to an Azure DevOps organization with pull requests

Installation

Install dependencies

pnpm install

Build the project

pnpm build

Azure CLI Setup

Install Azure CLI (if not already installed):
- macOS: brew install azure-cli
- Windows: Download from Microsoft Docs
- Linux: Follow Linux installation guide
Login to Azure:
```
az login
```
The Azure DevOps extension will be automatically installed when you first use the server.

Usage

Running the MCP Server

The server runs on stdio and is designed to be used with MCP clients:

node dist/index.js

Available Tools

1. `check_azure_cli`

Checks if Azure CLI is installed and the user is authenticated.

Input: None

Output:

{
  "cli_installed": true,
  "cli_version": "2.50.0",
  "authenticated": true,
  "account": "user@example.com",
  "devops_extension": true,
  "status": "ready"
}

2. `get_pr_comments`

Retrieves comments from an Azure DevOps Pull Request with optional status filtering.

Input:

pr_url (required): Full Azure DevOps PR URL
- Format: https://dev.azure.com/{org}/{project}/_git/{repo}/pullrequest/{id}
- Legacy format: https://{org}.visualstudio.com/{project}/_git/{repo}/pullrequest/{id}
status_filter (optional): Filter by comment status
- Options: active, fixed, closed, wontfix, pending, bydesign, unknown, system

Output:

{
  "pr_url": "https://dev.azure.com/myorg/myproject/_git/myrepo/pullrequest/123",
  "status_filter": "active",
  "total_comments": 5,
  "comments": [
    {
      "id": 1,
      "thread_id": 100,
      "author": "John Doe",
      "author_email": "john.doe@example.com",
      "content": "Please add error handling here",
      "status": "active",
      "thread_status": "active",
      "comment_type": "text",
      "published_date": "2025-11-20T10:30:00Z",
      "last_updated_date": "2025-11-20T10:30:00Z"
    }
  ]
}

Example PR URL Formats

https://dev.azure.com/myorg/myproject/_git/myrepo/pullrequest/123

https://myorg.visualstudio.com/myproject/_git/myrepo/pullrequest/456

MCP Client Configuration

VS Code with GitHub Copilot (User-Level Global Configuration)

For global access across all workspaces, add the server to your user-level MCP configuration:

File Location: ~/.config/Code/User/mcp.json (Linux/macOS) or %APPDATA%\Code\User\mcp.json (Windows)

Add this entry to the servers object:

{
  "servers": {
    "simple-azure-devops-mcp": {
      "command": "node",
      "type": "stdio",
      "args": ["/absolute/path/to/azure-mcp/dist/index.js"]
    }
  }
}

Important: Replace /absolute/path/to/azure-mcp/dist/index.js with the actual path to your built project.

Setup Steps:

Build the project: pnpm build
Edit ~/.config/Code/User/mcp.json and add the server configuration
Reload VS Code window (Cmd/Ctrl + Shift + P → "Developer: Reload Window")
Open GitHub Copilot Chat
The MCP tools will be available in all workspaces

VS Code with GitHub Copilot (Workspace Level)

Create or edit .vscode/settings.json to automatically enable MCP server for the current workspace:

{
  "github.copilot.chat.mcp.enabled": true,
  "github.copilot.chat.mcp.servers": {
    "simple-azure-devops-mcp": {
      "command": "node",
      "args": ["${workspaceFolder}/dist/index.js"]
    }
  }
}

Setup Steps:

Open this workspace in VS Code
Ensure the project is built: pnpm build
Reload VS Code window (Cmd/Ctrl + Shift + P → "Developer: Reload Window")
Open GitHub Copilot Chat
The MCP tools will be automatically available

Note: Make sure you have GitHub Copilot enabled and MCP support is available in your VS Code version.

VS Code (Cline Extension)

Install the Cline extension from the VS Code marketplace
Open Cline Settings (click the gear icon in Cline panel)
Add MCP Server in the MCP Servers section:

{
  "mcpServers": {
    "simple-azure-devops-mcp": {
      "command": "node",
      "args": ["/absolute/path/to/azure-mcp/dist/index.js"]
    }
  }
}

Important: Use the absolute path to your project. For example:

Linux/macOS: /home/username/Code/azure-mcp/dist/index.js
Windows: C:\\Users\\username\\Code\\azure-mcp\\dist\\index.js

Restart Cline or reload VS Code
The tools should now appear in Cline's available tools

VS Code Settings Location

You can also manually edit the Cline configuration file:

Linux: ~/.config/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
macOS: ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
Windows: %APPDATA%\Code\User\globalStorage\saoudrizwan.claude-dev\settings\cline_mcp_settings.json

Claude Desktop

Add this server to your Claude Desktop configuration:

{
  "mcpServers": {
    "simple-azure-devops-mcp": {
      "command": "node",
      "args": ["/absolute/path/to/azure-mcp/dist/index.js"]
    }
  }
}

Configuration file location:

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json

Development

This project uses pnpm as its official package manager. Please use pnpm for all package management operations to ensure consistency and proper dependency resolution.

Run tests

pnpm test

Run tests with coverage

pnpm test:coverage

Linting and Formatting

This project uses ESLint for linting and Prettier for code formatting:

# Run linter
pnpm lint

# Fix linting issues automatically
pnpm lint:fix

# Format code with Prettier
pnpm format

# Check formatting without making changes
pnpm format:check

Git Hooks

Husky is configured to run lint-staged on pre-commit, which automatically:

Runs ESLint with auto-fix on staged TypeScript files
Formats code with Prettier

This ensures code quality and consistency before commits.

Watch mode for development

pnpm dev

Project Structure

azure-mcp/
├── src/
│   ├── index.ts              # Main MCP server
│   ├── azure-cli.ts          # Azure CLI utilities
│   ├── pr-comments.ts        # PR comment retrieval logic
│   ├── azure-cli.test.ts     # Tests for Azure CLI utilities
│   └── pr-comments.test.ts   # Tests for PR comment parsing
├── dist/                     # Compiled JavaScript (generated)
├── package.json              # Package configuration
├── tsconfig.json             # TypeScript configuration
├── vitest.config.ts          # Vitest test configuration
└── README.md                 # This file

Comment Status Types

active: Comment thread is active and requires attention
fixed: Issue has been addressed
closed: Thread is closed
wontfix: Issue won't be addressed
pending: Waiting for action
bydesign: Behavior is intentional
unknown: Status is not determined
system: System-generated comment

Troubleshooting

Azure CLI not found

Error: Azure CLI is not installed or not available in PATH

Solution: Install Azure CLI and ensure it's in your PATH.

Not authenticated

Error: Not authenticated. Please run: az login

Solution: Run az login and complete the authentication flow.

Azure DevOps extension missing

The server will automatically attempt to install the azure-devops extension. If this fails:

az extension add --name azure-devops

Invalid PR URL format

Error: Invalid Azure DevOps PR URL format

Solution: Ensure your PR URL matches one of these formats:

https://dev.azure.com/{org}/{project}/_git/{repo}/pullrequest/{id}
https://{org}.visualstudio.com/{project}/_git/{repo}/pullrequest/{id}

Contributing

Fork the repository
Create a feature branch
Make your changes
Run tests: pnpm test
Submit a pull request

License

MIT

Resources

Available Tools

2 tools

check_azure_cliA

Checks if Azure CLI is installed and the user is authenticated

ParametersJSON Schema

Name	Required	Description	Default
No parameters

TDQS

A3.8/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description must fully convey behavioral traits. It states the tool 'checks' installation and authentication, implying a read-only operation with boolean or status response. However, it does not disclose what happens on failure (e.g., error vs false return) or whether the tool might have side effects like prompting login. The description is adequate but lacks specific return information.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, concise sentence that directly states the tool's purpose. It is front-loaded with the key action and resource, and contains no unnecessary words or information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has zero parameters, no output schema, and a single sibling with no functional overlap, the description is mostly complete for its simplicity. It would benefit from mentioning the return type or value, but for a basic check tool, the current description is sufficient for an AI agent to understand the tool's role.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There are no parameters, so the baseline is 4. The description does not need to add parameter information. The schema already covers all parameters (none), so no additional explanation is needed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool checks two specific conditions: whether Azure CLI is installed and the user is authenticated. It uses a specific verb ('checks') and resource ('Azure CLI'), and distinguishes itself from the sibling tool 'get_pr_comments' which has a completely different purpose.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives. There is no mention of prerequisites, or scenarios where this should be used before other CLI-related operations. The sibling tool is unrelated, so no differentiation is needed, but usage context is missing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get_pr_commentsB

Retrieves comments from an Azure DevOps Pull Request with their metadata. Optionally filter by comment status (active, fixed, closed, etc.).

ParametersJSON Schema

Name	Required	Description	Default
`pr_url`	Yes	The full URL of the Azure DevOps Pull Request (e.g., https://dev.azure.com/{org}/{project}/_git/{repo}/pullrequest/{id})
`status_filter`	No	Optional filter for comment status. Values: active, fixed, closed, wontfix, pending, bydesign, unknown, system

TDQS

B3.3/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, so description bears full burden. It mentions retrieval and optional filtering but lacks disclosure on pagination, authentication, error handling, or performance implications.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two concise sentences, front-loaded with purpose, no extraneous information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers purpose and parameters adequately given simple tool, but lacks behavioral details and usage context that would fully support an AI agent's decision-making.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. Description paraphrases the schema for both parameters without adding new meaning (e.g., example URL is in schema).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states it retrieves comments from an Azure DevOps Pull Request with metadata, specifying verb and resource. Distinguishes from sibling 'check_azure_cli' which is unrelated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives. Sibling tool 'check_azure_cli' is different, but no explicit context provided to help agent decide.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

2 tool updatesv1.0.0Jul 28, 2026
- First observedcheck_azure_cli
- First observedget_pr_comments

Install Server

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

B3.4/5.0

Disambiguation5/5

The two tools have completely distinct purposes: one retrieves PR comments, the other checks Azure CLI installation and authentication. No overlap.

Naming Consistency5/5

Both tools follow a consistent verb_noun pattern using snake_case (get_pr_comments, check_azure_cli), which is predictable and clear.

Tool Count1/5

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.

Completeness1/5

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.

Maintenance

ActivityInactive

ResponsivenessSyncing

Resources

GitHub Repository

Need Help?

Related Servers

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Azure DevOps (ADO)
io.github.PremierInc
The MCP server for Azure DevOps, bringing the power of Azure DevOps directly to your agents.
CI/CD & DevOps Version Control Project Management
21,997
JFrog Remote MCP Server
io.github.jfrog
MCP Server for JFrog, providing tools for development and artifact management.
Developer Tools CI/CD & DevOps Cloud Platforms
215
neverinfamous-memory-journal-mcp
ai.smithery
A MCP server built for developers enabling Git based project management with project and personal…
Version Control Developer Tools Project Management
320
Appcircle MCP
io.appcircle
MCP server for Appcircle mobile CI/CD platform.
CI/CD & DevOps Developer Tools
2

Related MCP Servers

GitHub PR Comments MCP Server
Version Control Developer Tools
shaileshahuja
A
license
D
quality
D
maintenance
An MCP server that fetches GitHub Pull Request comments with file paths, line ranges, and replies using a GitHub personal access token.
Updated a year ago (2025-07-30 05:54 UTC)
1
3
MIT
Azure DevOps MCP Server
CI/CD & DevOps Version Control Project Management
Kshitijijari09
F
license
Not graded
quality
C
maintenance
MCP server that provides tools to interact with Azure DevOps, including querying work items, repositories, pull requests, builds, commits, and creating work items via a standardized interface.
Updated a year ago (2025-09-07 19:17 UTC)
-
GitHub PR Review MCP
Version Control Project Management Code Analysis
aq35
A
license
B
quality
C
maintenance
An MCP server that collects Pull Request comments from private GitHub repositories, including issue comments, review comments, and review summaries.
Updated 2 months ago (2026-07-08 21:57 UTC)
1
19
MIT
Azure DevOps PR Reviewer MCP
Developer Tools CI/CD & DevOps Version Control
MalinduDilshan
A
license
Not graded
quality
B
maintenance
An MCP server for automated code reviews on Azure DevOps pull requests, enabling AI assistants to fetch PR details, validate requirements, post inline comments, and set review votes.
Updated a month ago (2026-07-28 17:03 UTC)
MIT

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/tacone/simple-azure-devops-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server

Azure PR MCP Server

Features

Prerequisites

Installation

Install dependencies

Build the project

Azure CLI Setup

Usage

Running the MCP Server

Available Tools

1. check_azure_cli

2. get_pr_comments

Example PR URL Formats

MCP Client Configuration

VS Code with GitHub Copilot (User-Level Global Configuration)

VS Code with GitHub Copilot (Workspace Level)

VS Code (Cline Extension)

VS Code Settings Location

Claude Desktop

Development

Run tests

Run tests with coverage

Linting and Formatting

Git Hooks

Watch mode for development

Project Structure

Comment Status Types

Troubleshooting

Azure CLI not found

Not authenticated

Azure DevOps extension missing

Invalid PR URL format

Contributing

License

Resources

Available Tools

TDQS

TDQS

Tool Schema Changelog

TDQS

Maintenance

Resources

Looking for Admin?

Related MCP Connectors

Related MCP Servers

GitHub PR Comments MCP Server

Azure DevOps MCP Server

GitHub PR Review MCP

Azure DevOps PR Reviewer MCP

Latest Blog Posts

MCP directory API

1. `check_azure_cli`

2. `get_pr_comments`