Google Cloud Monitoring, verificado

Servidor MCP de Google Cloud · Verificado

Query metrics, PromQL, alerts, alert policies and dashboards in Google Cloud Monitoring from your assistant.

Inicio de sesión OAuth (Inicias sesión con el proveedor la primera vez que te conectas)Streamable HTTP

Conectar con Google Cloud Monitoring

Google Cloud Monitoring requiere iniciar sesión. Conéctate con su propia URL:

https://monitoring.googleapis.com/mcp

La primera vez, tu cliente abre el inicio de sesión de Google Cloud. El token queda entre tu cliente y Google Cloud.

Compartir este servidor

Abre esta página, con la URL y los pasos de configuración.

mcp.tc/i/cloud-monitoring

Descripción

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.

Qué puedes hacer

  • 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

Herramientas 9

  • list_timeseriesSolo lectura

    List time series data from the Cloud Monitoring API with filter and aggregation options.

  • query_rangeSolo lectura

    Evaluate a PromQL query over a time range.

  • get_alert_policySolo lectura

    Get details of a specific alerting policy.

  • list_alert_policiesSolo lectura

    List alerting policies in a Google Cloud project.

  • get_alertSolo lectura

    Get details of a specific alert, a violation of an alert policy.

  • list_alertsSolo lectura

    List current and past alerts in a project.

  • list_metric_descriptorsSolo lectura

    Discover the metric types available in a project.

  • list_dashboardsSolo lectura

    List custom monitoring dashboards in a project.

  • get_dashboardSolo lectura

    Retrieve a single custom monitoring dashboard by resource name.

Leídas del servidor en funcionamiento el 3 oct 2026. Solo lectura, Escribe y Puede borrar son indicaciones que declara el servidor; tu cliente decide si te pregunta antes de ejecutar una herramienta.

Prompts de ejemplo

  • 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

Configuración

Todos los clientes se conectan a monitoring.googleapis.com, y la primera vez Google Cloud te pide que inicies sesión. Elige el tuyo; la página recuerda tu elección.

Claude Code

  1. Run this in a terminal, in your project folder:
claude mcp add --transport http cloud-monitoring https://monitoring.googleapis.com/mcp
  1. 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:
https://monitoring.googleapis.com/mcp
  1. 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:
  1. Check that the URL reads https://monitoring.googleapis.com/mcp and click Add.
  2. 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

Or add it by hand to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (this project):

mcp.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

Or from a terminal:

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
{
  "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
{
  "mcpServers": {
    "cloud-monitoring": {
      "serverUrl": "https://monitoring.googleapis.com/mcp"
    }
  }
}
  1. 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

codex mcp add cloud-monitoring --url https://monitoring.googleapis.com/mcp
codex mcp login cloud-monitoring

Or edit ~/.codex/config.toml directly:

config.toml
[mcp_servers.cloud-monitoring]
url = "https://monitoring.googleapis.com/mcp"

Gemini CLI

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.

{
  "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.

Preguntas frecuentes

Can I paste mcp.tc/i/cloud-monitoring into my MCP client?

No. mcp.tc links are pages, not server addresses. Connect with https://monitoring.googleapis.com/mcp, so your client talks to Google Cloud Monitoring directly. The sign-in token only works there anyway. The quick link is for sharing: it opens this page, with setup steps for every client.

Does Google Cloud Monitoring need an API key or a sign-in?

Yes, you need a Google Cloud account. The first time your client connects, it opens Google Cloud’s sign-in page. The token goes straight to the server’s own URL, never through mcp.tc.

Is Google Cloud Monitoring a remote or a local server?

Remote. Google Cloud hosts it at https://monitoring.googleapis.com/mcp, and it speaks Streamable HTTP. There’s nothing to install.

What can Google Cloud Monitoring do?

It has 9 tools, including list_timeseries, query_range y get_alert_policy. You can list time series data with filters and aggregation, run PromQL queries over a time range y list and inspect alert policies.

Which clients can use it?

Any client that supports remote MCP servers: Claude Code, Claude Desktop, claude.ai, ChatGPT in developer mode, Cursor, VS Code, Devin Desktop, Codex, Gemini CLI, Zed and others. The setup steps cover each one.

Who wrote this page?

mcp.tc’s robot read Google Cloud Monitoring’s own metadata (its MCP handshake, tool list and public pages), and an AI model drafted the text from it. A person reviews anything the checks can’t confirm. The text can still be wrong, so if you spot a mistake, use Report this listing on this page.

Insertar

Muestra Google Cloud Monitoring en un README o en tu web. Cada inserción enlaza a esta página, usa la URL propia del servidor y no instala cookies. Cómo funcionan las inserciones

Insignia para README

Vista previa de la insignia, claraVista previa de la insignia, oscura
Markdown
[![Google Cloud Monitoring on mcp.tc](https://mcp.tc/i/cloud-monitoring/badge.svg)](https://mcp.tc/i/cloud-monitoring)
HTML
<a href="https://mcp.tc/i/cloud-monitoring"><img src="https://mcp.tc/i/cloud-monitoring/badge.svg" alt="Google Cloud Monitoring on mcp.tc" height="20"></a>

Sigue el modo claro u oscuro de quien lee. Añade ?theme=light o ?theme=dark para fijarlo, o ?style=compact para mostrar el símbolo sin la palabra.

Tarjeta para web

HTML
<script src="https://mcp.tc/w/cloud-monitoring.js" async></script>

La tarjeta aparece donde esté la etiqueta. Añade data-theme="dark" o data-size="compact" a la etiqueta para cambiarla. El archivo contiene todo lo que necesita, así que no hace otras solicitudes ni instala cookies.

iframe

HTML
<iframe src="https://mcp.tc/embed/cloud-monitoring" title="Google Cloud Monitoring on mcp.tc" width="420" height="200" loading="lazy" allow="clipboard-write" style="border:0;border-radius:8px;max-width:100%"></iframe>

Úsalo en páginas que no permiten scripts. Añade ?theme=light o ?theme=dark a la dirección para fijar los colores.

JSON

La ficha como datos para tus propias páginas y herramientas: nombre, descripción corta, la URL propia del servidor, herramientas y los enlaces «Add to». Cualquier web puede leerla (CORS abierto).

https://mcp.tc/i/cloud-monitoring.json

Qué significa cada campo

mcp.tc no tiene relación con Google Cloud. Esta página se creó a partir de los metadatos públicos de Google Cloud Monitoring, comprobados por última vez el 3 oct 2026, y un modelo de IA escribió la descripción, así que puede contener errores. Los nombres y marcas pertenecen a sus titulares. ¿Algo no cuadra? Reportar esta ficha.