MCP Server Logs Sieve

Communauté Cloud et DevOps

Query, summarize and trace logs in plain English across GCP Cloud Logging, AWS CloudWatch, Azure Log Analytics, Grafana Loki and Elasticsearch.

Installation

Les étapes d'installation sont dans la documentation ci-dessous. Documentation

Documentation

Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.

Sommaire
  1. mcp-server-logs-sieve
  2. Why this exists
  3. Supported providers
  4. Prerequisites
  5. Quick MCP config
  6. Provider auth and env vars
  7. CLI usage
  8. Documentation
  9. Contributing

mcp-server-logs-sieve

mcp-server-logs-sieve is an MCP server that lets AI assistants query logs directly from your observability backend.

Ask debugging questions in plain language, and let Logs Sieve pull the exact logs and context for you.

Why this exists

During incidents, a lot of time goes into repetitive steps:

  • finding the right log source
  • narrowing the time window
  • spotting recurring failure patterns
  • following one trace across services

Logs Sieve packages those workflows into four tools: query_logs, summarize_logs, trace_request, and list_log_sources.

Supported providers

  • Google Cloud Logging (gcp)
  • AWS CloudWatch Logs (aws)
  • Azure Monitor Logs (azure)
  • Grafana Loki (loki)
  • Elasticsearch (elasticsearch)

Prerequisites

⚠️ Node.js 20 or above is required.

This package uses ES modules and dependencies that need Node.js 20+. If you see ERR_MODULE_NOT_FOUND errors, check your Node version with node -v and upgrade if needed.

This applies whether you run via npx, install globally, or use from source.

Quick MCP config

Example .mcp.json:

{
  "mcpServers": {
    "logs-sieve": {
      "command": "npx",
      "args": ["-y", "mcp-server-logs-sieve@latest", "--provider", "gcp"]
    }
  }
}

If you are running from this repo source directly, you can still use node ./bin/mcp-server-logs-sieve.js --provider gcp.

First-time setup: On first use, npx needs to download and install the package (~40s). Claude Code may time out waiting for this. Run the following once in your terminal to prime the cache before adding it to your MCP config:

npx mcp-server-logs-sieve@latest --provider gcp
# (Ctrl+C once it starts — you just need the install to complete)

After that, Claude Code will start the server instantly from the npx cache.

After updating config, restart your MCP client and confirm with /mcp.

Provider auth and env vars

See provider-specific setup and auth docs:

For Elasticsearch API compatibility headers:

export ELASTICSEARCH_COMPAT_VERSION=8

CLI usage

The package also includes a CLI for direct terminal usage:

mcp-server-logs-sieve query --provider gcp --scope my-project --last 1h --filter "payment failed"
mcp-server-logs-sieve summarize --provider gcp --scope my-project --last 24h
mcp-server-logs-sieve trace --provider gcp --scope my-project --trace <trace-id>
mcp-server-logs-sieve sources --provider gcp --scope my-project

Documentation

Contributing

Contributions are welcome.

Questions fréquentes

Qu'est-ce que MCP Server Logs Sieve ?

Query, summarize and trace logs in plain English across GCP Cloud Logging, AWS CloudWatch, Azure Log Analytics, Grafana Loki and Elasticsearch.

Comment installer MCP Server Logs Sieve ?

Suivez les étapes d'installation de sa documentation, affichée sur cette page et dans son dépôt.

MCP Server Logs Sieve est-il open source ?

Oui. Son code est sur GitHub sous licence MIT.

Qui maintient MCP Server Logs Sieve ?

Il est publié par Oluwatunmise-olat. AI.tn le référence sans le maintenir ni le recommander.

Issu des listes communautaires awesome-mcp-servers et du dépôt GitHub du projet. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.