Skip to main content
Glama
J-X0

lockwood-group-observability-mcp

by J-X0
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to lockwood-group-observability-mcp

No user-submitted related servers found.

    Related Servers

    • log-mcp

      ascii766164696D
      A
      license
      A
      quality
      D
      maintenance
      MCP server for log file analysis. Gives LLMs the ability to efficiently analyze large log files without loading them into context.
      7
      100
      MIT

    • Log Analyzer MCP Server

      suriya-ML
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server for intelligent log analysis providing semantic search, error pattern clustering, and smart error detection. It enables users to process, vectorize, and query local logs to efficiently identify issues and generate AI-powered summaries.
      MIT

    • log-ai-optimizer

      JustinHabashi
      F
      license
      Not graded
      quality
      C
      maintenance
      Compresses log files into templates and statistics using Drain3, and exposes them to AI assistants via an MCP server for efficient log monitoring and anomaly detection.
      -

    • Drain3 MCP Server

      xinqihuang
      A
      license
      A
      quality
      C
      maintenance
      MCP server that wraps Drain3 for streaming log template mining, read-only matching, parameter extraction, and model persistence, exposing tools and resources to train on logs and query learned templates.
      8
      MIT

    • elastic-mcp

      jrvalinas
      A
      license
      B
      quality
      D
      maintenance
      Small production-oriented MCP server for diagnosing incidents from Elasticsearch logs with unknown schema. It provides tools for log discovery, retrieval, and issue diagnosis.
      6
      MIT
    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

    A3.7/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only a single tool, there is no possibility of confusion or overlap between tools. The tool's purpose is clear and unambiguous.

    Naming Consistency5/5

    The single tool name 'triage_logs' follows a clear verb_noun pattern in snake_case. Without other tools to compare, there is no inconsistency.

    Tool Count2/5

    The server is named for observability yet exposes only one tool. A single tool is too few for the apparent breadth of an observability platform, making the count inadequate.

    Completeness1/5

    The tool only performs log triage via clustering. Missing are core observability operations such as querying, filtering, retrieving, or alerting, leaving the surface severely incomplete for the domain.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources