Liongard MCP
io.github.Servosity/liongard-mcp
Documentation
Liongard + 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 the Liongard API. Not affiliated with, endorsed by, or sponsored by Liongard, Inc.
▶ Watch the 30-second demo - demo data is simulated; every command shown exists in the real CLI.
Every Liongard endpoint, plus an offline copy of your whole MSP estate you can join, search, and drift-check from one command. 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):
| Your AI agent | How to install the Liongard skill |
|---|---|
| Claude Desktop | Run installer, then Settings > Extensions to register liongard-mcp (no JSON editing). |
| ChatGPT (paid plans) | Run installer, expose liongard-mcp over HTTPS, register as a Developer Mode connector. |
| Codex CLI | Paste the install prompt below. |
| Claude Code | Paste the install prompt below. |
| Claude Cowork | Paste the install prompt below. |
| GitHub Copilot (VS Code) | Run installer, add liongard-mcp to mcp.json under the servers key, then pick Agent mode. |
For ChatGPT, the Liongard MCP server is stdio - to use it with ChatGPT you expose it over HTTPS via the mcp-remote bridge or your own endpoint. 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.
| Agent | What it takes |
|---|---|
| Microsoft 365 Copilot / Copilot Studio | Not self-serve. Host liongard-mcp over HTTPS, then wire it into Copilot Studio (Tools > Add a tool > Model Context Protocol > Server URL) or a declarative agent. Needs a Copilot Studio license + tenant admin. See mcp-install.md. |
| Google Gemini | Gemini CLI is local - same as Claude Code. The Gemini app is remote - same HTTPS path as ChatGPT. See mcp-install.md. |
Skill-native agents (also covered): Hermes and OpenClaw read this skill's
SKILL.mddirectly 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.
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 Liongard MCP (.mcpb) - then open Claude Desktop > Settings > Extensions and select the file. One click, no JSON, no shell. (Browse every Liongard 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 liongard@msp-skills
Path A - paste one prompt into your AI agent (recommended)
Copy this into Claude Code, Codex CLI, or Claude Cowork:
Install the Liongard 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/liongard/install.sh). If it uses Windows PowerShell, runiwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/liongard/install.ps1 | iex. Then authenticate per the README and runliongard-cli --helpto 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/liongard/install.ps1 | iex
macOS / Linux:
bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/liongard/install.sh)
The installer drops both liongard-cli (the CLI) and liongard-mcp (the MCP server) into your user bin path. Claude Code, Codex, and Cowork discover the Skill via SKILL.md in this directory.
Verify:
liongard-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/liongard/install.sh)
Windows (PowerShell):
iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/liongard/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 liongard@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 and 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/liongard --force
Inside a Hermes chat session:
/skills install servosity/msp-skills/skills/liongard --force
Hermes speaks MCP natively, so it can also use the liongard-mcp server directly - same install path, same env vars.
Install for OpenClaw
Tell your OpenClaw agent (copy this):
Install the liongard skill from https://github.com/servosity/msp-skills/tree/main/skills/liongard. The skill defines how its required CLI (
liongard-cli) can be installed via theopenclaw:frontmatter block.
OpenClaw isn't generally available yet; the frontmatter wiring is pre-shipped and will activate the moment OpenClaw launches.
Authenticate
Set the credentials the CLI needs (from your Liongard portal):
LIONGARD_INSTANCE=<your-subdomain> LIONGARD_API_KEY=<value> liongard-cli doctor
LIONGARD_INSTANCE(required) is your Liongard subdomain - theacmeinhttps://acme.app.liongard.com. It builds the API URL; if you leave it unset the CLI falls back to the placeholderexample.app.liongard.com, which will not reach your data, so always set it. (Advanced: setLIONGARD_BASE_URLinstead to point at a full custom URL.)LIONGARD_API_KEY(required) is your base64 X-ROAR-API-KEY. Prefer to keep the parts separate? SetLIONGARD_ACCESS_KEY_IDandLIONGARD_ACCESS_KEY_SECRETand the CLI composes the header for you.LIONGARD_ENDPOINTS_API_KEY(optional) is only needed for the Liongard Endpoints API surface; leave it unset if you do not use it.
doctor confirms the credentials work before you run anything that touches data.
What this skill does
Run liongard-cli sync once first - the cross-estate commands below (drift, health, coverage, the stale/offline/failure rollups, metrics pivot) read your local mirror, so they return empty until the first sync populates it.
| Question your MSP keeps asking | Command |
|---|---|
| What changed across all my clients in the last 24h? | liongard-cli drift --since 24h |
| Which collectors (launchpoints) have gone stale? | liongard-cli launchpoints stale --older-than 7d |
| Which agents are offline, and whose environment do they serve? | liongard-cli agents offline |
| Give me one health scorecard for the whole estate. | liongard-cli health --agent |
| Show one client's complete picture in a single command. | liongard-cli environments overview 42 |
| Which inspections failed or errored across the estate? | liongard-cli detections failures --since 7d |
| Pull one metric across every system, CSV-ready for a report. | liongard-cli metrics pivot "MFA Enabled Count" --csv |
| Which systems breach a threshold (e.g. patch age over 30 days)? | liongard-cli metrics breach "Patch Age Days" --op gt --value 30 |
| Where are my monitoring gaps? | liongard-cli coverage |
| Which environments are still missing a given inspector? | liongard-cli inspectors coverage --inspector "Microsoft 365" |
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 Liongard integrations and MCP servers proxy each question into a live API call. That's fine for one record. It dies at scale, when you're asking "what changed across all 40 clients this week" or "which of my 600 launchpoints went stale" - questions that become dozens of paginated API calls.
This skill syncs Liongard into a local SQLite mirror with full-text search. Aggregate questions become one local SQL join: instant, offline, and the AI sees the answer, not the raw data. Compound commands like drift, health, and metrics pivot join across environments, systems, launchpoints, agents, and detections in one shot - work a stateless API wrapper can't do.
The pain this closes
Liongard is one of the most data-rich tools in the MSP stack - and one of the hardest to operationalize. The recurring theme in r/msp threads about Liongard is the same: it collects an enormous amount of configuration and change data, but the value is locked behind clicking into one environment at a time. Two pains show up over and over:
- Silent decay. A launchpoint goes stale or an agent drops offline and just stops collecting. Nobody notices until a QBR or an audit needs the data - and the "documentation" has quietly rotted.
liongard-cli launchpoints staleandliongard-cli agents offlinesurface it estate-wide in one command. - Reporting is manual. One metric across every system, or every failed inspection estate-wide, means clicking environment by environment or a one-off API script.
liongard-cli metrics pivot,liongard-cli detections failures, andliongard-cli healthanswer it in a single line.
See pain-point.md for the longer narrative.
Frequently asked questions
Does this work with ChatGPT?
Yes, on Plus, Pro, Team, Business, Enterprise, and Education plans (Free tier does not yet expose Developer Mode). ChatGPT connects to remote MCP servers over HTTPS, not local stdio binaries. The Liongard MCP server is local, so for ChatGPT you expose it via the mcp-remote bridge or your own HTTPS endpoint. Step-by-step in mcp-install.md.
Does this work with Codex, Cursor, Windsurf, Cline, Copilot, or Gemini?
Yes - all of them speak MCP. Cross-tool install commands are in the matrix above and the deep-dive in docs/which-agent.md.
Do I need to know how to code?
No. The recommended install is to paste one sentence into Claude Code or Codex - your agent reads SKILL.md and does the install. The fallback is a one-line installer per OS (bash or PowerShell). Neither path requires writing code. You'll enter your Liongard credentials once.
Is my Liongard data safe?
Your data stays on your machine. The CLI and MCP server are local binaries. The SQLite mirror sits in a directory under your user account. The AI agent only sees what the CLI returns - typically a query result, not raw bulk data. Credentials are read from your environment or your agent's config; never bundled into this repo or transmitted anywhere by MSP Skills.
Do I need to be a Liongard customer, and will this hit my API limits?
Yes - you use your own Liongard instance and access keys, so the skill only reaches data your credentials already permit. Because it syncs once into a local mirror and answers most questions from there, it makes far fewer API calls than a per-question live wrapper, which keeps you well clear of rate limits during reporting and QBR prep.
Will this replace my Liongard portal?
No - it complements it. The portal is built for clicking into one environment at a time; this skill answers the cross-estate questions (drift, stale collectors, offline agents, coverage gaps, one metric across every system) in a single command you can pipe into a report or hand to your AI agent.
What does it cost?
Free. Apache-2.0 licensed. You pay only for whichever AI agent you use (Claude, ChatGPT, Codex, etc.), and that's billed by your AI provider, not by us.
Safety model
| Tier | Examples | Recommended agent policy |
|---|---|---|
| Read | drift, health, coverage, launchpoints stale, agents offline, detections failures, metrics pivot, search, and every get/list/count | Allow |
| Write (routine) | environments create/update, launchpoints launchpoint/update/update-bulk, metrics create/update, users create/update, agents update, import, and inspection triggers (launchpoints run/bulk-run/run-stale, agents flush job-queue) | Preview with --dry-run, then a reviewed write |
| Destructive / credential | environments delete, launchpoints delete/bulk-delete, metrics delete, users delete, agents delete, access-keys create/delete, and the authentication/auth token commands | Human-in-the-loop only |
The strongest control is the scope you grant the Liongard credentials - the CLI can only do what the credentials are permitted to do. Full details, including how to lock it down, are in governance.md.
Status
Beta. Validated against the Liongard API surface. The next step is live validation with MSPs running it against their own production tenant in our weekly Build Sessions - RSVP at compoundingteams.com/build-sessions.
Standards. Conforms to the open Agent Skills spec (Anthropic, Dec 2025; 40+ agents). MCP-compatible - works with any MCP-capable agent including Hermes. OpenClaw-ready (frontmatter pre-wired, awaiting OpenClaw launch).
Maintained by Servosity. Apache-2.0 licensed. Built with CLI Printing Press. Last updated: 2026-06-06.