How it worksFeaturesDocsEarly accessGitHubDashboard

How to integrate Azure DevOps Health using MCP

Inspect Azure resource and service health. This guide creates an MCP server from Arthur's Azure DevOps Health template — tools preconfigured against https://management.azure.com — and finishes by sharing the server's MCP swagger documentation.

Steps

  1. Open the Secrets vault and create a secret named AZURE_DEVOPS_HEALTH_API_KEY holding your access token. Register a client with Microsoft Entra ID or obtain an Azure CLI/PowerShell access token for Azure Resource Manager, then provide the token for an identity authorized to read the target subscription.

    Open the Secrets vault to store the Azure DevOps Health credential before using the template

    Start the New secret wizard

    Name the secret AZUREDEVOPSHEALTHAPIKEY — servers reference it by this name

  2. Go to the REST API Templates gallery and search for Azure DevOps Health.

    Record what the credential is for so it stays recognizable

    Continue to the protected value step

  3. Click Use template on the Azure DevOps Health card to open the server-creation dialog.

    Enter the credential value — a demo value here; use your real key when adopting the integration

    Review the generated secret reference syntax

  4. Review the server name and select AZURE_DEVOPS_HEALTH_API_KEY in the credential field — the dialog only accepts vault secrets, and it lists every tool that will be created.

    Store the AZUREDEVOPSHEALTHAPIKEY secret in the vault

    Open the REST API template gallery

    Search the gallery for the Azure DevOps Health integration

  5. Click Create server. Arthur creates the server, applies the authentication, and generates all the tools.

    Open the Azure DevOps Health template with its preconfigured tools

    Name the server after the integration it provides

    Pick the AZUREDEVOPSHEALTHAPIKEY secret from the vault suggestions

    Select the stored credential

    Create the Azure DevOps Health server with its preconfigured tools

  6. Open the server's Tools tab to review the generated tools.

    Review the tools generated from the Azure DevOps Health template

  7. Open the server's Connect section and click Share the MCP swagger documentation — Arthur generates the public documentation link and QR code for this server.

    Open the server's Connect section, where the MCP endpoint and its documentation live

    Open the MCP swagger documentation share panel

    Show the generated swagger documentation link and QR code for this server

Confirm it worked

The server appears with 2 preconfigured tool(s): list_resource_group_health, list_service_health_events. The Connect section offers the MCP swagger documentation — a shareable page with setup instructions for any AI client.

Good to know

  • List current resource availability across an Azure resource group and review service health events affecting a subscription.
  • This integration requires a credential (bearer). Get one at https://portal.azure.com/.
  • Official API documentation: https://learn.microsoft.com/en-us/rest/api/resourcehealth/
  • Editing a tool later never changes the template — templates are starting points, and the server is fully yours after creation.

Related

Tutorial video