Google

Entreprise

Google Compute Engine MCP server
Google Compute Engine MCP server
Google Compute Engine MCP server
for Claude, ChatGPT, Cursor and your own agents
for Claude, ChatGPT, Cursor and your own agents
for Claude, ChatGPT, Cursor and your own agents

Q: What is the Google Compute Engine MCP server?

It’s a Model Context Protocol server that exposes the Google Compute Engine API operations as tools. Claude, ChatGPT, Cursor or your own agents call them through the Mindflow MCP Gateway.

Q: Do I need an official MCP server from the vendor?

No. Mindflow exposes Google Compute Engine as an MCP server through its native connector, which covers the full API and stays current when the API changes.

Q: Which AI clients can use Google Compute Engine through MCP?

MCP-compatible clients such as Claude, ChatGPT, Cursor, Codex or your own agents. They connect to one governed endpoint, so changing clients doesn’t mean rebuilding access.

Q: How do I control what AI agents can do in Google Compute Engine?

In the MCP Gateway, choose the tools each client may call. Allow reads, require human approval before sensitive writes and block the rest. Credentials stay in Mindflow and every call is logged.

Q: Can the same connection power automated workflows?

Yes. The same Google Compute Engine connector runs in Mindflow flows and AI··Agents, so one connection serves your AI clients and your automations.

Expose Google Compute Engine to Claude, ChatGPT, Cursor or your own agents as a governed MCP server, even if the vendor doesn’t ship one. Mindflow turns every API operation into an MCP tool and keeps the connector current when the API changes. The MCP Gateway sits between your AI clients and your data, with scoped access, human approval before sensitive writes and a record of every call.

Book a demo

See the integration

710

operation

available

Complete and up-to-date endpoint coverage by Mindflow.

Other services from this vendor:

Other services from this portfolio:

710

operation

available

Complete and up-to-date endpoint coverage by Mindflow.

Other services from this vendor:

Other services from this portfolio:

710

operation

available

Complete and up-to-date endpoint coverage by Mindflow.

Other services from this vendor:

Other services from this portfolio:

Our customers scale automation with security built in.

Read customer story

Tools exposed by this MCP server

Every Google Compute Engine operation, as an MCP tool

Each API operation becomes a tool your AI client can call. You decide which ones: allow reads, require approval before sensitive writes and block the rest. A few of the most used:

Google Compute Engine
Google Compute Engine
Attach disk to instance
Attach disk to instance
Google Compute Engine
Google Compute Engine
Delete disk
Delete disk
Google Compute Engine
Google Compute Engine
Delete instance
Delete instance
Google Compute Engine
Google Compute Engine
Detach disk from instance
Detach disk from instance
Google Compute Engine
Google Compute Engine
Get disk
Get disk
Google Compute Engine
Google Compute Engine
Get image
Get image
Google Compute Engine
Google Compute Engine
Get instance
Get instance
Google Compute Engine
Google Compute Engine
Insert disk
Insert disk
Google Compute Engine
Google Compute Engine
Insert instance
Insert instance
Google Compute Engine
Google Compute Engine
List disks
List disks
Google Compute Engine
Google Compute Engine
List firewalls
List firewalls
Google Compute Engine
Google Compute Engine
List images
List images
Google Compute Engine
Google Compute Engine
List instances
List instances
Google Compute Engine
Google Compute Engine
List networks
List networks
Google Compute Engine
Google Compute Engine
Start instance
Start instance
Google Compute Engine
Google Compute Engine
Stop instance
Stop instance

Google Compute Engine
Attach disk to instance
Google Compute Engine
Delete disk
Google Compute Engine
Delete instance
Google Compute Engine
Detach disk from instance
Google Compute Engine
Get disk
Google Compute Engine
Get image
Google Compute Engine
Get instance
Google Compute Engine
Insert disk
Google Compute Engine
Insert instance
Google Compute Engine
List disks
Google Compute Engine
List firewalls
Google Compute Engine
List images
Google Compute Engine
List instances
Google Compute Engine
List networks
Google Compute Engine
Start instance
Google Compute Engine
Stop instance

Google Compute Engine
Google Compute Engine
Stop instance
Stop instance
Google Compute Engine
Google Compute Engine
Start instance
Start instance
Google Compute Engine
Google Compute Engine
List networks
List networks
Google Compute Engine
Google Compute Engine
List instances
List instances
Google Compute Engine
Google Compute Engine
List images
List images
Google Compute Engine
Google Compute Engine
List firewalls
List firewalls
Google Compute Engine
Google Compute Engine
List disks
List disks
Google Compute Engine
Google Compute Engine
Insert instance
Insert instance
Google Compute Engine
Google Compute Engine
Insert disk
Insert disk
Google Compute Engine
Google Compute Engine
Get instance
Get instance
Google Compute Engine
Google Compute Engine
Get image
Get image
Google Compute Engine
Google Compute Engine
Get disk
Get disk
Google Compute Engine
Google Compute Engine
Detach disk from instance
Detach disk from instance
Google Compute Engine
Google Compute Engine
Delete instance
Delete instance
Google Compute Engine
Google Compute Engine
Delete disk
Delete disk
Google Compute Engine
Google Compute Engine
Attach disk to instance
Attach disk to instance

Google Compute Engine
Stop instance
Google Compute Engine
Start instance
Google Compute Engine
List networks
Google Compute Engine
List instances
Google Compute Engine
List images
Google Compute Engine
List firewalls
Google Compute Engine
List disks
Google Compute Engine
Insert instance
Google Compute Engine
Insert disk
Google Compute Engine
Get instance
Google Compute Engine
Get image
Google Compute Engine
Get disk
Google Compute Engine
Detach disk from instance
Google Compute Engine
Delete instance
Google Compute Engine
Delete disk
Google Compute Engine
Attach disk to instance

