AI analysis with MCP

Ask your enrollments anything.

Autopilot Monitor records every enrollment as structured data. Connect the AI assistant you already use and ask in plain language, about one device or the whole fleet.

Works inClaudeChatGPTVS Code & GitHub CopilotClaude CodeCodexGemini CLISelf-hosted clients

Included in every plan · read-only · Microsoft sign-in

Structured from the start

Your assistant reads facts, not log files.

The agent turns each enrollment into typed events while it runs. Your assistant queries them through dedicated tools, so its answers rest on data instead of guesswork.

On the deviceAppWorkload.log
<![LOG[[Win32App] Admin did NOT set mapping for lpExitCode: 60001]LOG]!><time="11:14:58.5124" date="10-1-2026" component="AppWorkload" context="" type="1" thread="18" file="">

One line among thousands, spread over several log files.

In Autopilot Monitortyped event
event
app_install_failed
app
Contoso CRM 4.2
exit code
60001 · no mapping
phase
Device setup
attempt
1
install time
1 min 32 s
In your assistantplain language
“Contoso CRM exited with 60001, a code the app has no mapping for, so the ESP stopped. The retry an hour later installed cleanly.”
  • Sessions and phases

    Status, duration, phase timeline and reboots of every enrollment.

  • App installs

    Attempts, exit codes and install times per app, plus Delivery Optimization.

  • Errors, decoded

    Error codes with their meaning, IME log matches and rule findings.

  • Devices and network

    Model, TPM, OS build, connection type and, if enabled, location.

  • Software and CVEs

    Optional inventory matched against known CVEs, ranked by KEV and EPSS.

  • Knowledge built in

    Analysis rules, the error-code catalog and the product docs.

Try it

Questions teams ask every day.

Pick a question to see which tools the assistant calls and what comes back. All answers use sample data.

How the connection works

Built-in prompts such as investigate-failed-session and cve-exposure-audit give your assistant a head start.

Claude on the web, desktop or mobile, or ChatGPT.

Enrollment questionsAutopilot Monitor
CONTOSO-3812 failed enrollment this morning. What happened?
search_sessionsget_session_summary
Assistant

Two attempts today. The first failed, the retry succeeded.

  • ✗ Failed 11:05–11:17 · ESP error 0x8007EA61 · 7 of 8 apps
  • ✓ Succeeded 12:05–12:20 · 8 of 8 apps

Cause: Contoso CRM exited with 60001. The Win32 app has no mapping for that code, so the ESP stopped. 0x8007EA61 is 60001 as an HRESULT.

60001 is PSADT's generic code for an unhandled error.

Fix: map 60001 to retry, or handle the error inside the package.

Ask a follow-up…

Sample data. The tools and the shape of each answer are real.

Bring your own AI

We provide the data. You pick the AI.

MCP is an open standard for connecting AI assistants to data. Use the assistant your organization already approved, wherever its model runs.

Where should the model run?

Pick one. The data and the tools stay the same.

Yours
Your devices

The agent records each enrollment while it runs.

Autopilot Monitor
Autopilot Monitor
Enrollment dataAnalysis rulesError-code catalogProduct docs
MCP serverread-only

Answers tool calls. Calls no AI provider itself.

Yours
Your AI client
Chat appClaude, ChatGPT
Code editorVS Code with GitHub Copilot
Terminal agentClaude Code, Codex, Gemini CLI
Self-hosted front endregistered once by a Tenant Admin
Automationits own app identity
Your choice
The model
Your AI vendor's cloudunder your agreement with them
Your cloud subscriptiona model you deploy yourself
Your own hardwarea local model on your servers
Reaches Autopilot Monitor: telemetry from your devices, tool calls from your assistant.Never reaches Autopilot Monitor: your prompts and the model's answers.

Typical clients

Claude on web, desktop and mobile. ChatGPT.

Who processes the conversation

Your AI vendor, under the agreement your organization already has with them.

What you set up

Add the server URL as a connector and sign in with Microsoft. Nothing to register.

  • Read-only tools

    Your assistant reads. Sessions, rules and settings stay untouched.

  • Microsoft sign-in

    Work accounts through Microsoft Entra ID. There are no API keys to hand out.

  • Your portal role

    The assistant sees exactly what the person's role allows in the portal.

  • Access follows the role

    Remove a role or block an account, and access ends within minutes.

Connect

Connected in a minute.

There are no API keys and no local server to install. You need a role in your organization's Autopilot Monitor tenant.

Setup guide for every client
  1. 1

    Add the server

    Paste this URL as a custom connector or MCP server in your client.
    https://mcp.autopilotmonitor.com/mcp
  2. 2

    Sign in with Microsoft

    Your browser opens the Microsoft sign-in. Use the work account you use for Autopilot Monitor.
  3. 3

    Ask your first question

    For example: “Which enrollments failed this week, and why?”

Your enrollment data has the answers. Start asking.

Get started

Free, open source, deployed in minutes.
Need SLAs, support, or MSP delegation? There's a Pro plan.