Liongard MCP Server

Liongard config visibility: sync your estate offline, then drift-check and search it from one CLI.

Local serverstdio

What is the Liongard MCP Server?

Liongard MCP is an MCP integration. Liongard config visibility: sync your estate offline, then drift-check and search it from one CLI.

Packages and local setup

The published mcpb package is https://github.com/Servosity/msp-skills/releases/download/liongard-v0.1.3/liongard-mcp.mcpb, version 0.1.3. Its declared MCP transport is stdio.

The package declares LIONGARD_ACCESS_KEY_ID: Liongard Access Key ID, the half that pairs with LIONGARD_ACCESS_KEY_SECRET; the server composes the two into the base64 X-ROAR-API-KEY. One of two ways to authenticate - set EITHER this pair OR the pre-encoded LIONGARD_API_KEY, never both. LIONGARD_API_KEY wins when it is set, so leave it blank to use this pair.; LIONGARD_ACCESS_KEY_SECRET: Liongard Access Key Secret, the other half of LIONGARD_ACCESS_KEY_ID. One of two ways to authenticate - set EITHER this pair OR the pre-encoded LIONGARD_API_KEY, never both. LIONGARD_API_KEY wins when it is set, so leave it blank to use this pair.; LIONGARD_API_KEY: Pre-encoded X-ROAR-API-KEY: base64 of 'accessKeyId:accessKeySecret'. One of two ways to authenticate - set EITHER this key OR the LIONGARD_ACCESS_KEY_ID + LIONGARD_ACCESS_KEY_SECRET pair, never both. This key wins when it is set, and the pair is ignored.; LIONGARD_BASE_URL: Full API base URL. Leave blank: the CLI builds it from LIONGARD_INSTANCE. Set it only to point at a different host.; LIONGARD_INSTANCE (required): Your Liongard subdomain (the 'acme' in acme.app.liongard.com); builds the API URL..

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository. This profile uses version 0.1.3 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related developer tools MCP servers for tools that cover the same kind of work.

Configuration

VariableDescriptionRequired
LIONGARD_ACCESS_KEY_IDLiongard Access Key ID, the half that pairs with LIONGARD_ACCESS_KEY_SECRET; the server composes the two into the base64 X-ROAR-API-KEY. One of two ways to authenticate - set EITHER this pair OR the pre-encoded LIONGARD_API_KEY, never both. LIONGARD_API_KEY wins when it is set, so leave it blank to use this pair.Optional
LIONGARD_ACCESS_KEY_SECRETLiongard Access Key Secret, the other half of LIONGARD_ACCESS_KEY_ID. One of two ways to authenticate - set EITHER this pair OR the pre-encoded LIONGARD_API_KEY, never both. LIONGARD_API_KEY wins when it is set, so leave it blank to use this pair.Optional
LIONGARD_API_KEYPre-encoded X-ROAR-API-KEY: base64 of 'accessKeyId:accessKeySecret'. One of two ways to authenticate - set EITHER this key OR the LIONGARD_ACCESS_KEY_ID + LIONGARD_ACCESS_KEY_SECRET pair, never both. This key wins when it is set, and the pair is ignored.Optional
LIONGARD_BASE_URLFull API base URL. Leave blank: the CLI builds it from LIONGARD_INSTANCE. Set it only to point at a different host.Optional
LIONGARD_INSTANCEYour Liongard subdomain (the 'acme' in acme.app.liongard.com); builds the API URL.Yes