ganakailabs/cloudeval-cli

**Your cloud, in the terminal: evaluated, reported, and agent-ready.**
Cloudeval CLI turns **ARM templates**, **GitHub-hosted IaC**, and **live Azure context** into cost, architecture, and Well-Architected signals. Use it as a terminal UI, a scriptable automation client, or an MCP server for Codex, Cursor, Claude, VS Code, and any stdio JSON-RPC client.
Why Use It
| For | What you get |
| ------------------ | --------------------------------------------------------------------------------------------------------------------------------- |
| **Terminal users** | A full TUI with chat, Agent mode, workspace tabs, thread switching, slash commands, a context rail, task ledger, artifact chips, and local SQLite session history. |
| **Automation** | Stable json, ndjson, markdown, and text output; payloads on stdout; progress and prompts on stderr; predictable exit codes. |
| **Agents and CI** | Scoped access-key credentials, redacted output by default, MCP toolsets, recipes, and machine-readable capability metadata. |
Install
Node.js 20+ users can install from npm:
macOS, Linux, WSL2, Git Bash, and PowerShell 7+ on Windows or Linux can use
the standalone release installer:
Then reload your shell and sign in:
Device login goes through **cloudeval.ai** and always asks the browser auth
provider to show the account chooser, so users can choose the intended work
email even when another account is already signed in. No local Azure app
registration is needed for normal CLI use.
Installer behavior and controls
The installer:
- downloads checksum-verified GitHub release assets and installs cloudeval;
- creates the eva and cloud aliases on non-Windows platforms;
- can install shell completions for bash, zsh, and fish;
- can offer concise MCP setup for detected Codex, Claude Desktop, Cursor, and VS Code clients, skipping clients where Cloudeval MCP is already configured and avoiding prompts when only manual-only setup remains;
- asks whether to share limited CLI telemetry, defaulting to yes; declining writes telemetry.enabled=false;
- explains credential setup but does not create access keys or write secrets into MCP client config;
- shows compact labeled progress bars in interactive terminals;
- uses connect/stall timeouts so slow CDN transfers fail clearly.
Useful controls:
The bash installer can also detect agent clients and offer MCP setup. The
PowerShell installer installs the verified binary, yoga.wasm, license
notices, PATH, and optional PowerShell tab completions. Run cloudeval mcp
setup afterward when you want MCP client configuration.
Telemetry
Cloudeval CLI sends curated custom events to Azure Application Insights by
default. Events cover command family, success, duration, safe option enums, CLI
version, Node/runtime version, OS major version, architecture, install source,
update/install outcomes, MCP tool names, and TUI launch/exit metadata. After
login, events may include the signed-in email and first/last/full name.
Telemetry never sends raw prompts, command output, tokens, local paths, project
or resource identifiers, account/session/tenant identifiers, cloud resource
names, stack traces, or raw error messages. Disable or re-enable it anytime:
Environment overrides take precedence for a single run:
Update later with:
After an update, restart or reload configured MCP clients when you are ready to
load newly exposed Cloudeval tools, resources, or prompts. Cloudeval does not
restart Codex, Claude, Cursor, VS Code, or other MCP hosts automatically.
Uninstall local installer-owned artifacts while keeping Cloudeval config,
sessions, and auth by default:
Start Here
Full docs: Get started with the CLI and CLI command reference.
Inside the Terminal UI, use the Thread control or /thread to switch open chat
sessions, recent Cloudeval chat threads, and local CLI sessions. /thread new
starts another independent open session, and /open jumps to the same chat
thread in Cloudeval when the active session has a thread id. Roomy terminals show
a context rail with project, thread, model, mode, profile, report artifact
chips; narrower terminals keep the