GitHub
GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.
Description from the maker (original English)
Cloud evaluations and reviews for Azure and static AWS CloudFormation (beta). Requires an account.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
CLOUDEVAL_ACCESS_KEYValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"cloudeval": {
"command": "npx",
"args": [
"-y",
"@ganakailabs/cloudeval-cli",
"mcp",
"serve",
"--toolset",
"readonly"
],
"env": {
"CLOUDEVAL_ACCESS_KEY": "your-value"
}
}
}
}Run this in your terminal
claude mcp add cloudeval --env CLOUDEVAL_ACCESS_KEY=your-value -- npx -y @ganakailabs/cloudeval-cli mcp serve --toolset readonlyFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"cloudeval": {
"command": "npx",
"args": [
"-y",
"@ganakailabs/cloudeval-cli",
"mcp",
"serve",
"--toolset",
"readonly"
],
"env": {
"CLOUDEVAL_ACCESS_KEY": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"cloudeval": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@ganakailabs/cloudeval-cli",
"mcp",
"serve",
"--toolset",
"readonly"
],
"env": {
"CLOUDEVAL_ACCESS_KEY": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The registry name was verified with the GitHub account ganakailabs, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: CLOUDEVAL_ACCESS_KEY
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.38.5) reached the registry 2 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: GitHub, Desktop Commander, Cloudflare MCP
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.
MCP server for terminal commands, file operations, and process management
Cloudflare MCP servers
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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.
| 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. |
Node.js 20+ users can install from npm:
npm install -g @ganakailabs/cloudeval-cli
cloudeval --help
macOS, Linux, WSL2, Git Bash, and PowerShell 7+ on Windows or Linux can use the standalone release installer:
curl -fsSL https://cli.cloudeval.ai/install.sh | bash
irm https://cli.cloudeval.ai/install.ps1 | iex
Then reload your shell and sign in:
source ~/.bashrc # or: source ~/.zshrc
cloudeval login cloudeval status cloudeval chat
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:
cloudeval;eva and cloud aliases on non-Windows platforms;telemetry.enabled=false;Useful controls:
curl -fsSL https://cli.cloudeval.ai/install.sh | CLOUDEVAL_INSTALL_AGENT_SETUP=0 bash
curl -fsSL https://cli.cloudeval.ai/install.sh | CLOUDEVAL_INSTALL_MCP_CLIENTS=codex,cursor bash curl -fsSL https://cli.cloudeval.ai/install.sh | CLOUDEVAL_TELEMETRY=0 bash
$env:CLOUDEVAL_ASSUME_YES = "1"
irm https://cli.cloudeval.ai/install.ps1 | iex
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.
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:
cloudeval config set telemetry.enabled false
cloudeval config get telemetry.enabled --format json cloudeval config set telemetry.enabled true cloudeval config unset telemetry.enabled
Environment overrides take precedence for a single run:
CLOUDEVAL_TELEMETRY=0 cloudeval status --format json
CLOUDEVAL_TELEMETRY=1 cloudeval --help
Update later with:
cloudeval update --check
cloudeval update --yes
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:
cloudeval uninstall --dry-run
cloudeval uninstall --yes cloudeval uninstall --yes --remove-config # also removes ~/.config/cloudeval npm uninstall -g @ganakailabs/cloudeval-cli # if installed through npm
cloudeval # Terminal UI
cloudeval tui --graph-diagram ascii cloudeval ask "Summarize my cloud risk" --format json cloudeval agent "Find cost and architecture risks" --format json cloudeval agents list cloudeval agents run cost --project --format json cloudeval recipes list cloudeval projects list cloudeval uninstall --dry-run cloudeval projects graph insights --focus impact --resource --format json cloudeval validate template --template-file template.json --parameters-file parameters.json --rule --details --wait --progress stderr --wait-timeout 600000 --format json cloudeval validate tests --template-file template.json --parameters-file parameters.json --wait --progress stderr --wait-timeout 600000 --format json cloudeval rules search "public network" --format json cloudeval reports list cloudeval actions list --type architecture,cost,unit-tests --format json cloudeval actions open --print-url --no-open cloudeval review --repo owner/repo --ref feature/infra-change --commit-sha --github-checks --sarif --output cloudeval-review --format json --non-interactive cloudeval capabilities --format json cloudeval doctor --deep
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 chat first and expose the same controls through the composer and slash commands. Typing / opens a bottom command completion strip; use Tab or Up/Down to move, Right to accept the ghost text, and Enter to choose the highlighted command. Streaming work appears as a task ledger in the thread, and the bottom composer stays docked so prompt entry does not compete with the transcript. Grounded answers show numbered citations and a Sources section instead of raw [S_tool_...] tags, with citation numbers highlighted inline; /copy copies the latest assistant response and /download writes a Markdown transcript with the same references. Graph insight blocks render as bordered terminal cards instead of exposing raw graph-insight markers; when a card contains a conservative Mermaid flowchart, --graph-diagram auto renders a terminal diagram in roomy TTYs, unicode or ascii force a mode, and off keeps the Mermaid source fallback. Unsupported Mermaid syntax stays visible as source instead of breaking the transcript. Negotiated chat visualizations render directly in the TUI: line/area trends use Unicode plots; bar, column, histogram, pie, doughnut, radar, and polar data use width-aware bars; scatter and heatmap data use compact terminal grids; unsupported chart families use the artifact's table fallback. Mermaid flow edges render as an edge list, with bounded Mermaid source as the fallback when no edges can be extracted. HITL approval prompts require an explicit option selection or typed answer; pressing Enter on a blank approval prompt does not choose the recommended option. Project and Connection tabs show a selected-item detail pane for backend fields, report coverage, sync state, and linked records; use J/K or Up/Down on Projects and Connections to move the selected row, then Enter to confirm it. The billing header separates credits left from observed credits used so usage does not look like the current budget. Use the Profile control or /profile cost to run the current prompt with an Agent Profile; selecting a profile switches the TUI to Agent mode, and selecting Ask mode clears the profile back to the default chat flow. Starter prompts stay hidden until you run /starter. Press Esc from the prompt to leave text editing so tab, arrow, and number shortcuts move through controls and tabs; type again to resume editing. Busy loaders and the input cursor can be disabled with --no-anim. The banner details include the logged-in user. Focused controls and the active top tab use the shared warm banner-yellow accent, with the active tab filled across its full button interior.
The CLI advertises cloudeval.visualization/v1, flint-v1, and mermaid-v11 capabilities on chat requests. The backend compiles chart intent; the CLI validates the bounded artifact and renders terminal-safe output without a browser or native SVG helper. ask and agent JSON results include data.visualizations when present, and NDJSON emits a visualization event as well as including the artifacts in the final `
Only the beginning is shown; read the rest in the repo