Context7
Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.
Description from the maker (original English)
Liongard config visibility: sync your estate offline, then drift-check and search it from one CLI.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
LIONGARD_ACCESS_KEY_ID, LIONGARD_ACCESS_KEY_SECRET, LIONGARD_API_KEY, LIONGARD_BASE_URL, LIONGARD_ENDPOINTS_SESSION_TOKEN_AUTH, LIONGARD_INSTANCE, LIONGARD_MCP_HTTP_TOKEN, LIONGARD_MCP_READ_ONLY, LIONGARD_NO_LOCAL_DATA, LIONGARD_USER_AGENT, PRINTING_PRESS_CLIENT_PROFILEValues marked secret are keys to your account. Never share them or paste them into a chat.
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Download the maker’s .mcpb file
The link goes to the maker’s own file; we do not host or repackage it. Open the file and Claude Desktop installs it.
Run this in your terminal
Fill in the empty values before running it.
Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
LIONGARD_BASE_URL envLIONGARD_MCP_READ_ONLY envLIONGARD_NO_LOCAL_DATA envLIONGARD_USER_AGENT envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified with the GitHub account servosity, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: LIONGARD_ACCESS_KEY_ID, LIONGARD_ACCESS_KEY_SECRET, LIONGARD_API_KEY, LIONGARD_ENDPOINTS_SESSION_TOKEN_AUTH, LIONGARD_INSTANCE, LIONGARD_MCP_HTTP_TOKEN, PRINTING_PRESS_CLIENT_PROFILE
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.1.8) reached the registry yesterday.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need MCPB on your computer.
In the same category: Context7, Codebase Memory, Exa
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
Connect AI agents to Exa for web search, content fetching, and multi-step research.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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 (desktop app), Claude Desktop, Codex, Claude Code, Claude Cowork, and GitHub Copilot - plus Gemini CLI. Free, open source, runs on your laptop. Built for MSP owners. No code required.
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 (desktop app) | Run installer, then add liongard-mcp in Settings > MCP servers as a local (STDIO) server. ChatGPT on the web is not supported yet. |
| 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. |
The ChatGPT desktop app runs liongard-mcp locally and shares MCP configuration with Codex (OpenAI). ChatGPT on the web needs a remote (HTTP) server, which msp-skills does not support yet (see Remote agents in mcp-install.md). If your team works there, a hosted gateway is the better pick; check that your AI app is on the gateway's setup list.
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 supported by msp-skills yet: it needs a remote server. A hosted gateway is the better pick; check that your AI app is on the gateway's setup list. |
| Google Gemini | Gemini CLI is local - same as Claude Code. See mcp-install.md. The Gemini app needs a remote server and is not supported by msp-skills yet. |
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](../../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.
.mcpbClaude Desktop bundle: the
.mcpblaunches on macOS (Intel and Apple Silicon), Windows x64 and Linux x64. Every tool shells out to the companionliongard-cli. Releases cut from 2026-09-18 on ship that CLI inside the bundle; older bundles contain only the MCP server, so if yours lacks the companion, run the Path A or Path B installer below first (or setLIONGARD_CLI_PATHto an existing binary). Details: #331.
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
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.
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
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.
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 ChatGPT desktop app. 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.
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.
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.
Set the credentials the CLI needs (from your Liongard portal):
LIONGARD_INSTANCE=<your-subdomain> LIONGARD_API_KEY=<value> liongard-cli doctor
acme in https://acme.app.liongard.com. It builds the API URL; if you leave it unset the CLI falls back to the placeholder example.app.liongard.com, which will not reach your data, so always set it. (Advanced: set LIONGARD_BASE_URL instead to point at a full custom URL.)LIONGARD_API_KEY, your pre-encoded base64 X-ROAR-API-KEY (the line above), or the pair LIONGARD_ACCESS_KEY_ID + LIONGARD_ACCESS_KEY_SECRET, the two strings Liongard hands you, which the CLI encodes for you: LIONGARD_INSTANCE=<your-subdomain> LIONGARD_ACCESS_KEY_ID=<value> LIONGARD_ACCESS_KEY_SECRET=<value> liongard-cli doctor
Do not set both shapes: LIONGARD_API_KEY wins whenever it is non-empty and the ID/secret pair is ignored.
doctor confirms the credentials work before you run anything that touches data. It exits 0 even when the credential is rejected, so scripts should add --fail-on error.
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 until a full sync has finished they refuse and name the exact sync command to run.
| 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 |
| Which systems does one metric cover, CSV-ready for a report? | liongard-cli metrics pivot "MFA Enabled Count" --csv |
| 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.
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.
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 o
Only the beginning is shown; read the rest in the repo