Cloudcostwise vs Cloud Tools
A side-by-side look at the Cloudcostwise and Cloud Tools MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Cloudcostwise for cloud platforms work as a local process; choose Cloud Tools for cloud platforms as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Cloudcostwise when
- You need dedicated capabilities in the Cloud Platforms domain.
- You prefer a local stdio subprocess transport.
Choose Cloud Tools when
- You need dedicated capabilities in the Cloud Platforms domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: other.
- You have the keys it needs:
AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, AWS_PROFILE, GOOGLE_APPLICATION_CREDENTIALS, CLOUDFLARE_API_TOKEN, CLOUDFLARE_ACCOUNT_ID, OVH_APPLICATION_KEY, OVH_CONSUMER_KEY. - You want tools like
compare_costs, get_commitments, get_costs.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Cloud Platforms | Cloud Platforms |
| Quality signal | 36/100 · Fair | 61/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | other |
| Pricing | Not declared | Free |
| Required env vars | None listed | AWS_ACCESS_KEY_IDAWS_SECRET_ACCESS_KEYAWS_PROFILE |
Tools & capabilities
Cloudcostwise tools
No tool names declared yet. Check the project README from the listing page.
Cloud Tools tools 7
compare_costsThis period against the same day window of the previous month, so a partial month does not read as a fall. AWS and GCP only. GCP needs credentials.gcp.billing_table.get_commitmentsCommitments you are paying for, and whether you are consuming them, over the last 30 days. AWS: Savings Plans utilisation, coverage of eligible spend, and the saving a further commitment would give. GCP: committed use discounts with their expiry. Not implemented for Cloudflare or OVH, which sell no commitments.get_costsCloud spend. AWS: by service over a date range, from Cost Explorer; pass group_by="data_transfer" for transfer cost by usage type. GCP: by service from the BigQuery billing export, which credentials.gcp.billing_table must name — without it you get budget amounts, not spend. Cloudflare: subscriptions and zone plan costs. OVH: the 6 most recent invoices.get_cross_cloud_summaryOne cost and waste report over every cloud you pass credentials for, with a grand total. Omit a cloud's credentials to skip it.get_inventoryWhat exists. GCP: GCE instances, disks, addresses, snapshots, forwarding rules, GKE clusters with node pools, Cloud SQL, Cloud Functions, Cloud Run, GCS buckets, Cloud NAT, Cloud IDS, Artifact Registry, VPN gateways, subnets, PSC endpoints and Cloud Logging ingestion, with a per-project summary. Cloudflare: zones with plan and price, DNS records split proxied against dns-only, certificates with hosts and expiry, and Workers with invocation counts. OVH: instances and active services with renewal dates and monthly cost. Not implemented for AWS.get_recommendationsThe cloud provider's own optimisation suggestions. GCP: the Recommender API across every zone and region — idle VMs, machine type rightsizing, idle disks and addresses, idle and oversized Cloud SQL. Not implemented for the others; AWS Compute Optimizer is read as part of get_waste instead.get_waste
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Cloudcostwise
{
"mcpServers": {
"cloudcostwise": {
"command": "uvx",
"args": [
"cloudcostwise"
]
}
}
}
Cloud Tools
{
"mcpServers": {
"cloud-tools": {
"command": "npx",
"args": [
"-y",
"@munhq/cloud-tools"
],
"env": {
"AWS_ACCESS_KEY_ID": "YOUR_AWS_ACCESS_KEY_ID_HERE",
"AWS_SECRET_ACCESS_KEY": "YOUR_AWS_SECRET_ACCESS_KEY_HERE",
"AWS_PROFILE": "YOUR_AWS_PROFILE_HERE",
"GOOGLE_APPLICATION_CREDENTIALS": "YOUR_GOOGLE_APPLICATION_CREDENTIALS_HERE",
"CLOUDFLARE_API_TOKEN": "YOUR_CLOUDFLARE_API_TOKEN_HERE",
"CLOUDFLARE_ACCOUNT_ID": "YOUR_CLOUDFLARE_ACCOUNT_ID_HERE",
"OVH_APPLICATION_KEY": "YOUR_OVH_APPLICATION_KEY_HERE",
"OVH_CONSUMER_KEY": "YOUR_OVH_CONSUMER_KEY_HERE"
}
}
}
}
Frequently asked questions
Cloudcostwise is categorized under Cloud Platforms and uses a local stdio subprocess. Cloud Tools belongs to Cloud Platforms and uses a local stdio subprocess. Pick Cloudcostwise for cloud platforms work and Cloud Tools for cloud platforms.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Cloudcostwise has no declared pricing — check the project's own site. Cloud Tools is listed as free. Auth: other. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add cloudcostwise and cloud-tools as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Cloudcostwise has a quality signal of 36/100 (Fair) with 0 views, 0 installs and 1 GitHub stars. Cloud Tools has 61/100 (Good) with 3 views, 0 installs and 0 GitHub stars.