Labsco
MCP SERVER

Google Cloud Logging

by swen128

Search Google Cloud Logging with the filter syntax you already use, then open a single entry in full.

Observability, Monitoring & Incident Response
Summary
An agent can go from an error report to the log line behind it.

It keeps GCP's own filter language rather than inventing one, so a filter you would paste into the console works here — and the entry that matters comes back whole instead of flattened into a summary.

What it is

A reader for Google Cloud Logging. Queries take GCP's own filter syntax with sort order, page size and pagination, and any single entry can be pulled back complete by id. It authenticates with the Google Cloud credentials already on the machine.

What you get
  • Logs queried across a project using GCP logging filter syntax
  • Sort order, page size and page tokens for working through large result sets, plus a choice of summary fields
  • Specific log resources targeted rather than the whole project
  • One log entry retrieved in full, by id
  • The GCP projects you have access to, listed
Requirements

The Bun runtime, access to the Cloud Logging API, and Google credentials already in place — either gcloud application-default login or a service account file. A default project is set in the server's environment.

Setup effort

One command plus a key — npx -y cloud-logging-mcp, then supply credentials