Back to Browse

Liongard MCP Server

Developer ToolsUse Caution4.2MCP RegistryLocal
Free

Server data from the Official MCP Registry

MCP server for Liongard — inspectors, environments, metrics, detections, and timeline data.

About

MCP server for Liongard — inspectors, environments, metrics, detections, and timeline data.

Security Report

4.2
Use Caution4.2High Risk

The Liongard MCP server is a well-structured tool for interacting with the Liongard platform API. Authentication is properly required via environment variables, and the codebase shows good security practices with TypeScript, linting, and comprehensive testing. However, there are moderate concerns around environment variable handling in the bundled UI code and potential for over-permissive API access depending on Liongard credentials. Supply chain analysis found 5 known vulnerabilities in dependencies (0 critical, 2 high severity).

3 files analyzed · 11 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

env_vars

Check that this permission is expected for this type of plugin.

HTTP Network Access

Connects to external APIs or services over the internet.

File System Read

Reads files on your machine. Normal for tools that analyze or process local data.

File System Write

Writes or modifies files on your machine. Check that this is expected for the tool.

What You'll Need

Set these up before or after installing:

Liongard API access key (access key ID and secret combined per Liongard auth scheme)Required

Environment variable: LIONGARD_API_KEY

Liongard instance hostname (e.g. yourorg.app.liongard.com)Optional

Environment variable: LIONGARD_INSTANCE

Transport mode for the server. Set to 'stdio' for local CLI use; the image defaults to 'http' for gateway hosting.Optional

Environment variable: MCP_TRANSPORT

Credential source: 'env' reads vars locally, 'gateway' expects header injection from the WYRE MCP Gateway.Optional

Environment variable: AUTH_MODE

Log verbosity: debug, info, warn, errorOptional

Environment variable: LOG_LEVEL

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "io-github-wyre-ai-liongard-mcp": {
      "env": {
        "AUTH_MODE": "your-auth-mode-here",
        "LOG_LEVEL": "your-log-level-here",
        "MCP_TRANSPORT": "your-mcp-transport-here",
        "LIONGARD_API_KEY": "your-liongard-api-key-here",
        "LIONGARD_INSTANCE": "your-liongard-instance-here"
      },
      "args": [
        "-y",
        "@wyre-ai/liongard-mcp"
      ],
      "command": "npx"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

Liongard MCP Server

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.

One-Click Deployment

[!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, every npm install needs a token. The cloud builder runs npm install for you, so you must give it one, or the build fails with npm error 401 Unauthorized ... npm.pkg.github.com.

  1. Create a GitHub Personal Access Token with the read:packages scope (classic token). Any GitHub account works — you do not need to be a member of the wyre-technology org to read its public packages.
  2. Add it as a build variable when prompted by the deploy flow:
    • Cloudflare Workers → set a build variable named NODE_AUTH_TOKEN to your PAT (Workers → Settings → Build → Variables and Secrets).
    • DigitalOcean App Platform → set an encrypted env var named GITHUB_TOKEN with scope Build Time to your PAT (the Dockerfile reads it for the install).

Deploy to DO

Deploy to Cloudflare Workers

Features

  • Decision-tree tool architecture — starts with a navigation tool, then exposes domain-specific tools on demand
  • 25 tools across inspectors, systems, metrics, alerts, users, groups, environments, and integrations
  • Interactive detection card via MCP Apps (SEP-1865): liongard_detections_get renders as a read-only card in MCP Apps hosts (Claude Desktop/web) with severity/status badges and server-resolved system/environment names — neutral by default, brandable via window.__BRAND__ injection or MCP_BRAND_* env vars (MCP_BRAND_NAME, MCP_BRAND_LOGO_URL, MCP_BRAND_PRIMARY_COLOR, MCP_BRAND_ACCENT_COLOR, MCP_BRAND_BG, MCP_BRAND_TEXT), no rebuild needed
  • Dual API version support (v1 and v2)
  • 128 tests

Installation

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.

Configuration

Set the following environment variables:

VariableDescription
LIONGARD_URLYour Liongard instance URL
LIONGARD_ACCESS_KEYAPI access key
LIONGARD_ACCESS_SECRETAPI access secret

Usage

npm start

Development

npm run build       # Build the project
npm run test        # Run tests
npm run lint        # Run linter
npm run typecheck   # Type-check

License

Apache-2.0

Reviews

No reviews yet

Be the first to review this server!