azurehelp

The Azure Self Help MCP Server exposes Azure's Guided Troubleshooter API as MCP tools for an agent running in an MCP host (such as Claude Desktop or an SK App). It lets the agent start a troubleshooter session for a specific Azure resource, inspect the current step with instructions, provide responses to advance the flow, and finally end or restart the session. Available tools include: CreateTroubleshooter (start a new session for a resource), GetTroubleshooterStep (view the current step and guidance), ContinueTroubleshooter (respond to the current step’s query), EndTroubleshooter (terminate the session), and RestartTroubleshooter (begin again from step one).

To use it, connect the MCP host to this server using the provided MCP config. Once loaded, Claude or your host app will expose the methods as conversational actions. A typical workflow is: create a troubleshooter for a resource (ResourceURI), query the current step to see what the system asks, provide guidance or answers through ContinueTroubleshooter, and eventually EndTroubleshooter when the issue is resolved or RestartTroubleshooter to retry with a different angle. Documentation within the server code explains each tool’s purpose and expected parameters.

Prerequisites:

• .NET 8 SDK
• Access to Azure (CLI logged in)
• An MCP host (e.g., Claude App) to connect the MCP server to

Setup steps:

1. Acquire the repository and navigate to the server project directory.
2. Restore and build the project (or run directly if you prefer):

# If you have the source locally
dotnet restore
dotnet build

3. Run the MCP server:

# From the project directory or with an explicit project path
dotnet run --project /Users/yourname/Projects/AzureTroubleshooterServer --no-build

4. Configure your MCP host to connect to the server using the provided mcp config example (see README for the Claude Desktop settings). Ensure the path in the --project argument matches your environment.
5. Test the tooling by invoking CreateTroubleshooter with a resource URI and then following up with GetTroubleshooterStep and ContinueTroubleshooter as needed.

Notes and tips:

• The server uses DefaultAzureCredential for authentication; ensure your environment provides proper credentials (Azure CLI login, environment variables, or managed identity).
• The example path in the MCP config should be adjusted to your actual project location.
• If you modify the server code, rebuild or use --no-build carefully to reflect changes in your MCP host.
• The Self Help API and solutionId usage are demonstrated in the AzureTroubleshooterTools.cs example; replicate or adapt as needed for other resources.
• Common issues include misconfigured credentials, incorrect ResourceURI formats, or MCP host not detecting the tool set. Check MCP host logs for tool registration messages.