Google Cloud Billing MCP server: 29 tools, none for spend

What Google's hosted billing endpoint reaches, which three of its tools change state, and where your actual spend still has to come from.

Last verified 1 September 2026 · from Google's Cloud Billing MCP reference, a live tools/list against the endpoint, and the gcloud-mcp repository

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 Google Cloud Billing MCP server?

Google Cloud bills through Cloud Billing. A billing account pays for one or more projects, and an optional export sends the detailed charges to BigQuery for analysis.

This server models the structure and the price list. It reads which account pays for a project, who has access to that account, and what each SKU costs. A SKU is one billable unit of a service, such as a machine type in a region.

It does not model consumption. No tool returns what an account was charged, none queries usage, and none returns an invoice total. The output fields across all 29 tools are account metadata, access policy and prices.

Four routes to a Google Cloud cost question:

The distinction that decides this page: a price is what a unit costs, and a bill is that price multiplied by what you used. Only the middle two rows reach the second.

This page is named for cost management, and the billing server now covers part of that stage.

The server answers what a service costs and which account pays for a project. It does not answer what that project was charged.

What can an AI agent do with Google Cloud Billing?

Google Cloud Billing MCP server limits: where answers come back incomplete

Google Cloud Billing now has a real server, and the limits that matter are about what it covers rather than whether it exists.

How to configure Google Cloud Billing MCP for agents

1. 1

   Decide whether the three write tools should be reachable at all

   set_iam_policy grants and revokes access to a billing account, and Google marks it destructive.

2. 2

   Scope the credential, not the tool list

   The endpoint offers all 29 tools to every caller. IAM decides which ones actually succeed.

3. 3

   Know that the inventory is public

   A tools/list against the endpoint returns every tool and schema without a credential, so the shape of the server is not a secret.

4. 4

   Separate a rate from a bill

   get_billing_account_price returns the prices that apply to your account, which is closer than the public catalog and still not a charge.

5. 5

   Keep the BigQuery export for spend questions

   No tool on this server reaches consumption, so the export stays the route for anything about actual money.

Paste this into your agent’s instructions

Two different servers and one export can each answer a Google Cloud cost question, and they return different kinds of number. The block forces the agent to name which one it used.

When you answer a Google Cloud cost question, state:
- Which route produced the number: a tool on the Cloud
  Billing MCP server, a gcloud command, or the BigQuery
  billing export.
- Whether the number is a price or an amount charged. The
  billing server returns prices only. It has no tool that
  returns what was spent.
- The billing account or project the number applies to.
Never state that data does not exist. The charges exist, in
the billing export. Say which route you used, say what it
returned, and name the route that holds the rest.
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?

Yes for account structure and prices, and no for spend. The 29 tools answer which account pays for a project and what a SKU costs. They never answer what you were charged.

The Cloud Billing export to BigQuery is Google's own route for analyzing charges. An agent that can already query BigQuery can query it without a new connector.

gcloud billing in a terminal reaches the same data as the passthrough, and does not hand a model the whole command line.

For spend across more than one cloud, Vantage, CloudZero and OpenCost publish servers built around cost rather than around a billing API.

Use the billing server for accounts, access and prices. Use the BigQuery export or a purpose-built connector for what you actually spent.

Google Cloud Billing MCP server setup

There are two Google servers here and one export, and they answer different questions. Start by deciding which question you have.

The billing server is hosted, so nothing installs. You point a client at a single URL and authenticate to Google.

The reference page names two prerequisites before any of that: enable MCP servers, and set up authentication.

curl --location 'https://cloudbilling.googleapis.com/mcp' \
  --header 'content-type: application/json' \
  --header 'accept: application/json, text/event-stream' \
  --data '{"method": "tools/list", "jsonrpc": "2.0", "id": 1}'

Request is missing required authentication credential.
Expected OAuth 2 access token, login cookie or other
valid authentication credential.

Every other client

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

{"mcpServers":{"gcloud":{
  "command":"npx",
  "args":["-y","@google-cloud/gcloud-mcp"]}}}

billing MCP server : accounts, IAM, prices -> no spend
run_gcloud_command : drives the CLI        -> actual spend
BigQuery export    : detailed charges      -> actual spend
community server   : Catalog API           -> estimates

Read-only access, permissions and security

• Three tools change state, and two are marked destructive

  move_billing_account reparents an account between organizations, and set_iam_policy overwrites its access control policy.

• set_iam_policy is the sharpest tool here

  A policy write can grant billing access to a new principal, or remove it from an existing one, in a single call.

• The endpoint hands every caller all 29 tools

  There is no read-only mode documented on the reference page, so IAM on the credential is the only boundary that holds.

• The tool inventory is public

  Anyone can list the tools and schemas without authenticating, though calling one is refused without a credential.

• gcloud-mcp carries its own risk, separately

  One tool runs almost the whole CLI, and its ten denied prefixes are SSH, tunnel, serial port, interactive and meta commands rather than destructive ones.

• Billing data is commercially sensitive

  Account structure and negotiated prices describe what a company buys and what it pays, which is not something to expose broadly.

Troubleshooting

Request is missing required authentication credential

The call reached the server and was refused for want of a credential. The message names an OAuth 2 access token, a login cookie, or another valid credential.

It arrives as tool content with isError set rather than an HTTP 401, so a client that only checks status codes will treat the request as successful.

You cannot find a tool that reports spend

There is not one. All 29 tools return account metadata, access policy or prices, and no output field on any of them carries an amount charged.

Use the Cloud Billing export to BigQuery, or run gcloud billing through the separate gcloud server.

The numbers do not match the invoice

Check which price you read. list_prices is the public catalog, and list_billing_account_prices is what applies to your account. Neither reflects what you consumed.

A regional endpoint is refused

There is not one. Google notes that its MCP endpoints can be global or regional, and documents only the global address for Cloud Billing.

The agent runs a gcloud command you did not expect

That is the design of the other server. run_gcloud_command takes the command as an argument. Impersonate a service account with a limited role if that is not acceptable.

Google Cloud Billing MCP server: Reference

What the vendor documents

Practitioner writing about this server is thin, because it is new. The reference page carries a last-updated date of 18 August 2026. The counts below come from the documentation and from the endpoint itself.

“Google MCP endpoints can be global or regional.”

“Request is missing required authentication credential. Expected OAuth 2 access token, login cookie or other valid authentication credential.”

“This repository is currently in preview and may see breaking changes. This repository provides a solution, not an officially supported Google product.”

The reference page and its 29 per-tool pages were read on 1 September 2026. A tools/list and an initialize were sent to the endpoint on the same day, and returned 29 tools and protocol version 2025-11-25. The googleapis/gcloud-mcp README was searched for billing on the same date, returning no matches.

Should you connect an agent to Google Cloud Billing?

Yes. Best for account structure, access review and pricing. Send spend questions to the export or a purpose-built connector.

Strongest fit

Teams who want an agent to read billing account structure, who has access to it, and what Google Cloud services cost them.

Main advantage

It is hosted by Google, needs no install, and 26 of its 29 tools are marked read-only by the vendor.

Main weakness

It returns prices rather than charges, so the most common cost question still goes to the BigQuery export.

Operational risk

Three tools write, including an access policy write on a billing account, and the server offers all of them to every caller.

Frequently asked questions