HomeLiongardRequest a DemoKnowledge Base
Guides
Start typing to search…

Liongard MCP - FAQs

Liongard MCP Server & AI Features FAQ

For MSP Customer Partners

1. What is Liongard’s Model Context Protocol (MCP) Server?

Answer: MCP is Liongard’s secure, modern interface for accessing up-to-date asset and system data. It enables AI-powered natural-language search as well as integration with external tools to support faster reporting, compliance workflows, and automation.

2. How do MCP tools work in Liongard?

Answer: Users can search asset, system, or environment information using natural language (for example: “Which SonicWall devices have expiring feature licenses?”). The MCP client retrieves data from Liongard’s MCP server and returns AI-generated summaries and actionable insights in real time.

3. What is required to use the MCP Server?

Answer: You must be a Liongard MCP subscriber. Each subscription includes one global MCP access token that provides access to all data and environments within your Liongard tenant.

Additional Private Access MCP Tokens (see below) may be purchased as needed. Only authorized Liongard users can access MCP features.

4. What are Private Access MCP Tokens, and when would I need one?

Answer: Private Access MCP Tokens are scoped to a single environment or environment group. They are ideal for co-managed, restricted, or delegated integration scenarios.

These tokens incur an additional cost and provide more limited, controlled access than the global token.

5. How should MCP tokens be secured?

Answer: The global MCP token grants access to all tenant data and managed environments. It should be:

  • Restricted to trusted integration clients only
  • Carefully distributed and stored securely
  • Immediately revoked if misuse is suspected
  • Regularly audited for usage activity

Strong access controls are essential.

6. How is data protected when using MCP and AI Search?

Answer:

  • All data in transit is encrypted using TLS 1.2+
  • Access requires a valid MCP token
  • Once data is retrieved via MCP, it leaves Liongard’s control and must be secured according to your organization’s data protection policies

7. Who manages and audits MCP access?

Answer: Only tenant administrators can issue, scope, rotate, or revoke MCP tokens (both global and Private Access tokens). Regular audits of token usage and integrations are strongly recommended.

8. How is usage tracked and metered?

Answer: Each completed MCP query or AI search session consumes one credit.

  • All tokens (global and private) draw from the same credit pool
  • Unused credits do not roll over

9. What workflows does MCP enable?

Answer: MCP supports automation and acceleration of:

  • Asset and license validation
  • Compliance reporting
  • QBR reporting
  • Service desk workflows
  • Integration with tools such as n8n and VS Code

10. Can MCP or AI features be disabled?

Answer: Yes. Tenant administrators may revoke MCP tokens or adjust access under:

Liongard Admin → AI Preferences

Revoking a token immediately blocks access for that integration or client.


Liongard MCP Integration FAQ

For Alliance Partners & Integrators

Q1. What does MCP access enable for Alliance Partners?

Answer: MCP allows Alliance Partners to connect external platforms (such as ticketing, reporting, or documentation systems) directly to Liongard. This enables enrichment of partner solutions with real-time asset and configuration intelligence for mutual MSP customers.

Q2. How do Alliance Partners access Liongard data?

Answer: An MSP partner must provide an MCP access token. This token authorizes your integration to query the MSP’s tenant environments via the MCP server.

Traditional API integrations or bulk ETL processes are not required. Access may be scoped to specific environments or all environments.

Note: MCP currently does not support OAuth2.

Q3. What responsibilities come with direct MCP access?

Answer: Alliance Partners are responsible for:

  • Protecting issued access tokens
  • Restricting use to authorized applications and users
  • Handling all data in accordance with mutual MSP agreements
  • Ensuring proper storage and access controls for retrieved data

Q4. Is data processing secure and compliant?

Answer:

  • All data is encrypted in transit
  • Access is controlled via token authorization
  • Once retrieved, data must be protected under your organization’s security standards

MCP does not currently support OAuth2 (v1).

Q5. Will results vary depending on the AI model or client used?

Answer: Yes. Response formatting and reasoning quality may vary depending on the MCP client and LLM used.

Liongard has tested integrations with tools such as Claude Code, n8n, and Cursor using Anthropic Opus 4.5+ and Sonnet 4.5; however, results may differ across environments.

Q6. What is the scope of data available via MCP?

Answer: Once a valid token is issued by an MSP tenant administrator, access may be global at the service provider level or scoped to specific environments.

Alliance Partners should ensure access is enabled only for mutually agreed environments.

Q7. How are credits and usage tracked for Alliance Partners?

Answer: All MCP queries made by an Alliance integration count against the Alliance Partner’s credit entitlement.

Usage can be monitored in the Liongard portal or through the partner dashboard.

Q8. How do I get support for onboarding or troubleshooting?

Answer: Alliance Partners have access to:

  • Integration documentation
  • Onboarding support
  • Dedicated Liongard Alliance Partner support for advanced technical or security questions

Q9. Can an Alliance integration be disabled?

Answer: Yes. If an MSP revokes the MCP token or disables the integration, access to that tenant’s Liongard data is immediately blocked.

Q10. What are best practices for MCP integration security?

Answer:

  • Safeguard all client-issued tokens
  • Rotate or revoke tokens upon termination or suspected compromise
  • Notify mutual MSP partners of any potential security events involving data access

Updated about 4 hours ago