Mcp

Google Compute Engine MCP

Official Google Cloud MCP server for Compute Engine — create / start / stop / delete / reset VM instances, list disks, snapshots, instance groups, templates, reservations, commitments, accelerator types, and zone operations. Hosted on the canonical compute.googleapis.com origin via Google's ESF.

Verified: 2026-05-13 (mcp-registry-ingest-2026-05-13+enrich-capability-skill)

When to use Google Compute Engine MCP

Choose if

You need an agent to manage Google Compute Engine VMs from the loop and prefer the official Google-hosted MCP over a third-party gcloud wrapper. Read-only tools (list / get) are safe to expose broadly; destructive tools should be human-gated. Live at compute.googleapis.com/mcp via Google's ESF — same trust surface as the rest of cloud.google.com.

Avoid if

Your agent only needs read-only inventory — use the GCE REST API or `gcloud` with limited IAM rather than expose write tools. Also avoid if you need Kubernetes (GKE), Cloud Run, or any non-Compute GCP service — those need separate MCPs. Authentication wiring isn't documented in the registry entry; expect to figure out OAuth or service-account JSON setup yourself.

Risk Flags

  • HIGH auth Production GCP endpoint — requires real Google Cloud credentials with Compute Engine IAM permissions. The MCP registry entry doesn't expose auth flow; users must wire OAuth or service-account credentials themselves. Misuse (or compromised key) can incur GCP spend.
  • HIGH runtime Tools include destructive operations (`create_instance`, `delete_instance`, `start_instance`, `stop_instance`, `reset_instance`) marked `destructiveHint: true` in their MCP annotations. Agents running this unsupervised can create real billable VMs or wipe production infrastructure. Gate behind human approval for non-read tools.
  • MEDIUM rate_limit Google Cloud per-project + per-region quotas apply. Bulk operations risk hitting `quotaExceeded` errors; the MCP doesn't auto-back-off.

Cost

Type: Usage based

Distribution

MCP Registry
com.googleapis.compute/mcp