MCP Server
Bring Breeze operations into MCP workflows.
The MCP Server enables external AI clients to access Breeze resources and operational tools through the Model Context Protocol.
Why It Is Useful
Many teams run assistant workflows outside the Breeze UI. MCP integration lets those assistants query fleet context and initiate controlled operations while still relying on Breeze for enforcement and auditability.
Governance Continuity
MCP actions are still governed by Breeze controls:
- role and permission checks
- tenant isolation
- risk-tier behavior
- approval requirements for sensitive actions
- execution and denial logging
Integration Scenarios
Typical use cases include assistant-driven triage, workflow orchestration across systems, and tool chaining where Breeze is the execution authority.
Why Teams Use It
MCP provides flexibility in client experience without giving up operational guardrails.
Capabilities
MCP Protocol Support
Breeze exposes fleet resources and operational tools through the Model Context Protocol for compatible AI client hosts.
Governance Continuity
MCP actions go through Breeze RBAC, tenant isolation, risk-tier evaluation, and approval workflows.
Tenant-Scoped Context
Fleet data and operational tool scope follow organization boundaries regardless of the AI client origin.
Execution and Denial Audit
Tool calls and denials through MCP are logged the same way as native AI assistant actions.