Google Cloud CI/CD extension plugin
Extension for Gemini CLI and Claude Code: Cloud Run deploys, CI/CD pipelines, GCP Terraform and MCP for Cloud Build.
- 51 ★ on the repository
- Last commit
- Apache-2.0
Broad access
Why this level
- The agent deletes and creates cloud resources on your behalf, and a model mistake turns into extra spend.
- The deploy skill publishes code to services, so a secret left in the repository could reach a public bucket.
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add plugins/google-cloud-ci-cd-extensionDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- The agent deletes and creates cloud resources on your behalf, and a model mistake turns into extra spend.
- The deploy skill publishes code to services, so a secret left in the repository could reach a public bucket.
This is third-party code. Review the repository files before installing.
What it does
The extension automates deployment and CI/CD on Google Cloud through an agent. Four skills: `google-cicd-deploy` deploys a project to Cloud Run or Cloud Storage and scans for secrets first, `google-cicd-pipeline-design` drafts YAML for a secure pipeline, `google-cicd-terraform` prepares and fixes infrastructure using Cloud Foundation Fabric patterns, `google-cicd-release-orchestration` sets up Cloud Deploy releases with canary rollouts and rollbacks. A local MCP server `cicd-mcp-server` written in Go ships with it. Through it the agent works with Cloud Build, Artifact Registry, Cloud Deploy and Developer Connect using your Application Default Credentials. The extension installs in Gemini CLI, Claude Code and Antigravity.
Who it is for. Developers and DevOps engineers on Google Cloud who want to build pipelines, deploys and Terraform in a conversation with an agent.
Good fit when
- A static site goes to Cloud Storage after a secret scan of the code
- An app is deployed to Cloud Run without manual build setup
- A pipeline needs secure YAML with minimal service account rights
- GCP infrastructure is described in Terraform from recommended patterns
- Cloud Deploy releases run with a canary and automatic rollback
Not a fit when
- The project or cloud is production: the authors forbid using the extension on business-critical GCP projects
- You need another cloud provider: the extension works only with Google Cloud
- Your ADC credentials are broad and you are not ready to restrict them
Example request
Scan the project for secrets, then deploy it to Cloud Run in a test project and show the service link.Limitations
The authors call the project experimental and ask you not to use it in production or on business-critical GCP projects. You need the `gcloud` CLI, a Google Cloud project with Cloud Build, Artifact Registry, Cloud Run and other APIs enabled and configured Application Default Credentials. Gemini CLI must be version 0.15.0 or newer. The agent can be wrong and change resources, so review every command and configuration before running it. Pipelines created by the design skill run under a service account, so keep its rights minimal. Do not add untrusted files or emails to the context because indirect prompt injection is possible.
How to disable. Remove the extension with `gemini extensions uninstall` or disable the `cicd` plugin through `/plugin` in Claude Code. Delete cloud resources, pipelines and service accounts separately in the Google Cloud console.
FAQ
How do I install the extension in Gemini CLI?
Run `gemini extensions install https://github.com/gemini-cli-extensions/cicd` on Gemini CLI 0.15.0 or newer. For a development build add `--ref=nightly --pre-release`.
How do I install it in Claude Code?
Add the marketplace with `claude plugin marketplace add https://github.com/gemini-cli-extensions/cicd.git#v0.2.2`, then run `claude plugin install cicd`.
What rights does the agent get?
The rights of your Application Default Credentials: through the MCP server the agent reads and changes Google Cloud data. Use minimal rights for ADC and service accounts.
What does `google-cicd-deploy` do?
It analyses the project and deploys it to Cloud Run for dynamic apps or Cloud Storage for static sites. The skill scans code for secrets before deploying.
Is Antigravity supported?
Yes, the plugin with the MCP server and four skills installs with `agy plugin install cicd@antigravity-plugins-official` or through the settings UI.
Discussion
No questions or reviews yet.
Related
PluginsGoogle Cloud's MCP server and Gemini CLI extension for GKE clusters: resources, logs, deploys, costs and upgrade risks
Google's plugin with six skills and two MCP servers for Cloud Storage: buckets, objects, access errors and security audits
Google's MCP server for deploying apps to Cloud Run from an agent, with service listing and log reading
Google Cloud MCP servers: gcloud commands, logs and metrics, Cloud Storage and Backup and DR
Run Gemini CLI
run-gemini-cli
Google's official action for GitHub Actions: runs Gemini CLI in a repository to review pull requests, triage issues and edit code
Diffinery plugins connect Claude Code and Codex to self-hosted Git, pull requests and CI on Cloudflare through an MCP server
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| Google Cloud CI/CD extension (this card) | no | 51 | ||
| Cloud Run MCP server | yes | OAuth | 639 | a Google MCP server for Cloud Run deploys only; this extension adds pipelines, Terraform and Cloud Deploy |
| gcloud MCP Server | yes | OAuth | 949 | a server set with gcloud commands, logs and metrics; this one has CI/CD and release design skills |
README in short
The README lists features, prerequisites, installation for Gemini CLI, Claude Code and Antigravity, MCP tools and a detailed security warning. The author marks the project experimental.