---
title: "Kiwi for Google Cloud"
description: "Have the agent on a Kiwi step deploy a container to Cloud Run and read the service back, through Google Cloud's remote MCP server for Cloud Run."
canonical: "https://kiwiflow.io/integrations/google-cloud"
---

# Kiwi for Google Cloud

Have the agent on a Kiwi step deploy a container to Cloud Run and read the service back, through Google Cloud's remote MCP server for Cloud Run.

- Your agent works in Google Cloud through its own connection. Kiwi does not call Google Cloud and never holds its credentials.
- A workflow skill can list Google Cloud among the tools it requires. When you supply your agent's available tools to a skill check and Google Cloud is not among them, the check reports `SK15-UNSUPPORTED-TOOL`.
- A project Admin can add links to Google Cloud, with notes, under Connections and bind them to the steps that use them. The agent reads them with `list_connections`.
- The agent can report the tools and plugins it ran with, including its Google Cloud connection, with `report_configuration`.
- The agent submits links to its work in Google Cloud as the step's outputs. People review them, and sign-off stays with the people your workflow names.

## What your agent can do in Google Cloud

- List the Cloud Run services in a project and read the configuration of one.
- Deploy a Cloud Run service from a container image.
- Deploy a service from a source archive or from file contents the agent supplies.
- Review the server's calls afterwards in Cloud Audit Logs.

## Set up

### 1. Connect your agent to Kiwi

Add Kiwi's hosted MCP server, `https://kiwiflow.io/mcp`, to your coding agent.

- [Coding agents](https://kiwiflow.io/integrations#agent)
- [Quickstart](https://docs.kiwiflow.io/quickstart#connect-your-agent)

### 2. Connect your agent to Google Cloud

Add the Google Cloud MCP server to your agent with this URL. The credentials stay with your agent.

```
https://run.googleapis.com/mcp
```

- [Google Cloud documentation](https://docs.cloud.google.com/run/docs/use-cloud-run-mcp)

### 3. Example skill

Publish instructions like these as a workflow skill that lists Google Cloud among its required tools.

```
Take the project, region and image digest from the run's inputs.
Deploy the image to the Cloud Run service named in the assignment, which is
a staging service, and read the service back to check the new revision.
Submit the revision name and the service URL as the step's outputs.
A deploy to the production service needs a go-ahead from the run's Owner.
If the deploy fails twice, stop and report a blocker with the error.
```

## More deployment and hosting integrations

- [Kiwi for AWS](https://kiwiflow.io/integrations/aws.md): Have the agent on a Kiwi step call AWS APIs under the IAM permissions it signs in with and read the AWS documentation, through the AWS MCP Server.
- [Kiwi for Microsoft Azure](https://kiwiflow.io/integrations/microsoft-azure.md): Have the agent on a Kiwi step check a Microsoft Azure App Service app and query Azure Monitor, through the Azure MCP Server.
- [Kiwi for Cloudflare](https://kiwiflow.io/integrations/cloudflare.md): Have the agent on a Kiwi step read and change Workers, DNS records and other Cloudflare settings, through the Cloudflare API MCP server.
- [Kiwi for Vercel](https://kiwiflow.io/integrations/vercel.md): Have the agent on a Kiwi step check a Vercel preview deployment and read its runtime logs, through Vercel's MCP server.
- [Kiwi for DigitalOcean](https://kiwiflow.io/integrations/digitalocean.md): Have the agent on a Kiwi step update a DigitalOcean App Platform app and follow its deployment, through DigitalOcean's MCP server.
- [Kiwi for Supabase](https://kiwiflow.io/integrations/supabase.md): Have the agent on a Kiwi step apply a database migration to a Supabase project and run the advisors afterwards, through Supabase's MCP server.
- [Kiwi for Netlify](https://kiwiflow.io/integrations/netlify.md): Have the agent on a Kiwi step deploy a site to Netlify and set its environment variables, through Netlify's MCP server.
- [Kiwi for Heroku](https://kiwiflow.io/integrations/heroku.md): Have the agent on a Kiwi step check a Heroku app's dynos, logs and Postgres database, through Heroku's MCP server.
- [Kiwi for Fly.io](https://kiwiflow.io/integrations/fly-io.md): Have the agent on a Kiwi step check a Fly.io app's status, Machines and logs, through the MCP server in Fly.io's flyctl CLI.
- [Kiwi for Render](https://kiwiflow.io/integrations/render.md): Have the agent on a Kiwi step trigger a Render deploy, filter the service's logs and read its metrics, through Render's MCP server.
- [Kiwi for Railway](https://kiwiflow.io/integrations/railway.md): Have the agent on a Kiwi step redeploy a Railway service in a non-production environment, through Railway's MCP server.

- [Get started](https://kiwiflow.io/get-started)
- [Read the setup guide](https://docs.kiwiflow.io/other-tools)