Looking for Liongard’s Lexful inspector? That integration reads Lexful into Liongard. See Inspect Lexful documentation with Liongard. The guide below covers the opposite direction: Ask Lex querying Liongard.
Why this exists
Lexful and Liongard are Better Together: your documentation platform and your MSP's operational source of truth, working as one. This doc shows the one thing that makes that real for an admin on a live support ticket — asking Lex a plain-language question and getting back real Liongard data, without switching tools.
The workflow: ask a question, get a live answer
The scenario: You're mid-ticket. A client says something's off, and you quickly discover "something changed on the network" and you don't know what. Instead of opening Liongard, finding the right environment, and digging through inspection history yourself, you simply ask Lex.
Prompt: use the liongard connector to tell me the history of changes on this network
Lex reaches into Liongard live — no documentation sync or export — and comes back with the answer.
That's the whole idea: the historical operational knowledge already exists in Liongard. Ask Lex means you never have to leave the conversation to get to it.
Setup: connect Lexful to Liongard
Browse to Platform >Integrations > Connectors
Add a connector.
Type:
MCPName:
Liongard(or whatever your team prefers)Server URL:
https://<your-instance>.app.liongard.com/api/mcp— this can't be changed after creation; delete and re-add if you need to point it elsewhere.
Authenticate.
Authentication:
Bearer tokenAuthorization token: generate this from your Liongard account and paste it in. This is a global, account-level connection — there's no per-user login required once it's set up.
Go to your Admin > AI Preferences section of Liongard to create your token
[Optional]. Restrict usage to certain users
Enable your tools. Refresh the available tools, then enable the ones your team needs. The provider’s catalog can change. Examples include:
Tool | What it queries |
| Agents — the lightweight service Liongard installs on a monitored machine (Windows, Linux, or Mac) |
| Devices in the Reconciled Asset Inventory |
| Environments — a client's network as Liongard sees it |
| Identities tracked across a client's environment |
| Domains and certificates in the Reconciled Asset Inventory |
Available results depend on the tools you enable and the account represented by the configured token.
More example queries
The workflow above uses liongard_environment under the hood. Here are a few more things you can ask Lex once the connector's live:
"What devices are registered for [client]'s environment?" →
liongard_device"Is [client]'s domain certificate still valid, what's the expiration date?" →
liongard_domain"What identities have been added or removed for [client] in the past 60 days?" →
liongard_identity"Is the Liongard agent still checking in on [client]'s server?" →
liongard_agents
Enabling more tools
Refresh the connector to see the tools currently offered by your Liongard instance. Review each tool’s purpose before enabling it.
To turn one on:
Select Platform >Integrations >Connectors >Liongard >Edit Connector
Click Refresh tools to pull the current tool list from your Liongard instance.
Check the box next to any additional tool you want Lex to be able to use.
Save Changes.
Enable only the tools your team needs, and review what each tool can read or change.
Engaging the tool from 'Ask Lex'
The Liongard Connector is not enabled by default, use the + Tool selector to enable it in the current chat session. A purple live indicator will give visual feedback that an external MCP connector has been enabled in the chat:
Troubleshooting
"Lex says the connector failed" / query returns nothing. Check that the Bearer token is present and hasn't expired — the Authorization token field will show masked dots if one is set, but an expired or revoked token will cause every query to fail the same way. Re-generate the token in Liongard and re-enter it in the connector's Edit screen.
"Lex can't find the client/environment I asked about." Check the environment name, the token’s access and the tools enabled for the connector. A missing result alone does not establish which of these caused it.
Use the environment name exactly as it appears in Liongard, or ask Lex to "list all environments available"
"The query ran but came back empty." Check the environment and time range, then confirm the expected data is visible to the configured Liongard account. If it is still missing, capture the non-sensitive error or result and contact support.
Next: the companion Lexful API Inspector pulls Lexful data into Liongard for compliance and audit-trail reporting.