azure-vm-pricing-mcp
Related Servers
Alternatives to azure-vm-pricing-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceAnchor AI FinOps to real, live cloud pricing. AWS, GCP & Azure — public list prices and enterprise negotiated rates. No credentials needed for AWS and Azure public pricing.1535 PyPI3MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to query Azure retail pricing, compare costs, estimate bills, and analyze reserved instances, with additional tools for spot VMs, orphaned resources, PTU sizing, Databricks DBU, and GitHub pricing.1MIT
- AlicenseNot gradedqualityBmaintenanceMCP server that converts hardware specs into Azure price quotes using live Azure Retail Prices API. Provides tools to propose VM flavors, get full quotes with disk and reservation options, and batch-analyze RVTools exports.MIT
- AlicenseAqualityFmaintenanceProvides AI assistants with real-time access to Azure retail pricing information, enabling price searches, regional cost comparisons, monthly bill estimates, and SKU discovery through natural language queries.1356MIT
- AlicenseAqualityBmaintenanceLive LLM API pricing: current token prices, model comparisons, cheapest-model lookups, and The LLM Price Index for 150+ models across 20+ providers, re-verified daily. No API key required.41MIT
- AlicenseAqualityBmaintenanceGlobal price benchmarking for AI inference across 2,600+ SKUs from 47 vendors. Query live pricing, market indexes, and model specs via 8 tools. Free tier available.8128 npmMIT
TDQS
Scored across 4 tools
Each tool has a distinct primary purpose: change reporting, single-size lookup, requirement-based discovery, and multi-size cost projection. However, get_vm_size (per-region hourly prices), find_vm_sizes (monthly list prices), and estimate_vm_cost (monthly/yearly costs with commitments) all surface pricing data, so an agent could reasonably confuse which pricing tool to pick for a given question.
All four names follow a clean verb_noun snake_case pattern (get_price_changes, get_vm_size, find_vm_sizes, estimate_vm_cost). Verb choices (get/find/estimate) are predictable and the singular/plural distinction between get_vm_size and find_vm_sizes is semantically meaningful, not inconsistent.
Four tools is slightly lean but well-scoped for a narrow domain like Azure VM pricing: monitoring, lookup, search, and estimation. Nothing redundant, though a slightly broader surface (e.g., a catalog/region listing tool) would round it out.
The surface covers the core pricing lifecycle: change tracking, per-size specs and regional prices, requirement-based discovery, and commitment cost estimation with break-even analysis. Gaps are minor (no spot/preemptible pricing, no full catalog or region listing), but agents can work around them with the existing tools.