# Google Cloud Monitoring MCP server > Query metrics, PromQL, alerts, alert policies and dashboards in Google Cloud Monitoring from your assistant. - Listing: https://mcp.tc/i/cloud-monitoring - Connect: use the server's own URL `https://monitoring.googleapis.com/mcp` (OAuth sign-in at the server); clients connect to it directly. The listing link is a page, not an MCP endpoint. - Type: remote (Streamable HTTP) - Auth: OAuth sign-in - Category: [Observability & Incidents](https://mcp.tc/c/observability) - Vendor: Google Cloud - Verified: yes, mcp.tc checked that this is the official server (https://mcp.tc/verify). It says who runs the server, not that it is safe. - Homepage: ## About Connects to the Cloud Monitoring API for a Google Cloud project. You can list time series, run PromQL range queries, discover metric descriptors, inspect alerts and alert policies, and read custom dashboards. All nine tools are read-only. Runs as a hosted streamable HTTP endpoint at monitoring.googleapis.com/mcp. Access is controlled by Google OAuth 2.0 and IAM permissions on the target project, so the signed-in account needs suitable Cloud Monitoring read roles. ## What it can do - List time series data with filters and aggregation - Run PromQL queries over a time range - List and inspect alert policies - List and inspect alerts raised by policy violations - Discover available metric descriptors in a project - List and read custom monitoring dashboards ## Tools (9) - `list_timeseries`: List time series data from the Cloud Monitoring API with filter and aggregation options. (read-only) - `query_range`: Evaluate a PromQL query over a time range. (read-only) - `get_alert_policy`: Get details of a specific alerting policy. (read-only) - `list_alert_policies`: List alerting policies in a Google Cloud project. (read-only) - `get_alert`: Get details of a specific alert, a violation of an alert policy. (read-only) - `list_alerts`: List current and past alerts in a project. (read-only) - `list_metric_descriptors`: Discover the metric types available in a project. (read-only) - `list_dashboards`: List custom monitoring dashboards in a project. (read-only) - `get_dashboard`: Retrieve a single custom monitoring dashboard by resource name. (read-only) ## Example prompts - "List the active alerts in my project my-prod-project" - "Show CPU utilization for my Compute Engine instances over the last hour" - "Which alert policies are configured in my-prod-project?" - "Run a PromQL query for request rate over the last 6 hours" ## Install ### Claude Code 1. Run this in a terminal, in your project folder: ```bash claude mcp add --transport http cloud-monitoring https://monitoring.googleapis.com/mcp ``` 2. Start Claude Code, type `/mcp`, pick **cloud-monitoring** and choose **Authenticate**. A browser window opens for the Google Cloud sign-in. Add `--scope user` to make it available in every project, not just this one. ### Claude Desktop 1. Open **Settings → Connectors** and click **Add custom connector**. 2. Name it **Google Cloud Monitoring** and paste this URL: ```url https://monitoring.googleapis.com/mcp ``` 3. Click **Add**, then **Connect**, and sign in when Google Cloud asks. Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too. ### claude.ai 1. Open the connector form on claude.ai. This button fills in the name and URL for you: [Add to claude.ai]() (opens connector settings) 2. Check that the URL reads `https://monitoring.googleapis.com/mcp` and click **Add**. 3. Click **Connect** and sign in when Google Cloud asks. Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under **Organization settings → Connectors**. ### ChatGPT 1. On chatgpt.com, open **Settings → Security and login** and turn on **Developer mode**. 2. Go to `chatgpt.com/plugins` and click **+** to create an app for a remote MCP server. 3. Paste `https://monitoring.googleapis.com/mcp` as the server URL and choose **OAuth**. ChatGPT sends you to Google Cloud to sign in. Developer mode is available on the web for Plus, Pro, Business, Enterprise and Education accounts. ### Cursor [Add to Cursor]() (opens Cursor) Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project): `mcp.json`: ```json { "mcpServers": { "cloud-monitoring": { "url": "https://monitoring.googleapis.com/mcp" } } } ``` Cursor shows **Needs login** next to the server. Click it to sign in. ### VS Code [Install in VS Code]() (opens VS Code) Or from a terminal: ```bash code --add-mcp '{"name":"cloud-monitoring","type":"http","url":"https://monitoring.googleapis.com/mcp"}' ``` Or commit it to the repo in `.vscode/mcp.json`: `.vscode/mcp.json`: ```json { "servers": { "cloud-monitoring": { "type": "http", "url": "https://monitoring.googleapis.com/mcp" } } } ``` VS Code asks you to sign in the first time the server starts. ### Devin Desktop 1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows): `mcp_config.json`: ```json { "mcpServers": { "cloud-monitoring": { "serverUrl": "https://monitoring.googleapis.com/mcp" } } } ``` 2. Refresh the MCP server list in Cascade and sign in when asked. Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers. ### Codex ```bash codex mcp add cloud-monitoring --url https://monitoring.googleapis.com/mcp codex mcp login cloud-monitoring ``` Or edit `~/.codex/config.toml` directly: `config.toml`: ```toml [mcp_servers.cloud-monitoring] url = "https://monitoring.googleapis.com/mcp" ``` ### Gemini CLI ```bash gemini mcp add --transport http cloud-monitoring https://monitoring.googleapis.com/mcp ``` Then, inside Gemini CLI, run `/mcp auth cloud-monitoring` to sign in. This adds it to the current project. Add `-s user` to use it everywhere. ### Any client Most clients accept this shape. Some name the URL field differently: `serverUrl` in Devin Desktop, `httpUrl` in Gemini CLI’s settings file. ```json { "mcpServers": { "cloud-monitoring": { "type": "http", "url": "https://monitoring.googleapis.com/mcp" } } } ``` Zed puts servers under `context_servers` in its settings. Cline needs `"type": "streamableHttp"`, or it assumes SSE. Client only starts local servers? Bridge it with `npx -y mcp-remote https://monitoring.googleapis.com/mcp`. ## Details - Server version: ESF - MCP protocol version: 2025-11-25 - Last checked: 2026-10-03 (reachable) - Listed: 2026-10-03 - Updated: 2026-10-03 --- Source: https://mcp.tc/i/cloud-monitoring (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report