Connect Google Compute Engine to your AI client in three steps.

01 Connect the service

Add Google Compute Engine in Mindflow with its credentials. They stay in Mindflow and never reach the AI client.

02 Choose the tools

Pick the operations each AI client may call. Allow reads, require approval before sensitive writes and block the rest.

03 Connect your AI client

Point Claude, ChatGPT, Cursor or your own agent to your MCP Gateway endpoint, then check real calls in the audit log.

How the MCP Gateway governs every call

Use cases

What your AI agents can do with Google Compute Engine

AI clients

Mindflow

Google Compute Engine

→ Automate instance lifecycle management to reduce errors and manual effort by autonomously performing creations, updates, and deletions with precise API calls. → Streamline network management by automating forwarding rules and VPN gateway configurations, improving agility and security controls. → Facilitate dynamic resource allocation with automated disk migrations and label management to ensure optimized cloud infrastructure scaling.

Google

Entreprise

MCP servers:

BigQuery

BigQuery Connection

BigQuery Data Transfer

BigQuery Reservation

Cloud Deployment Manager

Entreprise Cloud Speech-to-Text

Entreprise Cloud Translation

Google Access Context Manager

Google Agent Registry

Google Anthos On-Prem

Google Apigee

Google Apigee Registry

Google App Engine Admin

Google Artifact Registry

Google Assured Workloads

Google Bare Metal Solution

Google Binary Authorization

Google Cloud Asset

Google Cloud Bigtable Admin

Google Cloud Billing

Google Cloud Billing Budget

Google Cloud Build

Google Cloud Composer

Google Cloud Data Catalog

Google

MCP servers:

Abusive Experience Report

AdMob

AdSense Management

Advisory Notifications

Air Quality

Analytics

Android Device Provisioning

Android Management

AppSheet

Area120 Tables

Authorized Buyers Marketplace

BeyondCorp

Campaign Manager 360

Chrome Policy

Chrome User Experience Report

Chrome Verified Access

Chronicle Security Search

Cloud Testing

Cloud Workstations

Contact Center AI Insights

Contact Center AI Platform

Data Pipelines

Developer Tools Custom Search

Dialogflow

Every call goes through one governed endpoint.

Your AI clients get access. You keep control.

Every call to Google Compute Engine goes through the Mindflow MCP Gateway. The same policies apply to every AI client: role-based access by team and environment, scoped credentials that never reach the client, human approval before sensitive writes, and a log of every call you can export to your SIEM.

Discover the MCP Gateway

Google Compute Engine MCP server

Live

RBAC · SecOps

Scoped credentials

Audit log

Attach disk to instance

Allowed

Delete disk

Allowed

Delete instance

Needs approval

Detach disk from instance

Blocked

Every call logged · Export to SIEM

Questions about the Google Compute Engine MCP server

Clear answers before you connect an AI client.

What is the Google Compute Engine MCP server?

Do I need an official MCP server from the vendor?

Which AI clients can use Google Compute Engine through MCP?

How do I control what AI agents can do in Google Compute Engine?

Can the same connection power automated workflows?

Questions about the Google Compute Engine MCP server

Clear answers before you connect an AI client.

What is the Google Compute Engine MCP server?

Do I need an official MCP server from the vendor?

Which AI clients can use Google Compute Engine through MCP?

How do I control what AI agents can do in Google Compute Engine?

Can the same connection power automated workflows?

Explore more MCP servers in our catalog of 4,000+ services.

SAP Concur Entry Attendee Associations MCP server

InfluxDB Cloud MCP server

Browse all 4,000+ MCP servers

Put this MCP server to work.

Bring one AI client and the tools it needs. We’ll show you the setup in Mindflow, from scoped access to the audit log.

Book a demo

Put this MCP server to work.

Bring one AI client and the tools it needs. We’ll show you the setup in Mindflow, from scoped access to the audit log.

Book a demo

Less busywork. More possibility.

Let your agents handle the routine. Make room for what comes next.

Let’s talk

Automation intelligence, delivered monthly.

Product releases, automation playbooks, and security research — straight to your inbox. No spam, unsubscribe anytime.

Less busywork. More possibility.

Let your agents handle the routine. Make room for what comes next.

Let’s talk

Automation intelligence, delivered monthly.

Product releases, automation playbooks, and security research — straight to your inbox. No spam, unsubscribe anytime.

Less busywork. More possibility.

Let your agents handle the routine. Make room for what comes next.

Let’s talk

Automation intelligence, delivered monthly.

Product releases, automation playbooks, and security research — straight to your inbox. No spam, unsubscribe anytime.

SOC Starter

Vulnerability Operations

DORA & NIS2

SOC Starter

SOC Starter

Vulnerability Operations

DORA & NIS2

SOC Starter

Every Google Compute Engine operation, as an MCP tool

Every Google Compute Engine operation, as an MCP tool

Connect Google Compute Engine to your AI client in three steps.

01

Connect the service

02

Choose the tools

03

Connect your AI client

What your AI agents can do with Google Compute Engine

What your AI agents can do with Google Compute Engine

More

More

Google

Google

Entreprise

Entreprise

MCP servers:

MCP servers:

More

More

Google

Google

MCP servers:

MCP servers:

Every call goes through one governed endpoint.

Every call goes through one governed endpoint.

Your AI clients get access. You keep control.

Your AI clients get access. You keep control.

Questions about the Google Compute Engine MCP server

Questions about the Google Compute Engine MCP server

Automation intelligence, delivered monthly.

Automation intelligence, delivered monthly.

Automation intelligence, delivered monthly.