Azure DevOps Remote MCP Server is generally available

Sicherheitsmeldung mit Schweregrad noch nicht bewertet. Technische Details im Tab „Originaltext“; empfohlene Schritte in der Checkliste.

Originaltext der Quelle (nicht übersetzt) – die deutsche Zusammenfassung findest du im Tab „Kurzfassung".

Today, we’re excited to announce the general availability of the Azure DevOps MCP Server The Azure DevOps MCP Server gives AI assistants secure, contextual access to your Azure DevOps projects so they can help you plan, build, and ship software more effectively. With the Azure DevOps remote MCP Server, you can get started without installing or hosting anything yourself. Simply connect your AI assistant directly to the Azure DevOps hosted endpoint by using streamable HTTP transport and start working with your projects in minutes. Getting Started Getting started in simple. Depending on the tools that you are using, you only need to add the following server information to your mcp.json. { "servers": { "ado-remote-mcp": { "url": "https://mcp.dev.azure.com/{organization}", "type": "http" } }, "inputs": [] }

There are additional configuration options available, and you can read more in our official documentation. Supported Clients and Services The Remote MCP Server is hosted by the Azure DevOps service and uses Microsoft Entra for authentication. Because it relies on Microsoft Entra, it follows the platform’s authentication requirements and constraints. As a result, your Azure DevOps organization must be backed by a Microsoft Entra tenant. Standalone organizations that use Microsoft accounts (MSAs) are not supported. Support for the Remote MCP Server depends on a client’s ability to authenticate with Microsoft Entra. Today, clients such as Claude Desktop, Claude Code, ChatGPT, Cursor, and similar tools require support for dynamic OAuth client registration or client ID …

Vollständiger Originalartikel ↗

• Betroffenheit im eigenen Stack prüfen: Versionen/Komponenten abgleichen.
• Originalquelle / Hersteller-Advisory lesen: https://devblogs.microsoft.com/devops/azure-devops-remote-mcp-server-ga/
• Verfügbaren Patch oder Workaround einspielen und dokumentieren.