Agents propose.
Policy decides.
honua-devops is a private-beta commercial operator surface for one environment.
Register its MCP server with a compatible client to inspect health, diagnose incidents, plan deployments,
and draft GitOps changes. In plan mode, tools return evidence and a proposal without applying it. PR-first
routes eligible configuration changes through review instead of applying them directly. Explicit policy can
allow a narrow set of deterministic actions; fleet-wide control remains planned.
deploy_service_gitops({ target: "staging", environment: "staging" })
{
status: "plan-ready",
applied: false,
approval: "pr-first",
evidence: ["topology", "policy-gates"],
audit: "recorded"
}
nothing applied. The change goes out as a GitOps proposal for your team to review and merge. Coordinated dev → staging → prod promotion remains planned.Connect your agent to a bounded operator surface.
honua-devops --mcp exposes the private-beta tools as an MCP stdio server. Access requires the beta software and a narrowly scoped Honua credential. Configure the redacted action-record sink before using the tools.
describe_environment()
eks · lambda, environments dev / staging / prod.honua_diagnose() → honua_explain_slow_queries()
// These products have different jobs: honua-devops is the private-beta commercial operator surface; the open geospatial-mcp specification covers Community data discovery and query. In MCP mode, the client supplies the model reasoning.
Controls live below the model.
The operator configures credentials, tool permissions, action policy, and approval flow before a session. The tool handlers and engine enforce those boundaries; model instructions do not change them mid-conversation.
Inspect. Diagnose. Plan. Propose.
The table separates the private-beta operator tools from the Community discovery and query surface. Planned fleet behavior is not included.
| Surface | What agents do today | The guardrail |
|---|---|---|
| Operate | Describe the environment — edition, services, deploy targets, allowed environments — and track recent operations. | Read-only · audit-logged |
| Diagnose | Analyze logs and metrics, triage incidents, explain slow-query signatures with prioritized remediation and validation checks. | Read-only diagnostics · audit-logged |
| Deploy | Plan upgrades and deployments and recommend a topology for one environment. | Plan mode — evidence out, nothing applied |
| Propose | Draft GitOps proposals for configuration and metadata changes against one deploy target. | PR-first by default; explicitly permitted actions only |
| Discover & query | Service discovery, schema inspection, filtered queries and statistics, bounded spatial analysis on the open MCP data surface. | Read-only · cited sources · Community |
| Change configuration | Prepare a specification and dry run. The engine validates and plans before an approved or explicitly permitted deterministic action. | Validated spec + dry run · private beta |
// The honua-devops MCP server exposes 24 operator tools in private beta. MCP discovery & query are Community; commercial operator automation remains private beta until release and rollback evidence is complete. The edition split →
What must exist before fleet automation.
The private-beta operator starts in plan mode, routes eligible changes through pull requests, and records tool actions. Fleet automation will require verification after each action, recovery when an automated action or rollback fails, signed cross-repository promotion, and coordinated fleet control. Honua does not claim a self-healing production loop today. Review the current evidence →