Nerdio Manager MCP — Claude Code MCP server: setup and overview
An MCP server for the Nerdio Manager for MSP API without PowerShell. It helps audit multi-tenant Azure Virtual Desktop environments and track background jobs via AI agents.
Open on GitHubWhat Nerdio Manager MCP does
This server connects coding assistants to the Nerdio Manager for MSP API. It handles cross-tenant Azure Virtual Desktop inspections, offline queries, and asynchronous job monitoring. You do not need to assemble PowerShell scripts for routine fleet checks.
The package supplies two binaries: the nerdio-cli tool and the nerdio-mcp executable. Each assistant invokes the server locally across macOS, Linux, or Windows.
Network exposure is a critical security risk here. Running --transport http opens an unauthenticated listener across all local network interfaces, so stick strictly to the default stdio transport.
What it helps with
- inspect Azure Virtual Desktop hosts across client tenants
- check the progress of background jobs in Nerdio Manager
- search desktop fleet parameters offline without script writing
- audit AVD configurations without manual PowerShell sessions
Example prompts for the agent
- Audit all Azure Virtual Desktop session pools across accounts using Nerdio
- List recent asynchronous jobs and flag failed tasks in Nerdio Manager
- Query our Nerdio configuration offline to review host allocations
How to install Nerdio Manager MCP
Install
The MCP registry has no launch command for it: see the repository README
Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about Nerdio Manager MCP
How to install Nerdio Manager MCP in Claude Code?
Add the repository marketplace using /plugin marketplace add Servosity/msp-skills, then run /plugin install nerdio@msp-skills. You can also execute the installer script provided in the repository.
What does Nerdio Manager MCP do?
It gives AI assistants direct access to the Nerdio Manager for MSP API. Users can inspect AVD deployments, perform offline searches, and manage background tasks without PowerShell.
Why should you avoid HTTP transport with this server?
The current implementation of --transport http lacks authentication and listens on every interface. Any local webpage could reach it, so always keep the agent on stdio transport.
