Quave ONE speaks MCP, the open standard that lets Claude, Cursor, Codex, OpenCode, and other MCP clients call your Quave ONE tools. Ask it to read logs, check health, trigger deployments from a configured source, scale containers, or roll back to a previous deployment. Less dashboard hopping.
Documented setup for Cursor, Claude Desktop, Claude Code, Codex, OpenCode, and other MCP clients.
Talking to your infra is only safe if you stay in control. You do.
The agent can only do what your key allows. Not the model’s decision, yours.
Start with read-only scopes. Add deploy, config, or dangerous scopes only for workflows you intend to automate.
Mutating MCP operations land in the same Quave ONE audit log as UI and REST API changes, with the MCP channel preserved.