Aws Pricing MCP vs Infrawise — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Aws Pricing MCP vs Infrawise
In-depth architectural comparison of the Aws Pricing 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
Aws Pricing MCP
Cloud Platforms · Local stdio
Quality: 33/100 (Emerging) | Auth: No auth required
Infrawise
Cloud Platforms · Local stdio
Quality: 64/100 (Good) | Auth: API Key required
Verdict Summary: Choose Aws Pricing 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 Aws Pricing 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).
You have access to required keys: AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, AWS_SESSION_TOKEN.
Primary tools included: Provides EC2 pricing data from up-to-date AWS catalog, Supports multiple pricing models: On Demand, Reserved, CloudFix RightSpend, Flexible filtering by region, platform, tenancy, vCPU, RAM, GPU.
/🏠 - Get up-to-date EC2 pricing information with one call. Fast. Powered by a pre-parsed AWS pricing catalogue.
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
Aws Pricing MCP Tools (6)
Provides EC2 pricing data from up-to-date AWS catalog
Supports multiple pricing models: On Demand, Reserved, CloudFix RightSpend
Flexible filtering by region, platform, tenancy, vCPU, RAM, GPU
Full JSON-RPC 2.0 MCP protocol compliance
Available as serverless AWS Lambda function with Function URL
Dynamic pricing data sourced from AWS S3
Infrawise Tools (22)
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).
Aws Pricing MCP is categorized under Cloud Platforms and uses a local stdio subprocess. In contrast, Infrawise belongs to Cloud Platforms using local stdio subprocess. Select Aws Pricing MCP when you need capabilities focused on cloud platforms and Infrawise when you require tools for cloud platforms.
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