All servers / Observability / Google Cloud Observability MCP server
Google Cloud Observability MCP server
MCP Server for GCP environment for interacting with various Observability APIs.
Tested by ConnectATDScore 82 out of 100. Tested 2026-11-18 on package version 0.2.3. Package: @google-cloud/observability-mcp · source
Score breakdown
| Runs | 18 / 20 | |
|---|---|---|
| Tool descriptions | 20 / 20 | |
| Package safety | 20 / 20 | |
| Maintenance | 8 / 20 | |
| Adoption | 16 / 20 |
What we saw
- Starts and answers the MCP handshake: yes (10.2 seconds including download)
- Tools offered: 13
- Last published: 2026-02-11
- Weekly downloads (npm): 22,550
- License: Apache-2.0 · Direct dependencies: 6
Want this server set up for your team?
ConnectATD builds AI automation and wires up MCP servers like this one. Tell us what you are trying to do.
Talk to ConnectATDTools and how they are described
Agents choose tools from these descriptions. Under each name you can see how many of its parameters are explained.
list_log_entries5 of 5 parameters describedUse this as the primary tool to search and retrieve log entries from Google Cloud Logging. It's essential for debugging application behavior, finding specific error messages, or auditing events. The 'filter' is powerful and can be used to select logs by severity, resource type, text content, and more.
list_log_names3 of 3 parameters describedUse this as the primary tool to list the log names in a Google Cloud project. This is useful for discovering what logs are available for a project. Only logs which have log entries will be listed.
list_buckets3 of 3 parameters describedUse this as the primary tool to list the log buckets in a Google Cloud project. Log buckets are containers that store and organize your log data. This tool is useful for understanding how your logs are stored and for managing your logging configurations.
list_views3 of 3 parameters describedUse this as the primary tool to list the log views in a given log bucket. Log views provide fine-grained access control to the logs in your buckets. This is useful for managing who has access to which logs.
list_sinks3 of 3 parameters describedUse this as the primary tool to list the log sinks in a Google Cloud project. Log sinks control how Cloud Logging routes your logs to supported destinations, such as Cloud Storage buckets, BigQuery datasets, or Pub/Sub topics. This is useful for understanding your logging export configurations.
list_log_scopes3 of 3 parameters describedUse this as the primary tool to list the log scopes in a Google Cloud project. Log scopes allow you to query logs from multiple projects in a single view. This is useful for centralized logging across a large organization.
list_metric_descriptors4 of 4 parameters describedUse 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_time_series6 of 6 parameters describedUse this as the primary tool to retrieve metric data over a specific time period. This is the core tool for monitoring and observability, allowing you to get the actual data points for a given metric.
list_alert_policies5 of 5 parameters describedUse 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.
list_alerts5 of 5 parameters describedUse 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_traces7 of 7 parameters describedUse this as the primary tool to retrieve and examine distributed traces from Google Cloud Trace. Traces provide a detailed view of the path of a request as it travels through your application's services. This is essential for understanding latency issues and debugging complex, multi-service workflows. This will only return the root trace span, to gather full information call get_trace with that id.
get_trace2 of 2 parameters describedUse this as the primary tool to retrieve a single distributed trace from Google Cloud Trace. Traces provide a detailed view of the path of a request as it travels through your application's services. This is essential for understanding latency issues and debugging complex, multi-service workflows. This is often used as a follow on to list_traces to get full details on a specific trace.
list_group_stats5 of 5 parameters describedUse this tool ONLY to find and analyze recurring stack traces in your application. It aggregates similar stack traces, providing statistics like the number of occurrences and the number of affected users. DO NOT use this tool for general error searches or to view individual error logs. For queries asking to "find errors", or "show me errors", you MUST use list_log_entries tool. CRITICAL: Default to other tooling for generic questions about errors.
Tested in a sandbox with an empty environment: no API keys, a throwaway folder, nothing from a real account. A passing test shows the server runs and responds. It is not a security audit.