The MCP server for Azure DevOps, bringing the power of Azure DevOps directly to your agents.
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…
Inferred from the transports this listing declares (streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
The repository archive could not be read at scan time (The operation was aborted due to timeout), so no tool declarations could be extracted from it. Nothing here is a statement about what this exposes.
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 (Optional) 6. 🌏 Using Domains (local) 7. 🐥 Project and Team Defaults (local) 8. 📝…
This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.