Liongard MCP
Sync Liongard estate data offline, then drift-check and search configuration from your agent or CLI.
Overview
Liongard MCP is a MCP server for the Operate phase that syncs Liongard estate data offline and exposes drift-check and search tools to agents over stdio.
What is this MCP server?
- Liongard API integration with offline estate sync
- Drift-check and search workflows from CLI and MCP
- LIONGARD_INSTANCE subdomain plus LIONGARD_API_KEY (or access key id/secret pair)
- Optional LIONGARD_ENDPOINTS_API_KEY for extended endpoint coverage
- stdio mcpb v0.1.0 from Servosity msp-skills
- Server version 0.1.0
- stdio transport via mcpb package
- Required LIONGARD_INSTANCE plus API key authentication
Community signal: 1 GitHub stars.
What problem does it solve?
Finding config drift across a Liongard estate means leaving your agent to search consoles and compare historical inspections manually.
Who is it for?
Operators on Liongard who want faster config search and drift validation while shipping automation or client audits.
Skip if: Builders without Liongard or teams that only need generic cloud inventory unrelated to Liongard inspections.
What do I get? / Deliverables
Once instance and API credentials are set, you can sync locally and ask your agent to search or drift-check the estate from one MCP session.
- Offline Liongard estate sync usable from MCP and CLI
- Agent-invokable drift-check and search operations
- v0.1.0 mcpb Liongard MCP server
Recommended MCP Servers
Journey fit
How it compares
Liongard config-visibility MCP, not a cloud provisioning or penetration-testing skill.
Common Questions / FAQ
Who is Liongard MCP for?
It is for Liongard customers who want agents to search synced configuration data and run drift checks alongside the Servosity CLI.
When should I use Liongard MCP?
Use it during Operate when you review client environments, investigate configuration changes, or prepare evidence after syncing the estate offline.
How do I add Liongard MCP to my agent?
Install the liongard mcpb package, set LIONGARD_INSTANCE and LIONGARD_API_KEY (or access key credentials), optionally LIONGARD_ENDPOINTS_API_KEY, then register the stdio MCP server.