🧠 Azure Self Help MCP Server

Created By
akshaykokanea year ago
This is MCP server for Azure Help APIs for Guided Troubleshooter
Overview

What is Azure Self Help MCP Server?

Azure Self Help MCP Server is a hands-on implementation of the Model Context Protocol (MCP) designed to enable intelligent agents to troubleshoot Azure resources step-by-step using the Azure Self Help API.

How to use Azure Self Help MCP Server?

To use the server, connect it to an MCP Host (like Claude or Semantic Kernel) and initiate a troubleshooter session by asking the agent to guide you through the troubleshooting process.

Key features of Azure Self Help MCP Server?

  • Interactive AI assistant for Azure diagnostics
  • Ability to create and manage troubleshooting sessions
  • Integration with Azure's Guided Troubleshooter API

Use cases of Azure Self Help MCP Server?

  1. Troubleshooting SSH issues with Azure VMs.
  2. Guiding users through common Azure resource problems.
  3. Automating diagnostic workflows for Azure services.

FAQ from Azure Self Help MCP Server?

  • What is the purpose of this server?

It automates common diagnostic workflows for Azure resources using AI.

  • What are the prerequisites to set it up?

You need .NET 8 SDK, Azure CLI, and an MCP Host like Claude.

  • How does it enhance Azure diagnostics?

It allows for agent-native debugging, empowering AI applications with cloud intelligence.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
akshaykokane
Star
0
Language
C#
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago