Server Health Monitor

Surfaces servers short on disk, long overdue for a reboot or running with stopped critical services, plus domain controllers, SQL Server instances and the cloud versus on-prem split.

The Server Health Monitor skill uses Lansweeper inventory data joined to Windows service data to assess the server fleet. It reports uptime, disk pressure, domain controllers, SQL Server inventory by version, cloud versus on-prem distribution and auto-start services that are not running. It is also the entry point for cloud-estate questions across Azure, AWS and GCP, and gives infrastructure teams a triage list before problems turn into incidents.

Why the Server Health Monitor Matters Here

  • IT perspective

    “Which servers need attention before they cause an incident?”

    • Low-disk and long-uptime servers become an ordered triage list.

    • Stopped auto-start services are named per server so they can be restarted.

  • Security perspective

    “Which critical servers are unhealthy or unaccounted for?”

    • Domain controllers and SQL Server instances are listed with their state, so none go unwatched.

    • The cloud versus on-prem split shows where the server estate actually lives.

Beta

Lens Workbench

Ask your asset data a question. Get a straight answer.

Lens Workbench is a dedicated space where you can ask questions about your asset data and get straight answers, build live reports that stay current, connect your existing tools through MCP connectors, and take action directly, like adding or retiring an asset.

Requirements

Lansweeper MCP

https://mcp.lansweeper.com/mcp

Lansweeper plan

Starter, Pro, Enterprise

LLM

Claude 3.5+, ChatGPT, Gemini (Antigravity), Copilot, Lens Workbench (closed beta)

Step by step setup guide

Step 1: Download
Download the skill package for your platform. Lens Workbench users can skip this step.

Step 2: Install

  • Claude: install as a skill in Claude Desktop or Claude Code.
  • ChatGPT: add the skill to your ChatGPT (Codex) skills folder.
  • Gemini (Antigravity): load the skill into your Antigravity agent’s skill folder.
  • Copilot: add it as a skill in GitHub Copilot, or import it into Copilot Studio.
  • Lens Workbench: request access to the closed beta at Lansweeper Beta Program. Once you have access, the skill is already in the workbench.

Step 3: Connect Lansweeper
The skill needs your Lansweeper data to return results.

  • Claude: connect the Lansweeper MCP connector and sign in.
  • ChatGPT: connect Lansweeper MCP, EU or US endpoint based on your tenant.
  • Gemini (Antigravity): connect a Lansweeper MCP connector separately; Gemini doesn’t ship one built in.
  • Copilot: connect the Lansweeper MCP connector to your agent.
  • Lens Workbench: select the site(s) you want to run the skill on.

Step 4: Ask

  • Claude: “List all domain controllers and verify they’re healthy.” or “Servers up more than 90 days without a reboot.”
  • ChatGPT: trigger with $server-health-monitor or “Servers up more than 90 days without a reboot.”
  • Gemini (Antigravity): “Which servers run SQL Server? Group by version.”
  • Copilot: “List servers with stopped critical services.”
  • Lens Workbench: type /server-health-monitor in the prompt box.