Oliver Kieselbach
b4529d2c71
Workaround for clients (e.g. Claude Code's HTTP-MCP bridge in stateless mode) that don't expose `resources/list` reliably. Verified with a paired in-memory client that the server itself advertises `capabilities.resources` and answers `resources/list` correctly — the breakage is on the client side. Tools work everywhere, so a tool-call gateway is the pragmatic fix. Resources now share a single source-of-truth (`resource-catalog.ts`) used by both the MCP-protocol resource handlers and the new `get_resource(name)` tool. Tool descriptions previously said "see the device_properties resource" — updated to "call get_resource(name=...)" so the hint actually leads somewhere usable. Also tightens get_rule_stats description: the default window × number of rules × per-day trend can easily exceed the response cap, so the doc now recommends passing a tighter date range or ruleType filter for routine queries. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Autopilot Monitor
Advanced monitoring and troubleshooting solution for Windows Autopilot deployments. Gain full visibility into every enrollment session with a detailed event timeline, fleet health dashboards, and session reporting. Define custom analysis rules to automatically detect issues and gather rules to collect targeted evidence. Retrieve diagnostics packages on demand, configure agent settings like auto-reboot behavior and automatic timezone adjustment — all managed centrally from the web dashboard.
Private Preview
Autopilot Monitor is currently running as a Private Preview. Visit autopilotmonitor.com to request access and learn more.
Overview
Autopilot Monitor provides real-time tracking, intelligent diagnostics, and automated troubleshooting for Windows Autopilot enrollment processes. It consists of:
- Bootstrap Script — PowerShell script deployed via Intune that starts monitoring early in the enrollment process
- Monitoring Agent — Lightweight .NET application that collects telemetry and evidence during enrollment
- Backend API — Azure Functions-based ingestion and processing pipeline
- Web Dashboard — Next.js application for real-time monitoring and fleet analytics
Architecture
For detailed information about the system architecture, components, and data flow, see Architecture Documentation.
Documentation
Full documentation is available at autopilotmonitor.com/docs
License
This project uses a split licensing model:
- MIT License — Agent (
src/Agent/) and Shared library (src/Shared/) — unrestricted use on end-user devices - AGPL-3.0 — Backend (
src/Backend/), Web Dashboard (src/Web/), and MCP Server (src/McpServer/) — server-side components remain open source
See LICENSE for full details.