Enterprise Connectors
Google Kubernetes Engine logo. Google Kubernetes Engine MCP server connector.

Google Kubernetes Engine MCP Server

Official Google Kubernetes Engine MCP server

Tools
23
Last Updated
Jun 14, 2026
Category
all
Enterprise-grade security
SSO & authentication ready
Full governance & audit logs

What is the Google Kubernetes Engine MCP Server?

The Google Kubernetes Engine MCP server gives AI agents structured, permission-aware access to Google Kubernetes Engine through the Model Context Protocol. With 23 pre-built actions, agents can read, create, and update Google Kubernetes Engine data on behalf of authorized users.

Willow ships the Google Kubernetes Engine MCP server as part of an enterprise control plane. Every call runs behind SSO (Okta, Azure AD), enforces RBAC and least-privilege at runtime, writes to a full audit trail, and integrates with Splunk and Loki for SIEM visibility. Connect from Claude Desktop, Claude Code, Cursor, ChatGPT, VS Code, n8n, or any custom agent. Install once, distribute org-wide, and see exactly how Google Kubernetes Engine is being used by every AI agent in your stack.

Tools

list_k8s_api_resources

Retrieves the available API groups and resources from a Kubernetes cluster. This is similar to running `kubectl api-resources`.

check_k8s_auth

Checks whether an action is allowed on a Kubernetes resource. This is similar to running `kubectl auth can-i`.

describe_k8s_resource

Shows the details of a specific Kubernetes resource. This is similar to running `kubectl describe`.

list_k8s_events

Retrieves events from a Kubernetes cluster. This is similar to running `kubectl events`.

get_k8s_resource

Gets one or more Kubernetes resources from a cluster. Resources can be filtered by type, name, namespace, and label selectors. Returns the resources in YAML format. This is similar to running `kubectl get`.

get_k8s_cluster_info

Gets cluster endpoint information. This is similar to running `kubectl cluster-info`.

get_k8s_version

Retrieves Kubernetes client and server versions for a given cluster. This is similar to running `kubectl version`.

get_k8s_rollout_status

Checks the current rollout status of a Kubernetes resource. This is similar to running `kubectl rollout status`.

list_clusters

Lists GKE clusters in a given project and location. Location can be a region, zone, or '-' for all locations.

create_cluster

Creates a new GKE cluster in a given project and location. It's recommended to read the [GKE documentation](https://docs.cloud.google.com/kubernetes-engine/docs/concepts/configuration-overview) to understand cluster configuration options. Cluster creation will default to Autopilot mode, as recommended by GKE best practices. If the user explicitly wants to create a Standard cluster, you need to set autopilot.enabled=false in the cluster configuration. This is similar to running `gcloud container clusters create-auto` or `gcloud container clusters create`.
1–10 of 23 tools

Customize Tools

Edit descriptions, modify arguments, select tools, or add new ones

Edit descriptions
Change arguments
Select tools
Create New

Set Up Your Google Kubernetes Engine MCP Server in Minutes

Add the following configuration to your MCP client. Authentication is handled via OAuth. Compatible with Claude Desktop, Claude Code, Cursor, ChatGPT, VS Code, n8n, and any MCP-compatible agent.

Claude Desktop

claude_desktop_config.json
{
  "mcpServers": {
    "willow-google-kubernetes-engine": {
      "type": "http",
      "url": "https://<org>.mcp-s.com/mcp/mcp/google-kubernetes-engine"
    }
  }
}

Cursor

.cursor/mcp.json
{
  "mcpServers": {
    "willow-google-kubernetes-engine": {
      "type": "http",
      "url": "https://<org>.mcp-s.com/mcp/mcp/google-kubernetes-engine"
    }
  }
}

Claude Code

CLI
claude mcp add willow-google-kubernetes-engine --transport http https://<org>.mcp-s.com/mcp/mcp/google-kubernetes-engine

n8n

HTTP Request Node
{
  "url": "https://<org>.mcp-s.com/mcp/mcp/google-kubernetes-engine",
  "method": "POST"
}

Or click "Install with Willow" above to set up automatically with SSO and RBAC preconfigured.

Enterprise Governance for Google Kubernetes Engine

Willow adds the layer Google Kubernetes Engine and every other SaaS doesn't ship out of the box: every call runs behind SSO (Okta, Azure AD), enforces RBAC and least-privilege at runtime, writes to full audit logs, and detects shadow AI usage across your stack. One MCP gateway. Any agent. Every tool.

Google Kubernetes Engine MCP Server FAQ

What is the Google Kubernetes Engine MCP server?

The Google Kubernetes Engine MCP server is a Model Context Protocol implementation that lets AI agents like Claude, Cursor, and ChatGPT read and write Google Kubernetes Engine data through a standardized interface. Willow hosts and governs this server so enterprises can roll it out without a security review backlog.

How is Willow's Google Kubernetes Engine MCP server different from the official one?

The official Google Kubernetes Engine MCP server is scoped to a single user's account and does not include enterprise governance. Willow's version adds SSO, RBAC, audit logging, shadow AI detection, and centralized control over which actions agents can take across the entire org.

Which AI clients work with the Google Kubernetes Engine MCP server?

Claude Desktop, Claude Code, Cursor, ChatGPT, VS Code with MCP support, n8n, and any custom agent built with OpenAI Agents SDK, LangChain, Vercel AI SDK, or Anthropic SDK.

Is the Google Kubernetes Engine MCP server secure? How does Willow handle authentication?

Every call runs behind your existing SSO (Okta, Azure AD). Per-user OAuth scopes the agent to exactly what that user can do in Google Kubernetes Engine, nothing more. No credentials reach the LLM. Every action writes to an audit trail.

Can I limit which Google Kubernetes Engine actions agents can take?

Yes. Willow lets you scope agents to specific actions, specific projects, or specific environments. Toggle actions on or off in the dashboard, or enforce policy via infrastructure-as-code through GitHub.

How do I detect shadow Google Kubernetes Engine MCP servers in my org?

Willow's browser extension and discovery service surface unmanaged MCP servers, skills, and AI agents across the org. If a developer installed an unapproved Google Kubernetes Engine MCP locally, you'll see it.

What does the Google Kubernetes Engine MCP server cost?

Pricing depends on org size and deployment model (SaaS, dedicated cloud, self-host). See withwillow.ai/pricing or contact sales for a quote.

How do I install the Google Kubernetes Engine MCP server with Willow?

Install via the Willow Connect Panel in one click, or paste the JSON snippet above into your Claude Desktop, Cursor, or Claude Code config. SSO and RBAC inherit from your existing Willow setup.

Compare Willow MCP Gateway

See how Willow stacks up against other MCP platforms on governance, security, and enterprise readiness.

Your agents are already in the wild.

Give them a Basecamp. Go from AI chaos to AI work, in minutes.

Google Kubernetes Engine MCP Server | Willow