cloud-build

This MCP server enables programmatic interactions with Google Cloud Build via a set of built-in tools. The server exposes a collection of capabilities for managing Cloud Build jobs: listing jobs for a project, retrieving details for a specific build, creating new builds from a provided build configuration, and retrying failed or cancelled builds. Each tool is exposed as a function you can call through an MCP client, using the corresponding parameters described in the Tools table. For example, use list_cloud_build_jobs with a project_id to retrieve all builds for that project, or get_cloud_build_job with project_id and build_id to inspect a particular build's details. The server relies on Google Application Default Credentials (ADC) to access Cloud Build, so ensure authentication is set up before running.

To use it with an agent, configure the mcpServers section in your settings to point to the cloudbuild server executable, then invoke the desired tools via your MCP client. The documentation also notes Gemini CLI integration for streamlined workflows.

Prerequisites:

• Go 1.21+
• Google Cloud project with Cloud Build API enabled
• Google Application Default Credentials (ADC) configured (e.g., via gcloud auth application-default login or setting GOOGLE_APPLICATION_CREDENTIALS)

Installation and setup:

1. Install Go (if not already installed):

   • macOS: brew install go
   • Windows: use the official installer from golang.org
   • Linux: sudo apt-get install -y golang

2. Obtain the source code (clone the MCP server repository): git clone https://github.com/jerop-cloud-build-mcp-server.git cd jerop-cloud-build-mcp-server

3. Build the server binary: go build -o cloud-build-mcp-server ./cmd

4. Run the server: ./cloud-build-mcp-server

5. Validate connectivity by calling the MCP tools (e.g., list_cloud_build_jobs) once the server is running. Ensure ADC credentials are correctly configured so the server can access Cloud Build.

Notes:

• If you deploy this in an environment without direct Go tooling, you can adapt the command to run via a container or a supervisor that restarts the binary when it exits.

Environment variables and configuration:

• GOOGLE_APPLICATION_CREDENTIALS: Path to the service account JSON used by Google Cloud APIs.
• CLOUDSDK_AUTH_CREDENTIAL_FILE_OVERRIDE: Optional override for the credentials file.
• Ensure Cloud Build API is enabled for the project used by the credentials.

Common issues:

• Authorization errors due to missing or invalid ADC credentials. Run gcloud auth application-default login or set GOOGLE_APPLICATION_CREDENTIALS.
• Network access issues when the server cannot reach Cloud Build endpoints. Check firewall/VPC settings and egress rules.
• If the server starts but MCP tools fail to authenticate, verify that the credentials file has the proper permissions and scope for Cloud Build.

Configuration tips:

• In agent settings, reference the server executable path exactly as you run it locally, e.g., /path/to/cloud-build-mcp-server.
• You can adapt the environment to run inside containerized environments by injecting the same env vars into the container runtime.