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
Payai X402 Tools

6 hours ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

a day ago