ScriptsMay 12, 2026·2 min read

Monoscope — LLM Query for Logs/Traces/Metrics

Monoscope stores logs/traces/metrics in S3-compatible buckets and lets you explore them with natural-language queries plus a CLI and self-hosted UI.

Script Depot
Script Depot · Community
Agent ready

This asset can be read and installed directly by agents

TokRepo exposes a universal CLI command, install contract, metadata JSON, adapter-aware plan, and raw content links so agents can judge fit, risk, and next actions.

Native · 94/100Policy: allow
Agent surface
Any MCP/CLI agent
Kind
Cli
Install
Manual
Trust
Trust: Established
Entrypoint
docker-compose up
Universal CLI install command
npx tokrepo install a86f3430-eb78-50ab-bebe-6eef4f53ea4a
install contractmetadata JSONadapter planraw content
Intro

Monoscope stores logs/traces/metrics in S3-compatible buckets and lets you explore them with natural-language queries plus a CLI and self-hosted UI.

  • Best for: Log/trace triage and NLQ for observability data
  • Works with: Docker Compose; S3-compatible storage; OpenTelemetry ecosystem
  • Setup time: 10–30 minutes

Practical Notes

  • GitHub: 692 stars · 23 forks; pushed 2026-05-11 (verified via GitHub API).
  • README quick start uses docker-compose up and the UI defaults to http://localhost:8080.
  • Per README: CLI emits a stable JSON envelope, making it easy to chain search → triage in agent workflows.

Main

A “minimum useful loop” for incidents:

  1. Ingest a small amount of real telemetry (or use the test send/telemetrygen commands).
  2. Ask a narrow question first (“show errors for service X”), then progressively widen the window.
  3. Once you find a suspicious trace/log event, keep the query trail (filters + IDs) as a repeatable runbook.

When you later connect an agent, the goal is not “one-shot answers”—it’s to have the agent produce a deterministic chain of CLI commands you can re-run and audit.

FAQ

Q: Is cloud required? A: No—README includes a self-host quick start with Docker Compose.

Q: Where is data stored? A: README states it stores telemetry in S3-compatible buckets.

Q: How do I make it agent-friendly? A: Prefer CLI-driven workflows and keep the command chain as your audit trail.

🙏

Source & Thanks

Source: https://github.com/monoscope-tech/monoscope > License: AGPL-3.0 > GitHub stars: 692 · forks: 23

Discussion

Sign in to join the discussion.
No comments yet. Be the first to share your thoughts.

Related Assets

Datadog MCP Server — Query Metrics and Logs from AI Agents

Community Datadog MCP server lets Claude / Cursor query metrics, logs, traces, monitors in natural language. SRE copilots, on-call triage.

MCP Configs
Datadog

SigNoz MCP Server — Query Traces, Logs & Alerts

SigNoz MCP Server connects MCP clients to your SigNoz instance: query traces/logs, inspect alerts, and automate observability workflows using an API key.

MCP Configs
MCP Hub

magic-cli — LLM Command Suggestion for Terminals

magic-cli is a Rust CLI that suggests commands, semantically searches shell history, and works with local or cloud LLM providers.

CLI Tools
Script Depot

Augustus — LLM Vulnerability Scanner (Go CLI)

Augustus is a Go-based LLM vulnerability scanner covering 210+ adversarial attacks and 28 providers; verified 205★ and pushed 2026-05-11.

CLI Tools
Script Depot
◈Home🔍Search👤Me