Connects Claude to your Liongard platform for managing IT documentation and monitoring across client environments. The server exposes 25 tools organized around a decision tree architecture: you start with navigation, then get domain-specific tools for inspectors, systems, metrics, alerts, users, groups, and integrations. It supports both Liongard API v1 and v2, so you can pull timeline data, query detections, check environment health, or manage user access without leaving your conversation. Built by Wyre Technology with 118 tests covering the toolset. Best when you're working in Claude and need to check system status, investigate alerts, or pull metrics from your Liongard deployment.
An MCP (Model Context Protocol) server for interacting with the Liongard platform. Provides AI assistants with tools to manage inspectors, systems, metrics, alerts, users, and more through Liongard's API.
[!IMPORTANT] Before you click: this server depends on
@wyre-technology/node-liongard, which is hosted on the GitHub Packages npm registry. GitHub Packages has no anonymous access — even though the package is public, everynpm installneeds a token. The cloud builder runsnpm installfor you, so you must give it one, or the build fails withnpm error 401 Unauthorized ... npm.pkg.github.com.
- Create a GitHub Personal Access Token with the
read:packagesscope (classic token). Any GitHub account works — you do not need to be a member of thewyre-technologyorg to read its public packages.- Add it as a build variable when prompted by the deploy flow:
- Cloudflare Workers → set a build variable named
NODE_AUTH_TOKENto your PAT (Workers → Settings → Build → Variables and Secrets).- DigitalOcean App Platform → set an encrypted env var named
GITHUB_TOKENwith scope Build Time to your PAT (the Dockerfile reads it for the install).
This project depends on @wyre-technology/node-liongard, published to the
GitHub Packages npm registry, which requires a token even for public packages.
Authenticate once, then install:
# Authenticate npm to GitHub Packages (token needs the read:packages scope)
export NODE_AUTH_TOKEN=$(gh auth token) # or a PAT with read:packages
npm install
The repo's .npmrc already points the @wyre-technology scope at GitHub Packages and
reads the token from NODE_AUTH_TOKEN, so no further config is needed.
Set the following environment variables:
| Variable | Description |
|---|---|
LIONGARD_URL | Your Liongard instance URL |
LIONGARD_ACCESS_KEY | API access key |
LIONGARD_ACCESS_SECRET | API access secret |
npm start
npm run build # Build the project
npm run test # Run tests
npm run lint # Run linter
npm run typecheck # Type-check
LIONGARD_API_KEY*secretLiongard API access key (access key ID and secret combined per Liongard auth scheme)
LIONGARD_INSTANCE*Liongard instance hostname (e.g. yourorg.app.liongard.com)
MCP_TRANSPORTdefault: stdioTransport mode for the server. Set to 'stdio' for local CLI use; the image defaults to 'http' for gateway hosting.
AUTH_MODEdefault: envCredential source: 'env' reads vars locally, 'gateway' expects header injection from the WYRE MCP Gateway.
LOG_LEVELdefault: infoLog verbosity: debug, info, warn, error
com.mcparmory/google-sheets
domdomegg/google-sheets-mcp
henilcalagiya/google-sheets-mcp
cct15/war-dashboard-data
moooonad/mcp-google-sheets-full
io.github.br0ski777/csv-to-json