SSyncDev

Windows Server MCP Server

Agentless Windows Server health checks over WinRM: one verdict per server, a diffable inventory

Local serverstdio

What is the Windows Server MCP Server?

Windows Server MCP is an MCP integration. Agentless Windows Server health checks over WinRM: one verdict per server, a diffable inventory.

Packages and local setup

The published mcpb package is https://github.com/Servosity/msp-skills/releases/download/windows-server-v0.1.4/windows-server-mcp.mcpb, version 0.1.4. Its declared MCP transport is stdio.

The package declares WINDOWS_SERVER_PASSWORD (required): Password for the WinRM account shared by servers that have no password stored with servers login.; WINDOWS_SERVER_USERNAME (required): WinRM account name (a local or domain account in the server's Administrators group).; WINDOWS_SERVER_MCP_READ_ONLY: Optional. Set to exactly 1 to offer only tools that change nothing: services restart, services start, health and inventory snapshot are removed. Leave blank to keep every tool available.; WINDOWS_SERVER_NO_LOCAL_DATA: Optional. Set to 1 to keep no local store: health prints verdicts without recording history or events, and inventory snapshot is refused. Leave blank to keep the local store.; WINDOWS_SERVER_MCP_HTTP_TOKEN: Required only when running the MCP server with --transport http (a remote/hosted deployment). Callers must send a matching Authorization: Bearer header. Not needed for the default local stdio transport that Claude Desktop uses.; WINDOWS_SERVER_BASE_URL: Leave blank. The CLI's internal request surface is the fixed https://winrm.invalid; any other value is refused. Servers come only from the config file's [[servers]] entries.; WINDOWS_SERVER_USER_AGENT: Optional. Overrides the User-Agent the CLI sends on WinRM requests. Leave blank to use the CLI's own built-in User-Agent.; PRINTING_PRESS_CLIENT_PROFILE: Only for tenant-gated multi-client deployments: binds the MCP server to an existing Printing Press client profile. Leave blank for a single-tenant install..

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository. This profile uses version 0.1.4 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related other integrations MCP servers for tools that cover the same kind of work.

Configuration

VariableDescriptionRequired
WINDOWS_SERVER_PASSWORDPassword for the WinRM account shared by servers that have no password stored with servers login.Yes
WINDOWS_SERVER_USERNAMEWinRM account name (a local or domain account in the server's Administrators group).Yes
WINDOWS_SERVER_MCP_READ_ONLYOptional. Set to exactly 1 to offer only tools that change nothing: services restart, services start, health and inventory snapshot are removed. Leave blank to keep every tool available.Check documentation
WINDOWS_SERVER_NO_LOCAL_DATAOptional. Set to 1 to keep no local store: health prints verdicts without recording history or events, and inventory snapshot is refused. Leave blank to keep the local store.Check documentation
WINDOWS_SERVER_MCP_HTTP_TOKENRequired only when running the MCP server with --transport http (a remote/hosted deployment). Callers must send a matching Authorization: Bearer header. Not needed for the default local stdio transport that Claude Desktop uses.Check documentation
WINDOWS_SERVER_BASE_URLLeave blank. The CLI's internal request surface is the fixed https://winrm.invalid; any other value is refused. Servers come only from the config file's [[servers]] entries.Check documentation
WINDOWS_SERVER_USER_AGENTOptional. Overrides the User-Agent the CLI sends on WinRM requests. Leave blank to use the CLI's own built-in User-Agent.Check documentation
PRINTING_PRESS_CLIENT_PROFILEOnly for tenant-gated multi-client deployments: binds the MCP server to an existing Printing Press client profile. Leave blank for a single-tenant install.Check documentation