← Explore all mcp servers

CLOUD OPERATIONS / Google

gcloud MCP Server

Google's gcloud MCP server, published in the googleapis organisation, lets agents drive Google Cloud through the gcloud CLI in natural language — describing outcomes instead of memorising flags. The monorepo hosts three further Google Cloud servers (observability, storage, backupdr) under the same Apache-2.0 licence, runs over stdio via npx, and requires Node.js 20+ and an authenticated gcloud CLI. The repository states it is in preview and not an officially supported Google product.

“The gcloud Model Context Protocol (MCP) server enables AI assistants to easily interact with the Google Cloud environment using the gcloud CLI.”

01 / THE REASONING

Why this made the selection.

  • googleapis/gcloud-mcp completes the big-three cloud coverage alongside the catalogue's existing Azure and AWS records, published under Google's official API-tooling organisation.
  • The server wraps the gcloud CLI rather than raw REST, so it inherits the CLI's credential handling, and the monorepo hosts three further Google Cloud servers — observability, storage and backupdr — under the same Apache-2.0 licence.

02 / THE REVIEW RECORD

What we actually inspected.

Source review has boundaries.
A clear record is more useful than a “safe” badge.

Material inspected

  • README at pinned revision 238728f237ecb5f483199906b564a1767a0713f9: the server enables AI assistants to interact with the Google Cloud environment using the gcloud CLI; the monorepo hosts gcloud, observability, storage and backupdr MCP servers published as @google-cloud/* npm packages; prerequisites are Node.js 20+ and the gcloud CLI; setup via `npx @google-cloud/[PACKAGE_NAME] init --agent=gemini-cli` or a standard stdio config; a connection receipt shows `npx -y @google-cloud/gcloud-mcp (stdio) - Connected`; Important Notes state the repository is in preview, may see breaking changes, and provides a solution, not an officially supported Google product, not covered under Google Cloud Terms of Service.
  • packages/gcloud-mcp/package.json at the same revision: name @google-cloud/gcloud-mcp, version 0.5.3, Apache-2.0 licence, bin gcloud-mcp -> ./dist/bundle.js; packages/gcloud-mcp/src/index.ts exists at the revision; LICENSE at the revision is Apache 2.0.
  • packages/gcloud-mcp/src/index.ts at the same revision: default deny list, --config allow or deny file, single run_gcloud_command registration, stdio transport.

Our findings

  • The gcloud server is one of four Google Cloud MCP servers in the monorepo, each installable separately via npm.
  • Authentication is delegated to the local gcloud CLI session rather than a separate MCP credential.
  • The README’s tool table lists one gcloud tool, run_gcloud_command, which executes a gcloud command. packages/gcloud-mcp/src/index.ts registers only that tool and connects a StdioServerTransport.
  • index.ts denies these commands by default: compute start-iap-tunnel, compute connect-to-serial-port, compute tpus tpu-vm ssh, compute tpus queued-resources ssh, compute ssh, cloud-shell ssh, workstations ssh, app instances ssh, interactive, meta. A --config JSON file at an absolute path adds an allow list or a deny list, and the server exits if both are given.
  • Correction, 2026-10-13: the README prints the client entry as a bare "gcloud" fragment. configExample now holds that fragment as printed; the earlier value wrapped it in an mcpServers object the README does not show.

Not established by this review

  • The package was not installed and no Google Cloud project was connected.
  • run_gcloud_command and the --config allow and deny lists were not exercised.

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

Connect a server deliberately.

Upstream setup instructions ↗
  1. Install Node.js 20 or higher and the gcloud CLI, and authenticate with `gcloud auth login`.
  2. Add the configExample to the MCP client, or run `npx @google-cloud/gcloud-mcp init --agent=gemini-cli` for Gemini CLI or Gemini Code Assist.
  3. Ask the agent to describe a Google Cloud resource to verify the connection.

Before you start

  • Node.js version 20 or higher.
  • The gcloud CLI installed and authenticated against the target project.

Documented configuration example

Use the client and authentication context described in the setup guidance. Configuration formats vary between hosts.

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

04 / FOLLOW THE EVIDENCE

The source trail.

Our notes are separate from the original resource.
Check upstream before adopting a new version.

  1. https://github.com/googleapis/gcloud-mcp/blob/238728f237ecb5f483199906b564a1767a0713f9/README.md

    Supports: summary, upstreamDescription, descriptionSourceUrl, install, configExample, compatibility, limitations, transports, whySelected, access, Tool run_gcloud_command

  2. https://github.com/googleapis/gcloud-mcp/blob/238728f237ecb5f483199906b564a1767a0713f9/packages/gcloud-mcp/package.json

    Supports: repository, revision, language, license

  3. https://github.com/googleapis/gcloud-mcp/blob/238728f237ecb5f483199906b564a1767a0713f9/packages/gcloud-mcp/src/index.ts

    Supports: Default deny list, --config allow or deny file, run_gcloud_command registration, transports, limitations, access

Evidence & Ask