Qualys integration
Qualys asset management through the QPS (Qualys API Platform Service) JSON endpoints: search, count and update host assets, manage asset tags and read the tag tree. Scoped deliberately to the JSON surface: the classic Qualys FO endpoints (vulnerability detections, scan launch and fetch, the KnowledgeBase, report download) answer XML, which this platform cannot decode, so they are not exposed here. The Qualys platform pod is part of the credential.
Say what should happen.
The workflow builds itself.
Common Qualys use cases
- cleaning up tags left over from a finished project
- finding an asset by hostname across the whole subscription
- resolving a tag name to the identifier an asset search needs
- checking how large a result set will be before paging through it
- creating a tag that automatically collects hosts matching a rule
- enriching a finding with the full asset record of the affected machine
- tracking asset counts by tag over time
- listing every asset carrying a given tag
- reading the installed software inventory of one host
- removing a quarantine tag once remediation is complete
What you can do with Qualys
Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.
Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.
Host asset, 3 operations
count_host_assetsCount host assetsPOSTReturns how many Asset Management host assets match the given criteria without returning them.get_host_assetGet host assetGETReturns the full Asset Management record of a single host asset.search_host_assetsSearch host assetsPOSTSearches Qualys Asset Management host assets with structured criteria and returns matching records.
Tag, 3 operations
create_tagCreate tagPOSTCreates a Qualys asset tag, optionally nested under a parent and driven by a rule.delete_tagDelete tagPOSTDeletes a Qualys asset tag and removes it from every asset that carried it.search_tagsSearch tagsPOSTSearches Qualys asset tags by name, parent or rule type.
Use Qualys from Claude Code, Cursor or Codex
Connect Qualys in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Qualys operations become tools the client can call, next to every other integration you connected.
claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"
[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"{
"mcpServers": {
"livecontext": {
"type": "http",
"url": "https://livecontext.ai/mcp",
"headers": {
"X-API-Key": "YOUR_API_KEY"
}
}
}
}How to connect Qualys
- Create your workspace
Sign up free. Nothing to install.
- Connect Qualys once
Add your Qualys connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
- Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.
Qualys integration FAQ
What can you do with the Qualys integration?
LiveContext exposes 6 operations on Qualys, covering host asset and tag. Common uses include cleaning up tags left over from a finished project, finding an asset by hostname across the whole subscription and resolving a tag name to the identifier an asset search needs.
