Watchlist tracking
Reviewed for relevance and future tracking value.
MCP100 Assessment
Watchlist / Tracking
Why we’re tracking it
Follow-up value is specific to Azure DevOps project, work-item, repository and pipeline operations: Do domain filters and project defaults limit tool exposure while respecting signed-in Azure DevOps permissions?
Reviewed · Documentation review; complete setup workflow not independently tested
Best fit
Azure DevOps engineering and project-management workflows
What we know
Microsoft's Azure DevOps MCP server, available as a recommended hosted remote service and a local stdio package for clients that need it.
Maintenance / activity evidence
- @azure-devops/mcp 2.10.0 published 2026-09-09T14:14:57.396Z
Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.
Verification gaps / watch-outs
- Installation and comprehensive security have not been independently audited.
- Inherits user's Azure DevOps project/resource permissions. Writes: Depends on exposed Azure DevOps tools and user permissions.
- Entra OAuth or PAT.
- Sensitive access: Repositories, Work items, Pipelines/project data
- Official authentication does not imply read-only access; the user's Azure DevOps permissions determine effective authority.
Full authority, access and evidence limits are available in Review context and Access & risk.
Popularity
· 478k package downloads / 30 days
Downloads observed Sep 25, 2026.
Preserve any already-reviewed adoption metrics in MCP100. Batch 4 did not refresh package downloads because the package-stats provider had insufficient credits.
Preserve any already-reviewed adoption metrics in MCP100. Batch 4 did not refresh package downloads because the package-stats provider had insufficient credits.
All limitations / Review context
Do domain filters and project defaults limit tool exposure while respecting signed-in Azure DevOps permissions?
The bounded review of the publisher's documented Azure DevOps project, work-item, repository and pipeline operations and release notices identified no disclosed material condition preventing an accurately scoped public tracking entry. The resource's operational permissions remain uncertainty; this assessment does not certify installation safety.
- Official authentication does not imply read-only access; the user's Azure DevOps permissions determine effective authority.
- Inherits user's Azure DevOps project/resource permissions.
- Entra OAuth or PAT.
- Requests/results contain organizational engineering data.
- Reviewed write actions: Depends on exposed Azure DevOps tools and user permissions
- Sensitive access: Repositories, Work items, Pipelines/project data
- Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
- Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited.
- Documented tool authority and any remote data handling must be checked before installation or use.
- Tool inventory, client matrix and permissions completeness were not requirements for this Radar tracking review.
- Remote OAuth support depends on client; Microsoft docs currently direct Codex to local mode.
- Permissions inherit the Azure DevOps user/PAT.
Original activity observations
- @azure-devops/mcp 2.10.0 published 2026-09-09T14:14:57.396Z
Technical identity
npm/@azure-devops/mcp- Exact implementation source
- https://www.npmjs.com/package/@azure-devops/mcp ↗
- Reviewed resource type
- MCP Server
- Package identity
- @azure-devops/mcp
Evidence & Sources
- Evidence basis
- Recorded source evidence
- Setup runtime verification
- Not independently runtime-tested by MCP100 for this setup workflow.
Reviewed · Latest source observation
- Package registry ↗
@azure-devops/mcp
Recorded package identity, distribution or download evidence.
Includes references whose attribution is not established.
- Repository document ↗
microsoft/azure-devops-mcp
Recorded repository material and project history.
- Evidence source ↗
learn.microsoft.com/en-us/azure/devops/mcp-server/remote-mcp-server?view=azure-devops
Source material retained for this review.
Includes references whose attribution is not established.
Setup · Watchlist
Install & Agents
Publisher instructions.
Source evidence observed .
Additional setup details required — see the specific gaps below.
Install / connect
Publisher instructionsPublisher-documented install or connect path; prerequisites and any extra host configuration remain required.
publisher install or stdio launch · Publisher instructions
npx -y @azure-devops/mcp <YOUR_AZURE_DEVOPS_ORG>Configure / authenticate
MCP100 setup guideOfficial Azure DevOps MCP recommends hosted remote service first. Local `@azure-devops/mcp` package only for scenarios needing stdio; follow published repo link for auth and org/project scopes.
Previously reviewed local Azure stdio authentication; the hosted service remains preferred: Microsoft publisher: requires Node 20+, Azure DevOps org, and authentication. Default interactive Microsoft sign-in; alternatives are azcli, env, envvar (ADO_MCP_AUTH_TOKEN), or pat (base64 of email:PAT in PERSONAL_ACCESS_TOKEN). Configure exactly one selected auth mode and avoid checking secrets into MCP JSON.
Check connection
Suggested checkVerify client MCP tools and a read-only project/listing action; do not mutate work items.
Remove / uninstall / revoke
MCP100 setup guideIf registered in Claude Code under the name `azure-devops`, remove the client entry with `claude mcp remove azure-devops`. For other MCP hosts remove the matching server/connector in that host’s MCP settings. Remove a globally installed software package separately if applicable; this does not delete data or revoke a service credential.
Client removal, software uninstall, persistent-data deletion and credential revocation are separate actions.
Remove client registration · Claude Code only · MCP100 composed guide
claude mcp remove azure-devops
What it does
Microsoft's Azure DevOps MCP server, available as a recommended hosted remote service and a local stdio package for clients that need it.
- Capability
- Developer Tools
- Resource type
- MCP Server
- Industry
- Software & Technology
- Best fit
- Azure DevOps engineering and project-management workflows
Representative uses
- Query Azure DevOps projects/resources
- Work with engineering artifacts
- Use remote hosted MCP
- Use local stdio fallback
Limitations
- Remote OAuth support depends on client; Microsoft docs currently direct Codex to local mode.
- Permissions inherit the Azure DevOps user/PAT.
Reviewed access
Access & risk
Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.
- Authentication
- Entra OAuth or PAT.
- Permissions
- Inherits user's Azure DevOps project/resource permissions.
- Data handling
- Requests/results contain organizational engineering data.
- Cost
- unknown
- Risk and cautions
- Official authentication does not imply read-only access; the user's Azure DevOps permissions determine effective authority.
Access scope and cautions
- Write actions
- Depends on exposed Azure DevOps tools and user permissions
- Sensitive access
- Repositories Work items Pipelines/project data
- Risk level
- high
FAQ
Based on reviewed evidence as of 2026-10-06. Watchlist tracking is not a recommendation or a security certification.
Which tasks are documented for this implementation?
What setup and authentication are documented?
Can it modify data or perform write operations?
What data-handling boundary should I consider?
What limitations and risks should I check before use?
Is this an official MCP?
Microsoft is listed as First-party MCP in MCP100’s current evidence.