cloudprice-mcp
Related Servers
Alternatives to cloudprice-mcp
No user-submitted related servers found.
Related Servers
- FlicenseBqualityDmaintenanceAn MCP server that gives Claude live access to Azure pricing and cost data — retail prices, VM comparisons, reservation analysis, architecture estimates, and actual subscription spend.9-
- AlicenseAqualityDmaintenanceMulti-cloud pricing comparison MCP server that enables natural language queries to compare compute, storage, egress, and Kubernetes costs across AWS, Azure, GCP, and OCI.3132 npm4Apache 2.0
- AlicenseNot gradedqualityDmaintenanceLive LLM pricing as an MCP server. Ask Claude or any MCP client 'how much does this prompt cost?' and get real numbers from a hand-checked pricing table for every major LLM.MIT
- AlicenseNot gradedqualityBmaintenanceMCP server for monitoring competitor pricing pages, scraping pricing data into SQLite, and answering plain-language questions about pricing plans via Claude.MIT
- FlicenseNot gradedqualityDmaintenanceProvides real-time LLM pricing and availability data as an MCP server, enabling AI agents to make optimal model routing decisions at inference time with cited pricing sources.-
- AlicenseBqualityCmaintenanceAn MCP server for unified cost tracking and analysis across AWS, OpenAI, and Anthropic. It enables users to query expenditures, compare costs across providers, and analyze usage trends through natural language.10MIT
TDQS
Scored across 14 tools
Most tools have clearly distinct purposes: compare_clouds for single VM, compare_compute_inventory for bulk compute, compare_workload for combined compute+storage, etc. However, assess_migration and compare_total_cost_of_ownership overlap in projecting workload costs, and compare_workload overlaps with separate inventory tools, causing minor ambiguity.
Names follow a mostly consistent pattern: 'compare_' for multi-cloud comparisons, 'get_' for single-cloud lookups, and specialized verbs like 'assess_', 'find_', 'optimize_'. Minor variations exist (e.g., compare_total_cost_of_ownership vs compare_clouds) but overall readable and predictable.
14 tools is well-scoped for a cloud pricing server. Each tool covers a distinct pricing scenario (single VM, bulk compute, storage, egress, databases, migration, TCO, commitment), avoiding redundancy without missing critical functionality.
The tool set covers core compute, storage, egress, database, migration, and TCO scenarios. Notable gaps include non-PostgreSQL databases, serverless compute, and advanced networking costs (e.g., VPC peering, load balancers). Descriptions acknowledge missing features, which agents can work around.