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.
We read the source, 2 d ago · rules ccca72095570
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.
postinstall: node bin/postinstall.js
const res = spawnSync(bin, args, { stdio: 'inherit' });
copyFileSync(path.join(here, 'bin', f), path.join(stage, 'server', f));
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.
.put("http://169.254.169.254/latest/api/token")
(~/.aws/credentials, profile from AWS_PROFILE, otherwise [default]); \
(~/.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.
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.
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.
claude mcp add cloud-tools -- npx -y @munhq/cloud-tools
{
"mcpServers": {
"cloud-tools": {
"args": [
"-y",
"@munhq/cloud-tools"
],
"command": "npx"
}
}
}
[mcp_servers.cloud-tools]
command = "npx"
args = ["-y", "@munhq/cloud-tools"]
{
"mcpServers": {
"cloud-tools": {
"args": [
"-y",
"@munhq/cloud-tools"
],
"command": "npx"
}
}
}
{
"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.
Cloud cost, inventory and governance on AWS/Azure/GCP. Read-only by default, optional scoped writes
Cross-cloud observability for AI agents. Covers AWS, GCP, Vercel, and Cloudflare.
Cloud replacement for mcp-server-filesystem — 20 tools for S3, Azure Blob, and GCS
Cloud DevOps analysis with guarded Git, infrastructure, cloud and observability operations.
Cloud cost + FinOps knowledge for AI agents: AWS/Azure/GCP optimisation, AI spend, waste playbooks.
Deploy self-hosted OpenClaw to AWS, GCP, Azure or a local VM — a CLI and an MCP server in one.
Secure Umami Analytics MCP server for Cloud and self-hosted deployments
Compare, estimate, and deploy cloud infrastructure across AWS, GCP, and Azure for AI agents.
Answers built from our own checks of this server.