Skip to main content
Glama

Server Details

The Google Compute Engine MCP server is a fully-managed Model Context Protocol server that provides tools to manage Google Compute Engine resources through AI agents. It enables capabilities including instance management (creating, starting, stopping, resetting, listing), disk management, handling instance templates and group managers, viewing machine and accelerator types, managing images, and accessing reservation and commitment information. The server operates as a zero-deployment, enterprise-grade endpoint at https://compute.googleapis.com/mcp with built-in IAM-based security.

Status
Healthy
Last Tested
Transport
Streamable HTTP
URL

Glama MCP Gateway

Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.

MCP client
Glama
MCP server

Full call logging

Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.

Tool access control

Enable or disable individual tools per connector, so you decide what your agents can and cannot do.

Managed credentials

Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.

Usage analytics

See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.

100% free. Your data is private.
Tool DescriptionsA

Average 3.8/5 across 29 of 29 tools scored. Lowest: 3.2/5.

Server CoherenceA
Disambiguation5/5

Every tool targets a distinct resource and action. There is no overlap; for example, get_instance_basic_info and list_instances clearly differ in scope, and similar distinctions exist across all resource types.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case (e.g., create_instance, list_instances, get_disk_performance_config). No mixing of conventions or vague verbs observed.

Tool Count4/5

With 29 tools covering multiple GCE resource types, the count is slightly above the typical 3-15 range but still reasonable given the broad scope. Tools are not redundant and each serves a clear purpose.

Completeness2/5

The tool set is heavily read-only for many resources (disks, snapshots, images, reservations, commitments) and lacks update operations for instances (tags, metadata, etc.). Essential lifecycle actions like disk create/delete, instance update, or network management are missing, leaving significant gaps.

Discussions

No comments yet. Be the first to start the discussion!

Try in Browser

Your Connectors

Sign in to create a connector for this server.

Resources