Google Cloud gcloud MCP server from googleapis that lets Claude run approved gcloud CLI commands with allowlist and denylist controls for cloud resource inspection, automation, and operations.
Open the source and read safety notes before installing.
Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.
Decision playbook
Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.
0
63
—
No baseline selected
No major trust-signal divergence detected in the current selection.
Confirm ownership and provenance before trusting install instructions.
Source link availableRequired
Open the canonical repository and verify ownership.
Source provenance statusRequired
Marked as source-backed.
Metadata reviewed
No reviewed flag detected in metadata.
Validate risk disclosures before installation or API wiring.
Safety notes presentRequired
Review the listed safety guidance before running commands.
Privacy notes presentRequired
Review data handling notes before connecting accounts or secrets.
Trust level risk gateRequired
Trust level does not block evaluation.
Check package metadata and artifact integrity signals.
Install payload available
Install or copy payload is available for review.
Package verification flag
No package verification flag provided.
Checksum metadata
No checksum provided for downloaded artifact.
Use compare context to validate trade-offs before adoption.
Compare tray has multiple entries
Add at least one more entry to compare trust differences.
Baseline comparison available
No baseline peer selected yet.
Diverging trust signals identified
No major trust-signal divergence found.
Setup at a glance
Copy-ready — paste the snippet to get started.
Adoption plan
Current risk score 24/100. Use staged verification before broader rollout.
Validate source and review signals before any execution.
Confirm source provenanceRequired
Source URL/provenance metadata is present.
Confirm metadata review state
No review metadata found; increase manual validation.
Verify install payload
Install/config payload exists and can be inspected.
Confirm safety, privacy, and package integrity signals.
Review safety notesRequired
Safety notes are present.
Review privacy notesRequired
Privacy notes are present.
Verify package integrity metadata
No package verification/checksum metadata.
Adopt in controlled steps based on the selected plan.
Run in isolated sandbox firstRequired
Use a constrained sandbox and observe behavior across multiple tasks.
Roll out graduallyRequired
Roll out to a small cohort before wider usage.
Set monitoring and fallback
Define rollback path and monitor errors after adoption.
Evidence readiness
Missing required evidence: Metadata review. Risk score 31.
Source repository/provenance is listed.
Required in this preset
Review metadata is missing.
Required in this preset
Safety notes are present.
Required in this preset
Privacy notes are present.
Optional in this preset
Package integrity metadata is missing.
Optional in this preset
Install payload is available.
Required in this preset
Required gaps: Metadata review
Decision timeline
Blocking gaps: Check metadata review status. Risk 28.
triage
Source/provenance metadata is available.
triage
Review metadata is missing.
verify
Safety notes are available.
verify
Privacy notes are available.
verify
Package integrity metadata is missing.
rollout
Install payload is available.
Blockers: Check metadata review status
Prerequisite readiness
5 prerequisites to line up before setup. Have accounts and credentials ready first. Includes a review or approval gate.
Safety & privacy surface
5 safety and 4 privacy notes across 4 risk areas. Review closely: credentials & tokens, permissions & scopes, third-party handling.
Disclosure: Preview Google Cloud MCP server hosted in the googleapis organization. The upstream README says the repository provides a solution, is not an officially supported Google product, is not covered under Google Cloud Terms of Service, and may change as MCP and related SDKs evolve.
{
"mcpServers": {
"gcloud": {
"command": "npx",
"args": ["-y", "@google-cloud/gcloud-mcp"]
}
}
}gcloud MCP Server is a preview Google Cloud MCP server from the googleapis
organization. It lets Claude-compatible MCP clients execute approved gcloud
CLI commands through a single run_gcloud_command tool, with support for
command allowlists and denylists.
Use it when an agent needs Google Cloud context or can help automate a narrow, reviewed cloud workflow. Because gcloud commands can affect real infrastructure, IAM, data, deployments, and billing, configure it with least-privilege credentials and explicit command controls.
These sources were reviewed on 2026-06-06. Prefer the live repository,
package README, npm registry metadata, license, package manifest, server
implementation, run_gcloud_command tool, access-control implementation,
gcloud executor, and security policy for current installation and behavior
details.
gcloud command at a time through the MCP tool.npx -y @google-cloud/gcloud-mcp.init command.Install Node.js 20 or newer and the Google Cloud CLI, then authenticate gcloud with a user or service-account impersonation path scoped to the intended work.
Add the server to an MCP client:
{
"mcpServers": {
"gcloud": {
"command": "npx",
"args": ["-y", "@google-cloud/gcloud-mcp"]
}
}
}
Claude Code users can add it with:
claude mcp add gcloud -- npx -y @google-cloud/gcloud-mcp
Review allowlist and denylist configuration before using the server against shared or production Google Cloud projects.
gcloud MCP Server is active cloud automation. Even with its default denylist, commands that remain permitted can change infrastructure, expose data, affect availability, alter IAM, trigger spend, deploy code, or delete resources if the active account has those permissions.
Use service-account impersonation and least-privilege roles rather than a broad personal account. Prefer allowlists for routine workflows, keep production projects separate from experiments, and require human approval for commands that can mutate resources or reveal sensitive data.
Do not paste credentials, access tokens, private project details, or secret values into prompts. Treat gcloud command output as sensitive because it can include infrastructure topology, IAM bindings, resource names, logs, and other operational context.
Existing entries cover BigQuery, Firebase, Google Analytics, Google Workspace,
MCP Toolbox for Databases, and other cloud or database servers, but no gcloud
MCP Server entry, googleapis/gcloud-mcp, @google-cloud/gcloud-mcp, or
matching source URL was found in content/mcp.
Show that gcloud MCP Server is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.
[](https://heyclau.de/entry/mcp/gcloud-mcp-server)gcloud MCP Server side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.
| Field | Google Cloud gcloud MCP server from googleapis that lets Claude run approved gcloud CLI commands with allowlist and denylist controls for cloud resource inspection, automation, and operations. Open dossier | MCP server for Coolify infrastructure management, diagnostics, deployments, logs, projects, environments, applications, databases, services, env vars, storage, scheduled tasks, private keys, cloud tokens, teams, and docs search. Open dossier | Official Agentset MCP server that lets Claude retrieve cited knowledge-base results from an Agentset namespace through the `knowledge-base-retrieve` tool, with optional tenant scoping and custom tool descriptions. Open dossier | Unity MCP server, plugin, CLI, and skill generator for controlling Unity Editor and runtime projects from MCP clients through built-in game-dev tools. Open dossier |
|---|---|---|---|---|
| Next steps | ||||
| Trust | ||||
| Review status | Not reviewed | Not reviewed | Not reviewed | Not reviewed |
| Package trust | Package not verified | Package not verified | Package not verified | Package not verified |
| Source provenance | Source-backed | Source-backed | Source-backed | Source-backed |
| Submitter | oktofeesh1 | oktofeesh1 | oktofeesh1 | oktofeesh1 |
| Install risk | Review first | Review first | Review first | Review first |
| Notes | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ |
| Brand | ||||
| Category | mcp | mcp | mcp | mcp |
| Source | Source-backed | Source-backed | Source-backed | Source-backed |
| Author | Google APIs | Stuart Mason | Agentset | Ivan Murzak |
| Added | 2026-06-06 | 2026-06-06 | 2026-06-06 | 2026-06-06 |
| Platforms | ||||
| Harness | ||||
| Source repo | — | — | — | — |
| Safety notes | ✓gcloud MCP Server executes gcloud CLI commands with the permissions of the active gcloud account. Allowed commands can create, update, delete, deploy, scale, list, export, or configure Google Cloud resources depending on IAM permissions and selected services. The server blocks command substitution, pipes, redirection, SSH-style commands, interactive commands, and a default set of sensitive command prefixes, but allowed gcloud commands can still have real infrastructure, billing, IAM, and data impact. Use allowlists for narrow workflows and service account impersonation with limited roles when possible. Require human approval for IAM, billing, networking, firewall, storage, database, secret, deployment, delete, and production-impacting commands. | ✓Coolify MCP Server can start, stop, restart, redeploy, cancel deployments, update env vars, create or delete projects, environments, applications, databases, services, backups, storages, scheduled tasks, private keys, GitHub apps, and cloud tokens depending on API permissions. Batch tools such as `restart_project_apps`, `bulk_env_update`, `stop_all_apps`, and `redeploy_project` can affect multiple production services at once. Deployment, control, backup, storage, private key, cloud token, GitHub app, and scheduled-task operations should require explicit confirmation. Custom `--header` values may carry auth-proxy secrets; never let an agent invent, log, or modify them casually. Test on non-production projects or staging resources before allowing Claude to operate live Coolify infrastructure. | ✓The MCP server sends Claude's retrieval queries to the Agentset API using the configured API key and namespace. The `knowledge-base-retrieve` tool can return up to 100 results per call and can rerank results by relevance. Namespace and tenant selection control which indexed documents are searchable; review them before connecting a shared agent. API keys should be scoped, rotated, and stored only in the MCP server environment or a secret manager. Custom tool descriptions can influence when the model calls the retrieval tool, so review them before use in production workflows. | ✓AI Game Developer can create, move, copy, modify, and delete Unity assets, scenes, GameObjects, components, scripts, packages, and generated project files. Tools include dynamic C# script execution, C# reflection method lookup and calls, package installation/removal, Unity test execution, editor state changes, play mode control, screenshots, and profiler access. The MCP server supports streamable HTTP and stdio; HTTP deployments should require a bearer token and stay bound to trusted interfaces. Server variables include optional authorization and webhook settings; webhook endpoints can receive tool, prompt, resource, connection, and authorization events. Unity runtime connections can expose compiled game state or in-game behavior to an MCP client, not just editor-only project data. Use source control, backups, tool filtering, and explicit review before allowing destructive tools such as asset deletion, package removal, script execution, or reflection calls. |
| Privacy notes | ✓gcloud output can reveal project IDs, resource names, regions, IAM bindings, service accounts, logs, errors, labels, metadata, URLs, secrets references, billing context, and infrastructure topology. Authentication state, ADC files, service account impersonation details, access tokens, project IDs, and local gcloud configuration should stay out of prompts and repository files. Command output may be retained by the MCP client, model provider, terminal logs, shell history, and chat transcripts. Avoid broad listing or export commands against production projects unless data handling and retention have been reviewed. | ✓Coolify access tokens, base URLs, custom headers, application UUIDs, server IPs, domains, logs, env vars, deployment logs, private keys, cloud-provider tokens, GitHub app data, team membership, backups, database metadata, and service configuration can be exposed to the MCP client. Application and deployment logs may contain secrets, customer data, build output, container metadata, private repository details, and runtime errors. Environment variable and cloud-token tools can reveal or mutate sensitive infrastructure credentials. Documentation search is local to the server, but Coolify API calls contact the configured Coolify instance. Keep tokens and auth-proxy headers in local MCP client configuration only, and avoid sharing transcripts that include infrastructure identifiers or logs. | ✓Retrieved chunks can include private documents, product specs, policies, support content, internal procedures, historical project information, or customer-specific data. Retrieval queries, namespace IDs, tenant IDs, document chunks, citations, and tool outputs may be visible to the MCP client, model provider, Agentset logs, and application telemetry. Tenant IDs are useful for data segregation, but incorrect tenant or namespace configuration can expose the wrong knowledge base. Do not paste API keys, namespace IDs, tenant IDs, or retrieved private chunks into shared issue reports, screenshots, or repository files. | ✓Tool calls may expose Unity project paths, asset names, scene hierarchy, serialized object data, scripts, logs, screenshots, profiler metrics, test output, package metadata, and runtime state. MCP config files and Unity plugin config can contain server URLs, connection modes, bearer tokens, authorization settings, enabled tool IDs, and cloud or local endpoint details. Optional webhooks can receive tool, prompt, resource, connection, authorization, and token-bearing request data. Screenshots from Game View, Scene View, cameras, or isolated GameObjects may include proprietary artwork, level design, UI, debug overlays, or unreleased game content. Generated skills and AI-client configuration files can reveal available tools, project structure, installed packages, and local workflow assumptions. |
| Prerequisites |
|
|
|
|
| Install | | | | |
| Config | | | | |
| Citations | ||||
| Claim | Unclaimed | Unclaimed | Unclaimed | Unclaimed |
Connect Claude to Coolify for supervised self-hosted PaaS diagnostics, deployments, resource management, logs, env vars, cloud tokens, and docs.
Query Agentset RAG namespaces from Claude through the official `@agentset/mcp` server.
Source-backed guides for putting this to work.
Loading live community signals…
A short, calm digest of reviewed Claude resources. Unsubscribe any time.