Skip to content

google/google-cloud-developer

v1.1.4Apache-2.0

Google Cloud guidance for coding agents: first-project onboarding, authentication and credential selection, and safety-critical validation for gcloud CLI commands. Includes the Google Developer Knowledge MCP server for grounded, up-to-date Google Cloud documentation.

google-cloud-developer plugin

The google-cloud-developer plugin equips AI coding agents with foundational skills, safety guardrails, and live documentation grounding for building on Google Cloud.

Built on the open Agent Plugins specification, this plugin bundles curated Agent Skills, routing rules, and configuration for the Developer Knowledge MCP server into a single portable package.


Installation

Antigravity CLI

  1. Install the plugin directly via the CLI using its path in the Google Agent Skills repository:

    agy plugin install https://github.com/google/skills/plugins/cloud/google-cloud-developer
    
  2. Enable the Developer Knowledge API in your Google Cloud project by using the gcloud CLI:

    gcloud services enable developerknowledge.googleapis.com --project=<YOUR_PROJECT_ID>
    

Claude Code

  1. Add the Google plugins marketplace, then install the plugin:

    claude plugin marketplace add google/skills
    claude plugin install google-cloud-developer@google-plugins
    
  2. Enable the Developer Knowledge API in your Google Cloud project by using the gcloud CLI:

    gcloud services enable developerknowledge.googleapis.com --project=<YOUR_PROJECT_ID>
    
  3. Create an API key for the Developer Knowledge API by following the instructions Create and secure the API key. Save the key you create in a secure location.

  4. Export the API key to your environment before starting Claude Code:

    export DEVELOPERKNOWLEDGE_API_KEY=<YOUR_API_KEY>
    

    Note

    The DEVELOPERKNOWLEDGE_API_KEY environment variable needs to be set in the environment before you start Claude Code. You may consider adding this export to your shell's startup script (e.g. .bashrc, .zshrc) for convenience.

Codex CLI

  1. Add the Google plugins marketplace, then install the plugin:

    codex plugin marketplace add google/skills
    codex plugin add google-cloud-developer@google-plugins
    
  2. Enable the Developer Knowledge API in your Google Cloud project by using the gcloud CLI:

    gcloud services enable developerknowledge.googleapis.com --project=<YOUR_PROJECT_ID>
    
  3. Create an API key for the Developer Knowledge API by following the instructions Create and secure the API key. Save the key you create in a secure location.

  4. Enable authenticated access to the Developer Knowledge MCP server by updating ~/.codex/config.toml (or your project's .codex/config.toml) to include the following lines:

    [mcp_servers.developer-knowledge]
      url = "https://developerknowledge.googleapis.com/mcp"
      env_http_headers = { "X-Goog-Api-Key" = "DEVELOPERKNOWLEDGE_API_KEY" }
    
  5. Export the API key to your environment before starting Codex:

    export DEVELOPERKNOWLEDGE_API_KEY=<YOUR_API_KEY>
    

    Note

    The DEVELOPERKNOWLEDGE_API_KEY environment variable needs to be set in the environment before you start Codex. You may consider adding this export to your shell's startup script (e.g. .bashrc, .zshrc) for convenience.

    Note

    Note: After you change the configuration, the server may show a not logged in status. This is expected and won't affect your access.


What's Included

Bundled Skills

MCP Server

Routing Rules

  • google-cloud-discovery.md: Always-on routing map that guides the agent to discover and suggest deeper product-specific skills (such as gke-*, agent-platform-*, google-cloud-waf-*, and <product>-basics) when a task requires specialized domain knowledge beyond the foundational bundle.

Plugin in Action

To see how this plugin works, consider a situation where you're bootstrapping a new project as part of working on a script. With the google-cloud-developer plugin installed, you can prompt your agent:

I'm brand new to this platform, and I need to get an account and a first project with billing set up. Then, I need my local machine authenticated so a script that I'm writing can call the APIs as a service identity instead of as me.

  1. Environment awareness: The agent silently runs background checks against your live environment for prerequisites like CLI availability and potential existing projects or organizations.

  2. Review: The agent considers IAM best practices to avoid risks that might be assumed as part of the prompt, like accidental key leaks or git commits.

  3. Interaction with guardrails: The agent outlines a workflow roadmap and offers to act on those steps before modifying any resources.