--- title: "Google Cloud Billing MCP server for AI agents - actionlake" description: "Give Claude 31 Google Cloud Billing actions through one MCP server: billing accounts. Your agent never holds the credential. 100,000 calls a month free." canonical: https://actionlake.com/connectors/google-cloud-billing updated: 2026-10-23 --- Connectors · Accounting & finance # Google Cloud Billing MCP server for AI agents. actionlake is an MCP gateway: one remote MCP server that connects Claude and other MCP clients to Google Cloud Billing and the rest of your systems. It gives your agent 31 Google Cloud Billing actions (16 reads, 11 writes and 4 that wait for a confirmation) and holds the Google Cloud Billing credential itself, so the agent never does. It paces Google Cloud Billing's limits and records every call. Connecting Google Cloud Billing needs your own Google Cloud Billing OAuth app and one admin sign-in. [Connect Google Cloud Billing free](https://actionlake.com/console?start=sandbox) [See pricing](https://actionlake.com/pricing) 100,000 free calls a month. No card, no email, no password: press Start a free sandbox on the next screen and keep the key it shows you. `claude mcp add --transport http actionlake https://connect.actionlake.com/mcp` the first call ``` do { action: "gcp_cloud_billing.billing_accounts.list", intent: "check which Google Cloud Billing account is connected" } # Billing accounts: list · read · 1 upstream call ``` - 31 actions in one signed file - 16 read look, never change - 11 write create and update - 4 wait for a yes destructive, confirmed first Set up ## Connect Google Cloud Billing in three steps. 1. 01 ### Add actionlake to Claude. Run the command once in Claude Code; its consent page can create a free sandbox: 100,000 calls a month, no card. In the Claude app, add a custom connector with the URL below and paste your key on the consent page. Creating a new sandbox from the Claude app is not yet tested by us. `https://connect.actionlake.com/mcp` 2. 02 ### Connect Google Cloud Billing. OAuth 2.0, authorization code with PKCE. You register your own OAuth app with Google Cloud Billing, an admin signs in once, and you paste the app's client id and secret and the tokens from that sign-in; actionlake renews the access token from then on. actionlake stores what you paste write-only, sealed under your tenant's key. Before the first sign-in, Google Cloud Billing needs an OAuth app of your own, registered in its developer portal. actionlake has no Google Cloud Billing app to lend you. - `access_token` Access token from one sign-in with your own OAuth app - `refresh_token` Refresh token from the same sign-in; the access token is renewed from it - `client_id` Google OAuth client id (Google Cloud console > APIs & Services > Credentials; enable the Cloud Billing and Cloud… - `client_secret` Google OAuth client secret ``` account { op: "connections.requirements", service: "gcp_cloud_billing" } # free: exactly what to paste, and what is found for you ``` 3. 03 ### Make the first call. Check before a write. Ask in plain words; Claude picks the action. Before anything changes, `check` validates the call and prices it, for free. ``` do { action: "gcp_cloud_billing.billing_accounts.list" } # billing accounts: list · read · 1 upstream call check { action: "gcp_cloud_billing.billing_accounts_budgets.create", input: { … } } # free: inputs, permissions, cost and confirmations, nothing sent ``` Google Cloud Billing at a glance **Sign-in** OAuth 2.0, authorization code with PKCE. You register your own OAuth app with Google Cloud Billing, an admin signs in once, and you paste the app's client id and secret and the tokens from that sign-in; actionlake renews the access token from then on. **You provide** `access_token` `refresh_token` `client_id` `client_secret` **Limits we pace to** 300 calls a minute, per connection **API covered** Google Cloud Billing (billing accounts, project billing, SKU pricing catalog, budgets) API cloudbilling v1 (Discovery revision 20261016) + billingbudgets v1 (revision 20261018)`cloudbilling.googleapis.com` **Built from** Google Cloud Billing's documentation, read 23 October 2026[cloudbilling.googleapis.com](https://cloudbilling.googleapis.com/$discovery/rest?version=v1) [billingbudgets.googleapis.com](https://billingbudgets.googleapis.com/$discovery/rest?version=v1) [cloud.google.com](https://cloud.google.com/billing/docs/reference/rest) **Service file** Version 1.0.0, signed (Ed25519) **Cached reads** 16 of 16 reads, for up to 5 minutes; a write clears what it affects **Shared entities** 2, so ask can line Google Cloud Billing up with your other systems **Data** Processed and stored in Sydney, Australia. No US region yet Capabilities ## What an AI agent can do in Google Cloud Billing. 31 actions in 12 areas. Every one carries its effect, so a key can allow the reads and hold the rest. - **16** read look, never change - **11** write create and update - **4** destructive wait for a confirmation 1. ### Billing accounts 8 4 read · 3 write · 1 destructive Billing accounts: list · Billing accounts: create · Billing accounts: test iam permissions · Billing accounts: get 2. ### Billing accounts budgets 5 2 read · 2 write · 1 destructive Billing accounts budgets: list · Billing accounts budgets: create · Billing accounts budgets: get · Billing accounts budgets: patch 3. ### Tasks push notification configs 4 2 read · 1 write · 1 destructive Tasks push notification configs: create · Tasks push notification configs: list · Tasks push notification configs: get · Tasks push notification configs: delete 4. ### Organizations billing accounts 3 1 read · 2 write · 0 destructive Organizations billing accounts: create · Organizations billing accounts: list · Organizations billing accounts: move 5. ### Billing accounts sub accounts 2 1 read · 1 write · 0 destructive Billing accounts sub accounts: create · Billing accounts sub accounts: list 6. ### Projects 2 1 read · 1 write · 0 destructive Projects: get billing info · Projects: update billing info 7. ### Tasks 2 1 read · 0 write · 1 destructive Tasks: get · Tasks: cancel 8. ### Agent 1 1 read · 0 write · 0 destructive V1: get card **4 more areas · 4 actions** - Billing accounts projects **1** - Message **1** - Services **1** - Services skus **1** Top actions ## The Google Cloud Billing API, shaped for agents. The ids your agent types, what each does, and the one name it shares with other systems. 5 of Google Cloud Billing's 5 action names are shared with at least one other connector, so an agent learns them once. | Action | What it does | Effect | Same name in | | --- | --- | --- | --- | | `gcp_cloud_billing.billing_accounts_budgets.list` Billing accounts budgets: list | Returns a list of budgets for a billing account. | read | `finance.budget.list` 15 connectors | | `gcp_cloud_billing.billing_accounts_budgets.create` Billing accounts budgets: create | Creates a new budget. | write | `finance.budget.create` 9 connectors | | `gcp_cloud_billing.billing_accounts_budgets.delete` Billing accounts budgets: delete | Deletes a budget. | destructive | `finance.budget.delete` 7 connectors | | `gcp_cloud_billing.billing_accounts.list` Billing accounts: list | Lists the billing accounts that the current authenticated user has permission to [view](https://cloud.google.com/billing/docs/how-to/billing-access). | read | this connector | | `gcp_cloud_billing.services_skus.list` Services skus: list | Lists all publicly available SKUs for a given cloud service. | read | this connector | | `gcp_cloud_billing.services.list` Services: list | Lists all public cloud services. | read | this connector | | `gcp_cloud_billing.billing_accounts.create` Billing accounts: create | This method creates [billing subaccounts](https://cloud.google.com/billing/docs/concepts#subaccounts). | write | this connector | | `gcp_cloud_billing.organizations_billing_accounts.list` Organizations billing accounts: list | Lists the billing accounts that the current authenticated user has permission to [view](https://cloud.google.com/billing/docs/how-to/billing-access). | read | this connector | | `gcp_cloud_billing.organizations_billing_accounts.create` Organizations billing accounts: create | This method creates [billing subaccounts](https://cloud.google.com/billing/docs/concepts#subaccounts). | write | this connector | | `gcp_cloud_billing.projects.get_billing_info` Projects: get billing info | Gets the billing information for a project. | read | this connector | | `gcp_cloud_billing.projects.update_billing_info` Projects: update billing info | Sets or updates the billing account associated with a project. | write | this connector | | `gcp_cloud_billing.message.send` Message: send | Send a message to the agent. | write | this connector | Try it ## Prompts to paste into Claude. Each one names the Google Cloud Billing actions it will call, so you know what it reads and what it changes before you send it. 1. Read read Billing accounts: list in Google Cloud Billing and tell me what stands out. calls `gcp_cloud_billing.billing_accounts.list` 2. Write write Billing accounts budgets: create in Google Cloud Billing. Show me exactly what you will send before you save it. calls `gcp_cloud_billing.billing_accounts_budgets.create` Governance for Google Cloud Billing ## Destructive actions wait for a yes. 4 Google Cloud Billing actions are destructive. These are all of them: - Billing accounts budgets: delete `gcp_cloud_billing.billing_accounts_budgets.delete` - Billing accounts: set iam policy `gcp_cloud_billing.billing_accounts.set_iam_policy` - Tasks: cancel `gcp_cloud_billing.tasks.cancel` - Tasks push notification configs: delete `gcp_cloud_billing.tasks_push_notification_configs.delete` A destructive action runs only with `confirm: true`. Under the `human` policy the agent cannot confirm for itself: the run stops until a named person approves, in the console or from a signed link in an email. The cap on a key is refused before the call is sent, never after. do gcp_cloud_billing.billing_accounts_budgets.delete confirm_policy: **human** Billing accounts budgets: delete? **intent:** the user asked me to billing accounts budgets: delete run suspended · waiting for a named person · key _gcp-cloud-billing-agent_ cannot confirm itself In the console, or from an emailed signed link. a key for this connector ``` account { op: "keys.create", name: "gcp-cloud-billing-agent", allowed_actions: ["gcp_cloud_billing.*"], cap_calls: 2000, confirm_policy: "human_for_writes", approval_rules: [ { match: "gcp_cloud_billing.billing_accounts_budgets.delete", approver: "lead@example.com" }, { match: "gcp_cloud_billing.billing_accounts.set_iam_policy", approver: "lead@example.com" }, { match: "gcp_cloud_billing.tasks.cancel", approver: "lead@example.com" } ] } ``` Illustrative. Scoped to Google Cloud Billing only, capped at 2,000 upstream calls, every write confirmed, and the destructive ones approved by a named person. Cost ## What Google Cloud Billing costs on actionlake. Every Google Cloud Billing action is one upstream call, the only thing actionlake bills. Searching, `check`, `cost`, `account` and any call Google Cloud Billing refused with 401, 403, 429 or a 5xx are free. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000. - 1 upstream call per action all 31 Google Cloud Billing actions - 8 actions page each page of a long list is one call - 16 reads can be cached a cache hit costs nothing - 100,000 calls a month, free paid plans from US$49 a month for 250,000 [See pricing](https://actionlake.com/pricing) Action index ## Every Google Cloud Billing action. 31 actions by area: the id your agent calls, what it does, and its effect. **Billing accounts 8** - `gcp_cloud_billing.billing_accounts.create` Billing accounts: create write - `gcp_cloud_billing.billing_accounts.get` Billing accounts: get read - `gcp_cloud_billing.billing_accounts.get_iam_policy` Billing accounts: get iam policy read - `gcp_cloud_billing.billing_accounts.list` Billing accounts: list read - `gcp_cloud_billing.billing_accounts.move` Billing accounts: move write - `gcp_cloud_billing.billing_accounts.patch` Billing accounts: patch write - `gcp_cloud_billing.billing_accounts.set_iam_policy` Billing accounts: set iam policy destructive - `gcp_cloud_billing.billing_accounts.test_iam_permissions` Billing accounts: test iam permissions read **Billing accounts budgets 5** - `gcp_cloud_billing.billing_accounts_budgets.create` Billing accounts budgets: create write - `gcp_cloud_billing.billing_accounts_budgets.delete` Billing accounts budgets: delete destructive - `gcp_cloud_billing.billing_accounts_budgets.get` Billing accounts budgets: get read - `gcp_cloud_billing.billing_accounts_budgets.list` Billing accounts budgets: list read - `gcp_cloud_billing.billing_accounts_budgets.patch` Billing accounts budgets: patch write **Tasks push notification configs 4** - `gcp_cloud_billing.tasks_push_notification_configs.create` Tasks push notification configs: create write - `gcp_cloud_billing.tasks_push_notification_configs.delete` Tasks push notification configs: delete destructive - `gcp_cloud_billing.tasks_push_notification_configs.get` Tasks push notification configs: get read - `gcp_cloud_billing.tasks_push_notification_configs.list` Tasks push notification configs: list read **Organizations billing accounts 3** - `gcp_cloud_billing.organizations_billing_accounts.create` Organizations billing accounts: create write - `gcp_cloud_billing.organizations_billing_accounts.list` Organizations billing accounts: list read - `gcp_cloud_billing.organizations_billing_accounts.move` Organizations billing accounts: move write **Billing accounts sub accounts 2** - `gcp_cloud_billing.billing_accounts_sub_accounts.create` Billing accounts sub accounts: create write - `gcp_cloud_billing.billing_accounts_sub_accounts.list` Billing accounts sub accounts: list read **Projects 2** - `gcp_cloud_billing.projects.get_billing_info` Projects: get billing info read - `gcp_cloud_billing.projects.update_billing_info` Projects: update billing info write **Tasks 2** - `gcp_cloud_billing.tasks.cancel` Tasks: cancel destructive - `gcp_cloud_billing.tasks.get` Tasks: get read **Agent 1** - `gcp_cloud_billing.agent.get_card` V1: get card read **Billing accounts projects 1** - `gcp_cloud_billing.billing_accounts_projects.list` Billing accounts projects: list read **Message 1** - `gcp_cloud_billing.message.send` Message: send write **Services 1** - `gcp_cloud_billing.services.list` Services: list read **Services skus 1** - `gcp_cloud_billing.services_skus.list` Services skus: list read Questions ## The Google Cloud Billing MCP server, answered. **Is there a Google Cloud Billing MCP server for Claude?** Yes. actionlake is an MCP gateway: a remote MCP server that gives Claude, or another MCP client, 31 Google Cloud Billing actions across billing accounts, billing accounts budgets, tasks push notification configs and organizations billing accounts, through the same eight tools it uses for every other connector. actionlake is independent; it is not made or endorsed by Google Cloud Billing. **What do I need to connect Google Cloud Billing?** Your own Google Cloud Billing OAuth app, registered with Google Cloud Billing (its client id and client secret), and the access and refresh tokens from one admin sign-in. actionlake has no Google Cloud Billing app of its own, so this is not a one-step consent. actionlake renews the access token as it expires. The free call account { op: "connections.requirements", service: "gcp_cloud_billing" } lists exactly what to paste. **Can an AI agent delete or change things in Google Cloud Billing?** Only if its key allows it, and only with an explicit confirmation. 4 Google Cloud Billing actions are destructive, including billing accounts budgets: delete, billing accounts: set iam policy and tasks: cancel. Each runs only with confirm: true. Under the human confirm policy, or an approval rule on the key, the run waits until a named person approves it. **Will an AI agent use up my Google Cloud Billing API limit?** actionlake paces every call to the limits in the Google Cloud Billing service file: 300 calls a minute per connection. Repeated reads are answered from cache (16 Google Cloud Billing actions can be), which never reaches Google Cloud Billing. **What does a Google Cloud Billing action cost?** One upstream call, the only unit actionlake bills. A list that pages bills one call per page (8 Google Cloud Billing actions page). Cache hits, searches, dry runs and calls Google Cloud Billing refused with 401, 403, 429 or a 5xx are free. The Free plan includes 100,000 calls a month with no card. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000. **Which Google Cloud Billing API does it cover?** The Google Cloud Billing (billing accounts, project billing, SKU pricing catalog, budgets) API cloudbilling v1 (Discovery revision 20261016) + billingbudgets v1 (revision 20261018) at cloudbilling.googleapis.com. It is built from Google Cloud Billing's documentation as read on 23 October 2026. 31 actions in 12 areas, each one in the signed service file (version 1.0.0). **Does actionlake keep my Google Cloud Billing data, and where?** actionlake processes and stores data in Sydney, Australia; there is no US region yet. Reads may be cached for up to 5 minutes, and a write clears the reads it affects. Each run's request and response is kept, sealed, for your plan's trace window: 1 day on Free, 3 days on Starter, 7 days on Pro, 14 days on Team, 30 days on Business and 30 days on Enterprise. Your Google Cloud Billing credential is sealed under your tenant's key, never logged and never returned. Your traffic is not used to train models. **Which AI clients can use it?** Claude Code, tested by us end to end, and the Claude app as a custom connector, tested by us with an existing key. Other MCP clients that support remote servers over Streamable HTTP (MCP revisions 2025-06-18 and 2025-11-25) and OAuth dynamic client registration, or a bearer header, should connect the same way; we have not tested them. Or plain REST, under the same action names. ## More connectors like Google Cloud Billing Shares the most action names with - [BILL 5](https://actionlake.com/connectors/bill) - [Mercury 4](https://actionlake.com/connectors/mercury) - [Brex 4](https://actionlake.com/connectors/brex) - [Buildium 4](https://actionlake.com/connectors/buildium) - [Coupa 4](https://actionlake.com/connectors/coupa) - [SAP Concur 3](https://actionlake.com/connectors/sap-concur) Joins with, on shared entities - [Blackbaud SKY API 1](https://actionlake.com/connectors/blackbaud-sky-api) - [Rev.io 1](https://actionlake.com/connectors/rev-io) - [Cin7 Core 1](https://actionlake.com/connectors/cin7-core) - [Cliniko 1](https://actionlake.com/connectors/cliniko) - [Gorelo 1](https://actionlake.com/connectors/gorelo) Browse - [All Accounting & finance connectors](https://actionlake.com/connectors/category/accounting-and-finance) - [All connectors](https://actionlake.com/connectors) - [How actionlake compares](https://actionlake.com/compare) actionlake is independent. It is not made or endorsed by Google Cloud Billing; the name is the vendor's own. Counts are from the Google Cloud Billing service file, version 1.0.0. ## Give your agent Google Cloud Billing today. [Connect Google Cloud Billing free](https://actionlake.com/console?start=sandbox) [See pricing](https://actionlake.com/pricing) Start free - 100,000 calls/month, no card. No signup. Hard caps on every key. Cached answers are free. --- Source: https://actionlake.com/connectors/google-cloud-billing More: https://actionlake.com/llms.txt