Skip to main content
Glama
igorolv

loki-mcp-server

by igorolv
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Related Servers

Alternatives to loki-mcp-server

No user-submitted related servers found.

    Related Servers

    • observability-mcp

      ThainaJardim
      A
      license
      A
      quality
      D
      maintenance
      MCP server that enables AI assistants to query Grafana/Loki logs and Thanos/Prometheus metrics directly from MCP-compatible clients like Cursor or Claude Desktop.
      8
      MIT

    • mcp-server-logs-sieve

      Oluwatunmise-olat
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that connects Claude (or any MCP compatible client) to your existing log infrastructure. Query, summarize, and trace logs in plain English across GCP Cloud Logging, AWS CloudWatch, Azure Log Analytics, Grafana Loki, and Elasticsearch without writing filter expressions or leaving your editor.
      27 npm
      3
      MIT

    • loki-tail-mcp

      snickery
      A
      license
      A
      quality
      B
      maintenance
      An MCP server for Grafana Loki that enables LLMs to query, tail, and analyze logs, featuring fuzzy container-name matching, compact output, and tools for log patterns, volume, and label discovery. It can run as a local stdio server or a containerized HTTP service.
      9
      MIT

    • loki-mcp-server

      mo-silent
      F
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that enables AI assistants to query and analyze logs from Grafana Loki using LogQL, supporting label discovery and keyword search.
      4
      -

    • quickwit-mcp

      agarwalvivek29
      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
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.7/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool targets a distinct phase of the Loki log workflow: connection listing, label discovery, log querying, counting, and file export. No two tools overlap in purpose, and the descriptions make the boundaries between queryLogs, countLogs, and exportLogs explicit.

    Naming Consistency5/5

    All tool names follow a consistent camelCase verb+noun pattern (listConnections, discoverLogs, exportLogs, countLogs, queryLogs). There are no deviations in style or verb form.

    Tool Count5/5

    Five tools is well-scoped for a Loki log access server, covering the essential read and export operations without redundancy. Each tool earns its place and the set avoids both bloat and sparseness.

    Completeness4/5

    The set covers core log retrieval, counting, discovery, and export, but lacks support for arbitrary LogQL metric queries (e.g., rates) and live tailing. These are minor gaps that most log-querying workflows can work around, so coverage is strong but not exhaustive.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources