Azure Cost Management MCP: real spend, two clients

What the 14 cost tools return, which 5 need no configuration, and why the preview reaches GitHub Copilot and little else.

Last verified 1 September 2026 · from The Azure Resource Manager MCP server's README, its Cost Management tool reference and the GitHub API

This page is one of 90 in a directory of monitoring and developer tools. Each page checks what an AI coding agent can get out of the tool through its MCP server, the connector that lets the agent query the tool directly.

What is the Azure Cost Management MCP server?

Azure Cost Management is the service that holds actual spend. It covers usage records, amortized reservation costs, budgets, alerts and exports.

MCP is an open protocol that lets an AI coding agent call a tool's functions, such as running a log search, without anyone writing code against the tool's API. Microsoft's server puts the Cost Management APIs behind that protocol.

Cost is the stage this page grades, and the same endpoint reaches further. It also deploys ARM templates and runs Azure Resource Graph queries, which arrive on the same connection.

What answers an Azure cost question:

The first two rows are the same endpoint, and the difference between them is one header. The third is a different server that Microsoft also publishes, and it answers rate-card questions rather than billed ones.

Azure Cost Management is named for the cost stage, and the cost stage is the one this connector serves best.

The cost stage is where this endpoint is strongest. What limits it is not coverage but the short list of clients the preview will accept.

What can an AI agent do with Azure Cost Management?

The 5 default tools answer what a cost review opens with. query_costs returns actual or amortized spend for a subscription, management group or billing scope, grouped and filtered as asked. query_aks_costs splits an AKS bill by cluster, namespace, idle time and service category, at subscription scope only. get_retail_prices needs no sign-in. The pricesheet pair fetches a negotiated EA or MCA rate card as an asynchronous download. Budgets and forecasts wait behind the CostManagement header.

Azure Cost Management MCP server limits: where answers come back incomplete

The first limit below decides whether the connector is reachable at all. The rest change what an answer means once it is.

How to configure Azure Cost Management MCP for agents

1. 1

   Set the header if you need budgets

   Without x-mcp-toolset: CostManagement, an agent sees 5 cost tools rather than 14.

2. 2

   Check your client before anything else

   The preview names two, and both are GitHub Copilot. Anything else needs an app registration.

3. 3

   Know which tool writes

   create_budget creates a budget with threshold notifications. The other 13 cost tools return data.

4. 4

   Expect one tenant at a time

   The FAQ states there is no way to name a tenant per request, so the signed-in account decides.

5. 5

   Query a billing scope for wide comparisons

   The reference advises one call against a billing scope instead of one call per subscription.

Paste this into your agent’s instructions

Actual spend and a retail rate are both currency figures in a sentence, and this server returns both. Nothing in an answer separates them unless the agent is made to say which tool produced it.

When you answer an Azure cost question, state:
- Whether the figure is actual spend, amortized cost or a
  retail list price. query_costs returns what was charged
  and get_retail_prices returns published rates.
- The scope, the timeframe and the currency it applies to.
- Whether the CostManagement toolset is enabled, because
  budgets, forecasts and benefit data need that header.
- That a cost query returns 100 rows by default, so a
  total may be partial.
Never state that data does not exist. State which tool you
called and what it returned.
Write your answer in ASD-STE100 Simplified Technical
English. Use short sentences with one idea in each.

Do you need the MCP server at all?

You do not need it for a single figure, because Cost Management already answers through the Azure portal and its REST API. The server matters when an agent has to ask the question mid-conversation.

Cost Management exports write usage and amortized cost to storage on a schedule. That stays the route for a complete bill, because a cost query returns 100 rows by default.

For more than one cloud, FOCUS is an open billing format, and glassity/focus-mcp reads AWS, Azure and GCP through it.

msftnadavbh/AzurePricingMCP remains a pricing tool. It estimates and compares rates, which is a different question from what a subscription was charged.

With MCP, spend, forecasts and budgets arrive in the same conversation as the resources that caused them, over one endpoint with nothing installed.

