Google Cloud Monitoring MCP Server

Gain visibility into the performance, availability, and health of your apps and infrastructure.

Tools

Last Updated

Jun 14, 2026

What is the Google Cloud Monitoring MCP Server?

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

Willow ships the Google Cloud Monitoring 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 Cloud Monitoring is being used by every AI agent in your stack.

Tools

list_timeseries

Lists time series data from the Google Cloud Monitoring API

query_range

Evaluate a PromQL query in a range of time

get_alert_policy

Use this as the primary tool to get information about a specific alerting policy. Alerting policies define the conditions under which you want to be notified about issues with your services. This is useful for understanding the details of a specific alert configuration.

list_alert_policies

Use this as the primary tool to list the alerting policies in a Google Cloud project. Alerting policies define the conditions under which you want to be notified about issues with your services. This is useful for understanding what alerts are currently configured.

get_alert

Use this as the primary tool to get information about a specific alert. An alert is the representation of a violation of an alert policy. This is useful for understanding the details of a specific alert.

list_alerts

Use this as the primary tool to list the alerts in a Google Cloud project. An alert is the representation of a violation of an alert policy. This is useful for understanding current and past violations of an alert policy.

list_metric_descriptors

Use this as the primary tool to discover the types of metrics available in a Google Cloud project. This is a good first step to understanding what data is available for monitoring and building dashboards or alerts.

list_dashboards

Use this as the primary tool to retrieve a list of existing custom monitoring dashboards in a Google Cloud project. Custom monitoring dashboards let users view and analyze data from different sources in the same context. This is useful for understanding what custom dashboards are currently configured and available in a given project.

get_dashboard

Use this as the primary tool to retrieve a single specific custom monitoring dashboard from a Google Cloud project using the resource name of the requested dashboard. Custom monitoring dashboards let users view and analyze data from different sources in the same context. This is often used as a follow on to list_dashboards to get full details on a specific dashboard.

Customize Tools

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

Set Up Your Google Cloud Monitoring 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-cloud-monitoring": {
      "type": "http",
      "url": "https://<org>.mcp-s.com/mcp/mcp/google-cloud-monitoring"
    }
  }
}

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "willow-google-cloud-monitoring": {
      "type": "http",
      "url": "https://<org>.mcp-s.com/mcp/mcp/google-cloud-monitoring"
    }
  }
}

Claude Code

CLI

claude mcp add willow-google-cloud-monitoring --transport http https://<org>.mcp-s.com/mcp/mcp/google-cloud-monitoring

n8n

HTTP Request Node

{
  "url": "https://<org>.mcp-s.com/mcp/mcp/google-cloud-monitoring",
  "method": "POST"
}

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

Enterprise Governance for Google Cloud Monitoring

Willow adds the layer Google Cloud Monitoring 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 Cloud Monitoring MCP Server FAQ

What is the Google Cloud Monitoring MCP server?

The Google Cloud Monitoring MCP server is a Model Context Protocol implementation that lets AI agents like Claude, Cursor, and ChatGPT read and write Google Cloud Monitoring 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 Cloud Monitoring MCP server different from the official one?

The official Google Cloud Monitoring 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 Cloud Monitoring 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 Cloud Monitoring 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 Cloud Monitoring, nothing more. No credentials reach the LLM. Every action writes to an audit trail.

Can I limit which Google Cloud Monitoring 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 Cloud Monitoring 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 Cloud Monitoring MCP locally, you'll see it.

What does the Google Cloud Monitoring 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 Cloud Monitoring 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.