Skip to main content
Glama
abuzo

victorialogs-mcp

by abuzo

Related Servers

Alternatives to victorialogs-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      F
      maintenance
      A read-only MCP server that exposes Quickwit log search and aggregations to LLM clients, enabling natural language log investigation.
      Apache 2.0
    • A
      license
      Not graded
      quality
      F
      maintenance
      A read-only MCP server for the Auralogs logging platform, enabling AI agents to query production logs, search errors, and retrieve AI analyses without write access. It allows you to ask your coding assistant 'what's broken in production right now?' by connecting to your logs via a simple bearer auth key.
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      A read-only stdio MCP server that provides a generic log-querying layer for Grafana/Loki, enabling discovery, retrieval, and aggregation of logs (raw, slow, errors, volumes) through 15 tools, with hard limits on data volume and no built-in business logic.
      15
      10 npm
      1
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      A read-only MCP server for querying Sumo Logic logs, enabling AI assistants to search and investigate application logs with opinionated tools and secure credential handling.
      5
      12 npm
      1
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Read-only MCP server for Grafana Loki: lets AI agents (Claude Code, Cursor, Copilot) discover labels, read bounded LogQL pages, count lines by label or time, and export logs — across several Loki stands
      5
      Apache 2.0

    TDQS

    B3.4/5.0

    Scored across 8 tools

    Disambiguation4/5

    The eight tools mostly target distinct outputs: raw log retrieval (search_logs), stream discovery, field discovery, value discovery, time-bucketed counts (hits), aggregation pipelines (query_stats), and a UUID lookup convenience wrapper. However, search_logs, query_stats, hits, and search_uuid all run LogsQL-style queries over logs with overlapping capability, and only the detailed descriptions keep them apart.

    Naming Consistency3/5

    All names share the victorialogs. prefix and snake_case, which aids readability. But the internal pattern is mixed: search_stream/search_logs/search_uuid are verb_noun, list_streams is verb_noun, field_names/field_values are noun phrases, and hits/query_stats are bare noun/verb forms, so there is no single predictable convention.

    Tool Count5/5

    Eight tools is well-scoped for a log-search backend, with each tool covering a distinct capability (search, discovery, aggregation, counting, ID lookup) rather than redundant variants. Nothing feels padded or missing.

    Completeness4/5

    The surface covers stream discovery, field/value discovery, raw search, UUID lookup, time-bucketed counting, and aggregation, which is broad lifecycle coverage for querying logs. Minor gaps exist (no explicit schema/field-type or export/tail tool), but agents can work around them via LogsQL.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues