@azure-devops/mcp

Name: @azure-devops/mcp
Author: Microsoft Corporation

MCPcommunity

v2.7.0Microsoft CorporationMITUpdated 3mo agonpm GitHub

MCP server for interacting with Azure DevOps

The Azure DevOps Remote MCP Server is now available in public preview for all organizations. We recommend migrating to the Remote MCP Server going forward. This project provides Azure DevOps MCP tooling for AI agents, with a remote-first onboarding experience and a local server option when you need it. 3. 🚀 Remote MCP Server (Recommended) 4. ⚙️ Supported Tools 5. 🔌 Local MCP Server Installation…

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →

86kDownloads/wk

2kGitHub stars

557Forks

3mo agoLast update

Package

AuthorMicrosoft Corporation

LicenseMIT

Version2.7.0

Sourcenpm+github

npm@azure-devops/mcp

GitHubmicrosoft/azure-devops-mcp

Trust Status

40/100Caution

✓Listed in Forge index+10/10

—Publisher identity verified+0/20

→ Publisher: run `forge publish` from the package repo to claim ownership

—Ed25519 publish signature+0/5

→ Included automatically when the publisher runs `forge publish`

—Domain verification+0/5

→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }

—npm Trusted Publishing (Sigstore)+0/5

→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo

—npm maintainer match+0/5

→ Earned once your identity is verified above and that login is an npm maintainer of this package

✓CVE scan · clean+30/30

—Static analysis · clean+0/20

→ Suspicious install scripts or obfuscated code detected

Paste into Claude Code, Cursor, or any AI assistant to fix all gaps

StatusCommunity-indexed

PublisherUnverified

SignatureUnsigned

Domain—

Provenance—

Dependencies✓ 60 resolved+ · none vulnerable

Tool surface—

Security scan⚠ Warnings (1)v2.7.0 · 2mo ago

SCRIPTpreinstallOutbound network request

EvalsNone

IndexedMay 24, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts — it cannot prove the absence of malicious code.

About