gcloud MCP Server: Setup for Claude Desktop, Cursor and Other Apps
Lets Claude, Cursor and Gemini CLI run Google Cloud commands for you, so you describe what you want instead of typing gcloud flags.
This is Google's own server for the gcloud command line tool. Your assistant turns a request such as "list my stopped VMs" into a gcloud command and runs it on your computer. It uses the Google account that gcloud is already signed in to, so it can do anything that account can do. You need the gcloud CLI installed and Node.js 20 or newer.
Good for
- Cloud engineers who want to describe Google Cloud tasks in plain words
- Team members who do not know gcloud flags by heart
- Gemini CLI and Claude users who already work in Google Cloud
Works in
12 should work
Tap an app to see how to set it up and any known problems.
Supports local MCP servers.
Supports local MCP servers.
Supports local MCP servers.
Supports local MCP servers.
Supports local MCP servers.
Supports local MCP servers.
Supports local MCP servers.
Supports local MCP servers.
Supports local MCP servers.
Supports local MCP servers.
Supports local MCP servers.
Supports local MCP servers.
Client does not support this transport.
Client does not support this transport.
Install gcloud MCP
Claude Code
- 1
Copy this prompt.
Add the gcloud MCP server to Claude Code. Run this command: claude mcp add gcloud -- npx -y @google-cloud/gcloud-mcp Then check that it loaded and tell me if I need to sign in or restart.
- 2
Paste it into Claude Code. It shows the change and asks before running it.
Requires Node.js 20+, gcloud CLI, signed in.
Read-only mode: Add the config flag with the absolute path of a file that allows only read commands, for example {"allow": ["compute instances list"]}.
Install the gcloud CLI and sign in to it before you add this. The README also offers a one-step setup for Gemini CLI that installs it as an extension. To limit commands, add the config flag with the absolute path of an allow or deny file after the package name in the arguments.
Built from the package data we hold. Not yet tested by us.
Tools
Runs one Google Cloud gcloud command and returns the result
Runs a single gcloud command with the arguments the assistant chooses, using whichever Google account gcloud is signed in to. A few commands are always blocked, including SSH sessions and interactive mode, and you can add your own allow or deny list.
Try: “List my Compute Engine instances in us-central1 and show which are stopped.”
Delete ·
run_gcloud_command
Read from the source code
Permissions
high risk · 3 things to watch
High risk
The assistant can run almost any gcloud command as your signed-in account, which includes creating and deleting cloud resources. Sign gcloud in as a service account with a limited role, or set an allow list so only the commands you name can run.
What it can do
- Read your data
- Create and change things
- Delete things
- Read-only modeHow to turn it on
Watch out for
It can create and delete Google Cloud resources
The one tool passes any gcloud command to the CLI, so its power equals your account. Use a limited service account or an allow list. github.com
Only a few commands are blocked by default
The fixed deny list covers SSH, serial ports, interactive mode and similar commands, not destructive ones. Add your own deny entries such as instance deletes. github.com
The allow or deny list needs an absolute path
The config file path must be absolute, and the file can hold either an allow list or a deny list, not both. github.com
Security advisories
No published security advisories as of Nov 1, 2026.
Technical details
| Turning on read-only | Pass a config file with an allow list that names only read commands, for example "compute instances list". A fixed default deny list always applies, and you can also impersonate a service account with a view-only role. |
|---|---|
| Talks to | Google Cloud, through the gcloud CLI on your machine |
| Sign-in and keys | No key of its own. It uses the account gcloud is signed in to on your machine. |
Questions
Is the gcloud MCP server official?
Yes. Google publishes it from its googleapis GitHub organization, under the Apache 2.0 license.
Do I need the gcloud CLI?
Yes. The server runs your installed gcloud CLI, and you need Node.js 20 or newer. Sign in with gcloud first so the commands have an account to use.
Can I limit what it can do?
Yes. Point it at a config file with either an allow list or a deny list of commands. For stronger limits, sign in as a service account with a narrow role through impersonation, as the README advises.
Can it delete my cloud resources?
Yes, if your account can. A short default deny list blocks SSH and interactive commands, not deletes, so add a deny or allow list if that worries you.
Which apps does it work with?
The README gives setup for Gemini CLI, Claude Desktop, Cline, Cursor and VS Code. Use the install box above for yours.
Is it the same as the other Google Cloud MCP servers?
No. This one runs gcloud commands. The same repository also holds separate servers for Cloud Storage, observability and backup.
Information
updated Nov 2, 2026
- Publisher
- Official
- Package
@google-cloud/gcloud-mcp- Registry
- npm
- Transport
- stdio
- Auth
- None
- Version
- 0.5.3
- License
- Apache-2.0
- Last commit
- Oct 17, 2026
- Open issues
- 33
Sources
Docs, issue trackers and discussions this page is built from. Issues, quotes and findings above link to their own source.
Show all 3Hide
- github.com · github.com
- github.com · github.com
- github.com · github.com