Quave ONE Logo
Operate with MCP

You built your app by talking to AI. Operate it with the same conversation loop.

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.

Start freeCreate a free account, then create a scoped MCP key in minutes.
Ask the MCP anything...

Documented setup for Cursor, Claude Desktop, Claude Code, Codex, OpenCode, and other MCP clients.

The agent never gets the last word.

Talking to your infra is only safe if you stay in control. You do.

Permissions live on the server

The agent can only do what your key allows. Not the model’s decision, yours.

Scoped keys, read-only if you want

Start with read-only scopes. Add deploy, config, or dangerous scopes only for workflows you intend to automate.

Every change is audit logged

Mutating MCP operations land in the same Quave ONE audit log as UI and REST API changes, with the MCP channel preserved.

Operate Quave ONE from your AI client

Start with a free account, create a scoped MCP key, and use real supported tools for logs, metrics, deployments, rollback, alerts, and docs.