mcp-server-google-logging

Created By
kazuhideokia year ago
Overview

What is mcp-server-google-logging?

The mcp-server-google-logging is a server application that utilizes the Google Cloud CLI to read and manage logs from Google Cloud services.

How to use mcp-server-google-logging?

To use the mcp-server-google-logging, run the server with the command: node -- /path/to/mcp-server-google-logging/dist/index.js --project=<project-id> after ensuring you have the gcloud CLI installed and configured.

Key features of mcp-server-google-logging?

  • Read and display logs based on specified filter conditions.
  • Real-time log monitoring.
  • Manage log entries, including listing and deleting logs.
  • Manage log buckets and sinks for exporting logs to external services.
  • Create and manage log-based metrics for monitoring and alerts.

Use cases of mcp-server-google-logging?

  1. Monitoring application logs in real-time.
  2. Managing log retention and storage in Google Cloud.
  3. Creating alerts based on specific log conditions.

FAQ from mcp-server-google-logging?

  • What permissions do I need to use this project?

You need to have IAM permissions to access the logs in your Google Cloud project.

  • Can I filter logs using complex conditions?

Yes, you can filter logs using resource types, timestamps, and severity levels with AND/OR combinations.

  • Is there a way to delete logs?

Yes, you can delete logs, but be cautious as this action cannot be undone.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
kazuhideoki
Star
0
Language
TypeScript
License
-
Category
monitoring
Tags

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago