Azure Cost Management MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AZURE_CLIENT_ID | No | Your Azure client ID (required for Service Principal authentication). | |
| AZURE_TENANT_ID | No | Your Azure tenant ID (required for Service Principal authentication). | |
| AZURE_CLIENT_SECRET | No | Your Azure client secret (required for Service Principal authentication). | |
| AZURE_SUBSCRIPTION_ID | No | Default subscription ID to use as scope (optional but recommended). |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| azure_cost_queryA | Queries actual or amortized costs for an Azure scope with grouping and time filtering. WAF Cost Optimization: identify top-spending services and resource groups, track daily trends, and perform chargeback/showback using tag-based grouping. CAF: use management group scope for cross-subscription cost reports aligned to landing zones. |
| azure_cost_forecastA | Retrieves cost forecasts based on current usage trends. WAF Cost Optimization: compare forecast vs budget to detect overspend risk proactively. Set budgets with 100% forecasted threshold to receive early warning alerts (see azure_budget_create). |
| azure_cost_dimensionsA | Lists available dimensions for cost grouping and filtering at a given scope. Use this to discover valid values for the groupBy parameter in azure_cost_query. WAF: discover available tag keys for chargeback/showback analysis before querying. |
| azure_cost_alertsA | Lists active cost alerts for a scope (budget breaches, credit warnings, quota violations, anomalies). WAF Cost Optimization: monitor alerts to detect unexpected cost spikes before they escalate. Complement with azure_budget_list to correlate alerts with budget thresholds. |
| azure_budget_listA | Lists all cost budgets at a given scope with current spend, thresholds, and alert status. WAF Cost Optimization: verify every workload has budget coverage with 80% and 100% alert thresholds. CAF: every landing zone subscription should have at least one monthly budget. |
| azure_budget_getA | Retrieves full details of a specific budget including current and forecasted spend, all alert notification thresholds, and filter configuration. |
| azure_budget_createA | Creates or updates a cost budget with WAF-recommended alert thresholds. Default notifications: 80% actual, 100% actual, 100% forecasted — first line of defense against overruns. WAF Cost Optimization: always set both actual and forecasted alerts on every workload budget. CAF: align timeGrain with billing cycles; include Owner/Contributor in contactRoles for governance. If a budget with the same name already exists at the scope it will be updated in-place. |
| azure_budget_deleteA | Permanently deletes a cost budget. This action cannot be undone. |
| azure_advisor_recommendationsA | Retrieves Azure Advisor cost optimization recommendations for a subscription. Covers: right-sizing underutilized VMs, deleting idle resources (unattached disks, unused IPs), purchasing reservations or savings plans for predictable workloads, and removing empty resource groups. WAF Cost Optimization: address High impact recommendations first for maximum savings. CAF FinOps: run across all landing zone subscriptions to enforce cost governance. Note: Advisor operates at subscription scope; management group scope is not supported. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Each tool targets a distinct aspect of cost management: querying, forecasting, dimensions, alerts, budget CRUD, and Advisor recommendations. The descriptions clarify boundaries between similar tools like alerts vs. budget list, preventing confusion.
Names follow a consistent prefix pattern (azure_cost_, azure_budget_, azure_advisor_) with mostly verb-based actions (query, forecast, list, get, create, delete). However, 'azure_cost_dimensions' and 'azure_cost_alerts' use noun forms, which is a minor deviation from the verb_noun convention.
Nine tools is well-scoped for an Azure cost management server. Each tool serves a clear purpose without redundancy, covering the essential operations for cost analysis and budget management.
The tool surface covers the core cost management lifecycle: querying, forecasting, alerts, budget CRUD, and recommendations. Minor gaps exist, such as lacking cost export functionality or direct alert configuration, but these are not critical for most workflows.