Connect it if a supported client can reach it. Otherwise read an export or call the REST API, and keep the app registration in reserve.

Azure Cost Management MCP server setup

Nothing gets installed. Microsoft hosts the server at https://mcp.management.azure.com, and a client reaches it as an HTTP MCP server.

What you need first is an Azure account with access to a subscription, and a client the preview accepts. The server acts as the signed-in user, so Azure roles decide what it can read.

Adding x-mcp-toolset: CostManagement to the same entry is what turns 5 cost tools into 14.

{"servers":{"azure-resource-manager-mcp":{
  "type":"http",
  "url":"https://mcp.management.azure.com",
  "headers":{"x-mcp-toolset":"CostManagement"}}}}

{"mcpServers":{"azure-resource-manager-mcp":{
  "type":"http",
  "url":"https://mcp.management.azure.com",
  "headers":{"x-mcp-toolset":"CostManagement"}}}}

az ad sp create --id 22bfbae3-f4e7-485f-be43-8cee15065084
# then add the redirect URI, create a client secret,
# and use it in the custom connector definition

Every other client

Each block below is the configuration for one client, with the file path and the key that client expects.

{"mcpServers":{"azure":{
  "command":"npx",
  "args":["-y","@azure/mcp@latest","server","start"]}}}

Read-only access, permissions and security

• The server acts as the signed-in user

  The README states that every tool call is made on that user's behalf, under the same Azure permissions.

• Spend data is commercially sensitive

  What a company spends on which service describes what it is building, so scope the role before connecting.

• One cost tool changes state

  create_budget writes a budget with notification rules, and the reference marks it as the only write among the 14.

• The connection reaches past cost

  The same endpoint registers deployment and resource-creation tools, so a cost question carries them along.

• Deployments can be denied by policy

  The README documents an Azure Policy sample that blocks create_deployment by the server's application ID.

• The third-party route is a broad grant

  An app registration with a client secret, plus Owner on a subscription, is a larger ask than a read-only connector.

Troubleshooting

Your client cannot connect

The preview accepts GitHub Copilot Chat in VS Code and GitHub Copilot CLI. Other clients need the app registration route in docs/OtherClientSupport.md.

There is no budget or forecast tool

Those 9 tools sit in the CostManagement toolset. Add x-mcp-toolset: CostManagement to the server entry, then restart the server in the client.

AADSTS500200 on sign-in

The troubleshooting guide attributes this to a personal account. It suggests an organizational account, or inviting the personal account into the tenant as a guest.

The costs are from the wrong tenant

The FAQ states one tenant can be queried at a time, with no per-request tenant setting. The account falls back to its default tenant.

A total looks too small

A cost query returns 100 rows by default. The top parameter is registered up to 5,000, and a wide question may still need a narrower grouping.

Azure Cost Management MCP server: Reference

What the vendor documents

Public practitioner writing about these tools is thin, so the quotations below are Microsoft's own words about its own server.

“Several Cost Management & Pricing tools are enabled by default and need no extra configuration”

“During this preview, Azure Resource Manager MCP server can only be used with a set of MCP Clients.”

“The Azure Resource Manager MCP server ships a Cost Management & Pricing tool surface that lets agents answer cost, budget, savings, and pricing questions in natural language, on behalf of the signed-in user.”

The tool inventory was read from the server's Cost Management and Pricing reference and its README on 1 September 2026, and the two lists reconcile at 5 plus 9. Repository facts come from the GitHub API on the same date.

Should you connect an agent to Azure Cost Management?

Yes, with one of the four checks failing. Best for cost questions asked inside Copilot, with budgets and forecasts switched on by header.

Strongest fit

Teams working in GitHub Copilot who want an agent to read real Azure spend without leaving the editor.

Main advantage

Billed and amortized spend from a first-party hosted endpoint, with no package to install and no key to store.

Main weakness

The preview accepts two clients. Reaching it from anywhere else needs an Azure app registration and a client secret.

Operational risk

A default connection that carries deployment and resource-creation tools alongside the cost ones.

Frequently asked questions