mcpbeat Sign in

cloud-tools MCP Server

local only

cloud-tools runs on your own machine — the client starts it, so there is no endpoint to ping. 24 installs a week from npm. Last commit 29 Sep 2026.

Multi-cloud cost, inventory and waste analysis over MCP: AWS, GCP, Cloudflare and OVH.

Installs per day peak 12 · avg 5 · -33% w/w
a month agotoday
24
Installs / week
npm · @munhq/cloud-tools
0
Stars
0 open issues
29 Sep 2026
Last commit
1 release in 90 days
Apache-2.0
License
Rust

What the code does

We read the source, 2 d ago · rules ccca72095570

Capabilities

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

Runs a command on install [пакет] package.json:1
postinstall: node bin/postinstall.js
  const res = spawnSync(bin, args, { stdio: 'inherit' });
Builds a file path from a variable npm/build-mcpb.mjs:57
    copyFileSync(path.join(here, 'bin', f), path.join(stage, 'server', f));
In the project's build, not in the package

Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.

Reaches cloud metadata service src/clouds/aws/auth.rs:88
        .put("http://169.254.169.254/latest/api/token")
Reads secrets and sends them out src/clouds/aws/auth.rs:140
         (~/.aws/credentials, profile from AWS_PROFILE, otherwise [default]); \
Touches key and credential files src/clouds/aws/auth.rs:140, src/tools/cost.rs:505
         (~/.aws/credentials, profile from AWS_PROFILE, otherwise [default]); \

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

This code can reach further than it looks

We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.

Three servers free · no card

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

run in your terminal
claude mcp add cloud-tools -- npx -y @munhq/cloud-tools
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "cloud-tools": {
      "args": [
        "-y",
        "@munhq/cloud-tools"
      ],
      "command": "npx"
    }
  }
}
~/.codex/config.toml
[mcp_servers.cloud-tools]
command = "npx"
args = ["-y", "@munhq/cloud-tools"]
.cursor/mcp.json
{
  "mcpServers": {
    "cloud-tools": {
      "args": [
        "-y",
        "@munhq/cloud-tools"
      ],
      "command": "npx"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "cloud-tools": {
      "args": [
        "-y",
        "@munhq/cloud-tools"
      ],
      "command": "npx"
    }
  }
}

This one needs environment variables set before it will start: CLOUD_TOOLS_MODE (mcp for an MCP client over stdio, http for the REST API. Defaults to mcp, which is what every MCP client wants.). The author declared them in the registry entry; get the values from the project itself.

Alternatives to cloud-tools

same job, measured the same way
ZopDev MCP
by zop

Cloud cost, inventory and governance on AWS/Azure/GCP. Read-only by default, optional scoped writes

answering
Cloudpulse
by lhf552004

Cross-cloud observability for AI agents. Covers AWS, GCP, Vercel, and Cloudflare.

35 installs/wk local only
MCP Server Cloud Fs
by nogoo9

Cloud replacement for mcp-server-filesystem — 20 tools for S3, Azure Blob, and GCS

31 installs/wk local only
Cloud DevOps MCP Server
by alexcgodwin

Cloud DevOps analysis with guarded Git, infrastructure, cloud and observability operations.

158 installs/wk local only
Cloud FinOps Skill & MCP
by optimnow

Cloud cost + FinOps knowledge for AI agents: AWS/Azure/GCP optimisation, AI spend, waste playbooks.

1 608 installs/wk 6 tools answering
clawops
by dfridkin

Deploy self-hosted OpenClaw to AWS, GCP, Azure or a local VM — a CLI and an MCP server in one.

448 installs/wk local only
Umami Compass
by webcredo

Secure Umami Analytics MCP server for Cloud and self-hosted deployments

38 installs/wk local only
Synlake — Cloud Infrastructure for AI Agents
by synlake-ai

Compare, estimate, and deploy cloud infrastructure across AWS, GCP, and Azure for AI agents.

answering

cloud-tools — questions

Answers built from our own checks of this server.

Why is there no uptime for cloud-tools?
cloud-tools runs on your own machine over stdio — there is no network address to reach, so uptime cannot be measured for it by anyone. What can be measured is adoption: the npm package @munhq/cloud-tools was installed 24 times last week.
How do I connect cloud-tools?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It runs locally, so the command pulls @munhq/cloud-tools straight from npm; nothing to host, nothing to sign up for.
How many people use cloud-tools?
The npm package @munhq/cloud-tools was installed 24 times in the last week. Week over week that is -33%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.
Is cloud-tools open source?
Yes — it is published under the Apache-2.0 licence, written in Rust and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.