Skip to main content
Glama
adarshba

OpenObserve MCP Server

by adarshba

Related Servers

Alternatives to OpenObserve MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      MCP server that enables querying an OpenObserve instance for logs, traces, and metrics via tools like search_logs, search_traces, get_trace, and query_metrics, supporting natural-language-driven observability workflows.
      8
      46 npm
      MIT
    • A
      license
      B
      quality
      C
      maintenance
      A read-only MCP server for OpenObserve Community Edition that works over the REST API. Provides tools for searching logs, traces, stream schemas, and dashboards - no Enterprise license required.
      8
      170 PyPI
      16
      GPL 3.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that enables querying logs and metrics from Graylog, Prometheus, and InfluxDB 2.x. It provides tools for executing Lucene log searches, PromQL queries, and Flux queries directly within MCP-compatible clients.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for querying observability data from Elasticsearch, SkyWalking, and Prometheus/VictoriaMetrics, enabling AI models to search logs, traces, and metrics across environments.
      9
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that enables AI assistants to query and explore your OpenObserve observability data. Provides read-only access to logs, metrics, and traces for analysis and troubleshooting.
      5
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Unified MCP server for observability and monitoring, providing tools to query metrics, logs, and traces through Prometheus, Grafana, Loki, and Jaeger.
      2
      Mozilla Public 2.0

    TDQS

    A4.1/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: listing instances, searching logs, batch queries, listing streams, fetching schema, and retrieving context around events. No two tools overlap in functionality.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (list_instances, search_logs, batch_query, list_streams, get_stream_schema, get_logs_around), with no mixing of conventions.

    Tool Count5/5

    Six tools is well-scoped for interacting with OpenObserve instances, covering instance discovery, log searching (single and batch), stream listing, schema inspection, and context retrieval without being overwhelming or sparse.

    Completeness4/5

    The tool surface covers the core workflows of exploring and querying log data, but lacks direct support for querying metrics or traces, which are capabilities mentioned in instances. Still, for log-focused operations, it is nearly complete.

    Maintenance

    ActivityStale
    ResponsivenessNo issues