Windows Server MCP

Windows Server + AI - for ChatGPT, Claude, GitHub Copilot, Microsoft 365 Copilot, Gemini, and any agent that speaks MCP

Unofficial. Community-built Claude Code Skill and MCP server for Windows Server. Not affiliated with, endorsed by, or sponsored by Microsoft Corporation.

▶ Watch the 30-second demo - demo data is simulated; every command shown exists in the real CLI.

Agentless Windows Server health checks over WinRM: one verdict per server, a diffable inventory, and no arbitrary PowerShell. Works with the AI you already use - ChatGPT (Plus/Pro+), Claude Desktop, Codex, Claude Code, Claude Cowork, and GitHub Copilot - plus Microsoft 365 Copilot / Copilot Studio and Google Gemini via the remote path. Free, open source, runs on your laptop. Built for MSP owners. No code required.

Works with your agent

The six agents MSP owners actually use (self-serve, works today):

For ChatGPT, run windows-server-mcp --transport http with WINDOWS_SERVER_MCP_HTTP_TOKEN set, on an HTTPS host; every request sends that token. See mcp-install.md.

Also for the Microsoft and Google stacks

Big install base, but an honest heads-up: these are the remote / enterprise path, not the local binary you just installed.

Skill-native agents (also covered): Hermes and OpenClaw read this skill's SKILL.md directly *and* speak MCP - see their install sections below. Also works with Cursor, Windsurf, Cline, Continue.dev, and Zed via MCP. Full per-tool wire-up: [docs/which-agent.md](../../docs/which-agent.md).

Run more than one agent? Install across all 51+ supported agents in one command: npx skills add Servosity/msp-skills@latest (requires Node.js, then run the per-skill installer for the CLI/MCP binaries). See docs/which-agent.md.

Install in 60 seconds

Fastest for Claude Desktop - one-click .mcpb

Download Windows Server MCP (.mcpb) - then open Claude Desktop > Settings > Extensions and select the file. One click, no JSON, no shell. (Browse every Windows Server release on the releases page.)

Prefer the Claude Code plugin? Add the marketplace once, then install - works immediately, no directory listing required:

/plugin marketplace add Servosity/msp-skills

/plugin install windows-server@msp-skills

Path A - paste one prompt into your AI agent (recommended)

Copy this into Claude Code, Codex CLI, or Claude Cowork:

Install the Windows Server Skill and MCP server from Servosity/msp-skills in this agent workspace. If this workspace uses a POSIX shell (macOS, Linux, WSL, or Bash), run bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/windows-server/install.sh). If it uses Windows PowerShell, run iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/windows-server/install.ps1 | iex. Then authenticate per the README and run windows-server-cli --help to explore.

The same prompt works in any agent that can run shell.

Path B - run the installer yourself

Windows (PowerShell):

iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/windows-server/install.ps1 | iex

macOS / Linux:

bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/windows-server/install.sh)

The installer drops both windows-server-cli (the CLI) and windows-server-mcp (the MCP server) into your user bin path. Claude Code, Codex, and Cowork discover the Skill via SKILL.md in this directory.

Verify:

windows-server-cli --version

Upgrade to the latest version

The installer always fetches the current release - re-run it to upgrade:

macOS / Linux:

bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/windows-server/install.sh)

Windows (PowerShell):

iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/windows-server/install.ps1 | iex

Claude Desktop .mcpb users: download the latest .mcpb (top of this section) and re-select it in Settings > Extensions. Claude Code plugin users: /plugin update windows-server@msp-skills.

Add to Claude Desktop, GitHub Copilot, Gemini CLI, Microsoft 365 Copilot, or another MCP client

After the installer runs, see [mcp-install.md](./mcp-install.md) and [docs/which-agent.md](../../docs/which-agent.md) for the per-agent wire-up - one section per agent, including the GitHub Copilot servers key and the remote Microsoft 365 Copilot / Copilot Studio path. Claude Desktop's Settings > Extensions panel is the simplest path; the MCP config block (for users who prefer editing JSON) is documented in mcp-install.md.

Install for Hermes

From the Hermes CLI:

hermes skills install servosity/msp-skills/skills/windows-server --force

Inside a Hermes chat session:

/skills install servosity/msp-skills/skills/windows-server --force

Hermes speaks MCP natively, so it can also use the windows-server-mcp server directly - same install path, same env vars.

Install for OpenClaw

Tell your OpenClaw agent (copy this):

Install the windows-server skill from https://github.com/servosity/msp-skills/tree/main/skills/windows-server. The skill defines how its required CLI (windows-server-cli) can be installed via the openclaw: frontmatter block.

OpenClaw isn't generally available yet; the frontmatter wiring is pre-shipped and will activate the moment OpenClaw launches.

Authenticate

Windows Server has no API key: the CLI signs in to each server's WinRM HTTPS listener (port 5986) with a local or domain account in that server's Administrators group. Add each server to the config file (default ~/.config/windows-server-cli/config.toml on macOS and Linux, %USERPROFILE%\.config\windows-server-cli\config.toml on Windows; override with --config or WINDOWS_SERVER_CONFIG):

[[servers]]

name = "fs01" host = "fs01.corp.example" auth = "ntlm" # or "basic" (HTTPS only) username = "CORP\\svc-monitor" cert_sha256 = "4B:EF:..." # or ca_file = "/path/to/ca.pem" for a private CA default = true

Then store its password (read from stdin, kept only in the CLI's 0600 credential store) and run the real connectivity test:

macOS / Linux:

windows-server-cli servers login fs01 --username 'CORP\svc-monitor' < password.txt

windows-server-cli servers list --agent windows-server-cli health --agent

Windows (PowerShell):

Get-Content password.txt | windows-server-cli servers login fs01 --username 'CORP\svc-monitor'

windows-server-cli servers list --agent windows-server-cli health --agent

Or share one account across servers with WINDOWS_SERVER_USERNAME and WINDOWS_SERVER_PASSWORD. Passwords shorter than 8 characters are refused. With NTLM, a local account other than the built-in Administrator gets HTTP 401 unless LocalAccountTokenFilterPolicy is 1 on the server: use a domain account, or auth = "basic" over HTTPS. doctor checks config and paths and reports whether credentials are present; it does not contact a server. health is the connectivity test.

What this skill does

health, services down, eventlog new, local-admins changes and inventory snapshot read every configured server; the single reads and the service actions act on one server (--server , or the entry marked default = true).

Full command reference: guide.md. For the AI-agent operating contract (--agent, --dry-run, when to confirm before mutating), see AGENTS.md.

What makes this different

Most ways to put an AI on a Windows server hand it a PowerShell prompt. This one cannot run arbitrary script: every command is one of a fixed set of read scripts that ship inside the binary, checked by SHA-256 on the server before they run, with arguments validated and passed as typed data. The server comes from your config by name (never from the agent), certificate verification is always on, and nothing is installed on the server.

On top of the reads, compound commands do work a single PowerShell call cannot: health rolls every check into one verdict per server and remembers how long each has failed, services down pairs each stop with its Service Control Manager event, eventlog new compares against the server's own history, and inventory snapshot plus inventory diff keep a local SQLite history so you see what changed between runs.

The pain this closes

Daily server checks are still a manual round on many MSP desks. The Active Directory Pro Windows Server maintenance checklist has you "monitor critical server services" every day, review disk space weekly, and check Event Viewer's application, security and system logs "for any c