Google Cloud Run for cloud infrastructure
For cloud infrastructure, Google Cloud Run's server is the second of four picks, and it is the right one when your workloads run on Google Cloud's serverless platform. This official server lets an agent deploy code, list and inspect services, and read service logs on Cloud Run, so operating a deployment becomes a conversation rather than a console session.
It ranks second because its scope is Cloud Run specifically, not the whole of GCP. Within that scope it is direct and official, which is what earns it the spot.
How Google Cloud Run fits
deploy-file-contents ships code to a Cloud Run service by passing the file contents, the path used when the server runs remotely, and deploy-local-folder deploys a folder from disk when it runs locally. list-services enumerates the services in a project and region, get-service returns one service's configuration, and get-service-log pulls its logs and error messages, so an agent can deploy, inspect, and diagnose in one flow. When running locally, list-projects and create-project add project management, the latter attaching a new project to the first available billing account.
The ranking is honest about reach. This server covers Cloud Run, not Compute Engine, storage, or networking across GCP, so it is narrower than a full-cloud surface. AWS (AWS Labs) is the pick when your stack runs on AWS, Azure when it runs on Microsoft's cloud, and Cloudflare for the edge platform many teams pair alongside. Choose the Cloud Run server when serverless on Google Cloud is where your services actually live.
Tools you would use
| Tool | What it does |
|---|---|
| deploy-file-contents | Deploy code to a Cloud Run service by passing the file contents directly. Used when the server runs as a remote MCP server. |
| list-services | List the Cloud Run services in a given project and region. |
| get-service | Get the configuration details for a specific Cloud Run service. |
| get-service-log | Get logs and error messages for a specific Cloud Run service. |
| deploy-local-folder | Deploy a folder from the local filesystem to a Cloud Run service. Available when the server runs locally. |
| list-projects | List the available GCP projects. Available when the server runs locally. |
| create-project | Create a new GCP project and attach it to the first available billing account. Available when the server runs locally. |
FAQ
- Does this server manage all of Google Cloud or just Cloud Run?
- Cloud Run specifically. Its tools deploy code (deploy-file-contents, deploy-local-folder), list and inspect services (list-services, get-service), and read logs (get-service-log). It does not reach Compute Engine, storage, or networking, so it is a Cloud Run server rather than a full-GCP one.
- Can the agent deploy to Cloud Run with this server?
- Yes. deploy-file-contents ships code by file contents when the server runs remotely, and deploy-local-folder deploys a folder from disk when it runs locally. get-service-log then surfaces logs and errors so the agent can confirm the deploy worked.