AI integration
Infrastructure that knows what it is
Basalt exposes infrastructure state and reasoning to AI systems through MCP, structured capability explanations, manifest projection, and guest-agent telemetry. Assistants can inspect the platform using the same security model as human operators.
AI integration builds on manifest projection, respects the RLS-aware auth model, and enriches compute operations with infrastructure context that assistants can safely read.
MCP Server
Basalt includes a native Model Context Protocol server for infrastructure state. It exposes nine read tools: vm.list, vm.get, task.list, task.get, cluster.list, host.list, network_zone.list, storage_pool.list, and image.list.
The MCP layer uses the same RLS-aware authentication context as REST, so an assistant sees only the infrastructure the caller is allowed to see. It works with Claude, ChatGPT, and in-house assistants through OAuth/HTTP integration. The surface is read-only today; write tools are roadmapped.
Capability Reasoning
Every decision about whether a feature is available carries a structured CapabilityReason. Basalt can explain that snapshots are unavailable because the selected pool is RBD, or that a feature depends on a host capability that is missing.
That makes capability checks machine-readable. The UI can do more than grey out a button, and an AI assistant can answer why a workflow is blocked. The platform does not just do things — it knows why things are or are not possible.
Manifest Projection
The gateway continuously computes per-host desired state. Eligibility predicates decide which resources belong on each host, agents poll for their manifests, and then converge local state toward the projected intent.
This is the self-awareness layer in operational form: Basalt knows what it wants to be at every moment, can describe that desired state, and can detect when actual host state drifts away from it.
Guest-Agent Telemetry
QEMU guest-agent telemetry surfaces hostname, OS information, network interfaces, and filesystem usage without SSH and without installing a Basalt-specific agent inside the guest. Operators and assistants can see inside workloads without requiring broad trust in the workload itself.