Cloudprice MCP vs Infrawise — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Cloudprice MCP vs Infrawise
In-depth architectural comparison of the Cloudprice 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
Cloudprice MCP
Cloud Platforms · Local stdio
Quality: 55/100 (Good) | Auth: No auth required
Infrawise
Cloud Platforms · Local stdio
Quality: 64/100 (Good) | Auth: API Key required
Verdict Summary: Choose Cloudprice 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 Cloudprice 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).
Compare on-demand compute, block/object storage, managed Postgres, egress & GPU pricing across AWS, Azure, GCP, and OCI, plus FinOps decision tools (RI/Savings Plan break-even, multi-cloud workload TCO, exit-cost migration analysis, and egress arbitrage). 25 tools.
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
Cloudprice MCP Tools (13)
get_aws_price
Look up an EC2 instance type → vCPUs, memory, hourly + monthly USD (us-east-1)
get_azure_price
Look up an Azure VM size → vCPUs, memory, hourly + monthly USD (eastus)
get_gcp_price
Look up a GCP Compute Engine machine type → vCPUs, memory, hourly + monthly USD (us-east1)
compare_clouds
Given a target spec (vCPUs + GB), return the cheapest matching SKU across **AWS / Azure / GCP / OCI**, sorted by monthly cost, with savings summary
compare_compute_inventory
Bulk-compare a list of compute workloads (each with vCPUs / memory / quantity / hours / optional OS disk) across all 4 clouds. Returns per-row matches, per-cloud totals, cheapest cloud.
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).
Cloudprice MCP is categorized under Cloud Platforms and uses a local stdio subprocess. In contrast, Infrawise belongs to Cloud Platforms using local stdio subprocess. Select Cloudprice MCP when you need capabilities focused on cloud platforms and Infrawise when you require tools for cloud platforms.
Bulk-compare managed PostgreSQL pricing across **AWS RDS / Azure Database for PostgreSQL / GCP Cloud SQL / OCI Database with PostgreSQL**. Each row specifies vCPUs / memory / storage_gb. Storage cost is calculated separately from compute.
assess_migration
"Should I move?" — projects per-target cloud cost, savings %, **one-time exit egress cost**, payback months. Returns a ranked recommendation by 3-year TCO with triggered caveats (e.g., "OCI A1.Flex is ARM — verify your AMIs").
optimize_commitment
"When does my RI / SP / CUD pay back?" — six commitment scenarios (`none` / `1yr_no_upfront` / `1yr_all_upfront` / `3yr_no_upfront` / `3yr_partial_upfront` / `3yr_all_upfront`) with per-scenario monthly cost, upfront, 3-year total, savings %, payback months. Recommends the lowest 3-year TCO option.
compare_total_cost_of_ownership
"What's my 3-year cost across clouds?" — multi-year projection with linear YoY growth assumptions for compute / storage / egress. Returns cumulative TCO per cloud, year-by-year breakdown, sensitivity analysis on the dominant variable. The kind of number that goes into board decks.
+1 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