Skip to main content
Use this page when you want a coding agent to drive Akua onboarding, operations, or troubleshooting. The CLI is the primary interface. The agent installs the CLI, completes browser/device authentication with you, asks what you want to build, and uses generated commands for platform operations.

​
Start the agent

Give your coding agent this instruction:
The prompt directs the agent to:
  • Install or update akua, then complete browser sign-in with you.
  • Confirm a workspace and include its Akua-Context in scoped API commands.
  • Ask what you want to build and what infrastructure you already have, then read https://docs.akua.dev/llms.txt and only the relevant linked pages.
  • Ask once whether to mirror created infrastructure declaratively in your git repository (optional, and not GitOps).
  • Explain pricing, the free allowance, and side effects before requesting approval for a change.

​
Continue through the CLI

The setup remains usable without MCP. The agent discovers commands through akua commands and validates request objects against the public OpenAPI contract. It must not invent provider-specific helpers, guess request fields, or claim a resource is ready before verifying the returned operation and resource state. Ask the agent to continue with your outcome:

​
Optional MCP context

Add MCP only when your agent benefits from another documentation or platform tool surface. MCP authentication is separate from CLI device authentication, and most hosts need a restart or new conversation after configuration changes. Don’t wait for that restart to continue the CLI quickstart. The agent-readable prompt includes reviewed commands for Codex and Claude Code, plus configuration guidance for other tools with MCP support.

Quickstart

Start from one prompt and authenticate through the CLI.

CLI reference

Discover generated commands and pass workspace context.

Documentation MCP

Add optional searchable documentation context.

Platform MCP

Add optional OAuth-based workspace access.