# cloud-tools MCP server

> Analyze multi-cloud costs, inventory, and waste across AWS, GCP, Cloudflare, and OVH using an AI agent.

- Repository: https://github.com/munhq/cloud-tools
- Page: https://hostedmcp.org/servers/munhq/cloud-tools
- Transport: stdio
- Stars: 0
- License: Apache-2.0
- Latest version: 0.2.0

## Install

### Claude Code

```sh
claude mcp add cloud-tools -- npx -y @munhq/cloud-tools
```

### Cursor (`~/.cursor/mcp.json`)

```json
{
  "mcpServers": {
    "cloud-tools": {
      "command": "npx",
      "args": [
        "-y",
        "@munhq/cloud-tools"
      ]
    }
  }
}
```

### VS Code (`.vscode/mcp.json`)

```json
{
  "servers": {
    "cloud-tools": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@munhq/cloud-tools"
      ]
    }
  }
}
```

### VS Code CLI

```sh
code --add-mcp '{"name":"cloud-tools","type":"stdio","command":"npx","args":["-y","@munhq/cloud-tools"]}'
```

### Claude Desktop (`claude_desktop_config.json`)

```json
{
  "mcpServers": {
    "cloud-tools": {
      "command": "npx",
      "args": [
        "-y",
        "@munhq/cloud-tools"
      ]
    }
  }
}
```

### Codex

```sh
codex mcp add cloud-tools -- npx -y @munhq/cloud-tools
```

### Codex config.toml (`~/.codex/config.toml`)

```toml
[mcp_servers.cloud-tools]
command = "npx"
args = ["-y", "@munhq/cloud-tools"]
```

### Gemini CLI

```sh
gemini mcp add -s user cloud-tools npx -- -y @munhq/cloud-tools
```

### Gemini settings.json (`~/.gemini/settings.json`)

```json
{
  "mcpServers": {
    "cloud-tools": {
      "command": "npx",
      "args": [
        "-y",
        "@munhq/cloud-tools"
      ]
    }
  }
}
```

## Environment variables

| Name | Required | Secret | Description |
|---|---|---|---|
| `CLOUD_TOOLS_MODE` | no | no | mcp for an MCP client over stdio, http for the REST API. Defaults to mcp, which is what every MCP client wants. |

## Tools (9)

- `check_access`
- `get_costs`
- `compare_costs`
- `get_inventory`
- `get_waste`
- `get_commitments`
- `get_recommendations`
- `get_cross_cloud_summary`
- `complete`

## FAQ

### Does the server handle my cloud credentials?

No, credentials never appear in a tool call. The server reads them from its own environment, so the agent never handles a secret.

### Is the server's access to my cloud accounts destructive?

No, the server is read-only and does not create, modify, or delete any cloud resources.

### How can I tell if a zero result means no waste or a failed scan?

Check the coverage field; 'complete' means nothing is wasted, while 'PARTIAL' indicates some API calls failed and the account could not be fully read.

### Does this server collect any telemetry or user data?

No, the server collects nothing, including no telemetry, analytics, or identifiers.