Cloud Cost MCP vs Infrawise — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Cloud Cost MCP vs Infrawise
In-depth architectural comparison of the Cloud Cost MCP and Infrawise MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Cloud Cost MCP
Cloud Platforms · Local stdio
Quality: 57/100 (Good) | Auth: No auth required
Infrawise
Cloud Platforms · Local stdio
Quality: 64/100 (Good) | Auth: API Key required
Verdict Summary: Choose Cloud Cost MCP if you need specialized Cloud Platforms tools running via a local process. Choose Infrawise if your workspace requires Cloud Platforms integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Cloud Cost MCP when:
You need dedicated capabilities in the Cloud Platforms domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Multi-cloud pricing comparison across AWS, Azure, GCP, and OCI with 2,700+ instance types. Real-time pricing from public APIs, workload calculators, and migration savings estimator.
Cloud infrastructure analysis for AI coding assistants — detects IaC drift, missing indexes, security gaps, and performance anti-patterns across AWS services and databases. 13 tools, works with Claude Code and Cursor.
Category & Scope
Tools & Capabilities Breakdown
Cloud Cost MCP Tools (31)
compare_compute
Compare VM/instance pricing across AWS, Azure, GCP, and OCI. Finds instances matching your vCPU and memory requirements.
compare_storage
Compare object and block storage pricing across all clouds.
compare_egress
Compare data transfer/egress costs. OCI offers 10TB/month free (100x more than others)!
compare_kubernetes
Compare managed Kubernetes pricing (EKS, AKS, GKE, OKE). Shows control plane and worker node costs.
find_cheapest_compute
Find the cheapest cloud provider for specific compute specs.
calculate_workload_cost
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Cloud Cost MCP is categorized under Cloud Platforms and uses a local stdio subprocess. In contrast, Infrawise belongs to Cloud Platforms using local stdio subprocess. Select Cloud Cost MCP when you need capabilities focused on cloud platforms and Infrawise when you require tools for cloud platforms.
Estimate total monthly cost for a workload across all cloud providers. Includes compute, storage, egress, and Kubernetes.
quick_estimate
Get instant cost comparison for common deployment presets including GPU workloads.
list_presets
List all available deployment presets for quick_estimate.
estimate_migration_savings
Calculate potential savings when migrating from one cloud provider to another.
get_data_freshness
Check how recent the pricing data is for each provider. Warns if data is stale (>30 days).
get_provider_details
Get detailed pricing data for a specific cloud provider.
get_storage_summary
Get storage pricing summary by tier (hot, cool, cold, archive) for all providers.
+19 more tools listed on main page
Infrawise Tools (22)
get_infra_overview
Complete snapshot — services, counts, high-severity findings, `configured` flag (data age and per-source status ride the `dataHealth` block on every response)
get_graph_summary
Full infrastructure graph — all nodes, edges, and findings
get_table_schema
Column-level schema for named tables/collections — types, PKs, FKs, indexes, DynamoDB keys/billing mode, cost signal (no row data)
analyze_function
Issues in a specific function — scans, missing indexes, N+1, trigger event shapes, missing IAM permissions; returns every same-named file as a separate match, or bind to one with the optional `file` input; names refused Lambda links and why (`unresolvedLambdas`)
suggest_gsi
Exact GSI config for a DynamoDB table + attribute — names the existing index instead when one already covers it
postgres_index_suggestions
Exact `CREATE INDEX` SQL for your actual table
suggest_mongo_index
Exact `createIndex` command for a MongoDB collection + field
mysql_index_suggestions
Exact `ALTER TABLE ADD INDEX` SQL for your MySQL table