Skip to main content
Glama
krackenservices

OTEL MCP Server

Related Servers

Alternatives to OTEL MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables to interact with Jaeger distributed tracing system through the MCP protocol. Supports querying traces, services, and operations via natural language.
      73 npm
      18
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Provides read-only access to Jaeger distributed tracing data through the Model Context Protocol. Enables Claude and other MCP-capable agents to search traces, inspect spans, and analyze service dependencies directly within conversations.
      15
      41 PyPI
      2
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Read-only MCP server for querying Jaeger environments from Codex, returning compact, sanitized trace summaries to protect sensitive data.
      -
    • A
      license
      A
      quality
      D
      maintenance
      MCP server that gives AI agents access to your application's OpenTelemetry traces for querying, analysis, and debugging.
      5
      13 npm
      2
      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
    • A
      license
      A
      quality
      C
      maintenance
      Enables querying logs, traces, and metrics from multiple OpenObserve instances via MCP tools, with parallel execution, batching, and caching.
      6
      46 npm
      11
      MIT

    TDQS

    B3.4/5.0

    Scored across 7 tools

    Disambiguation3/5

    find_errors and search_traces with has_error overlap significantly, as do get_slow_traces and search_traces with duration filters. While get_trace, get_operation_stats, list_services, and list_operations are clearly distinct, the overlapping search/filter tools could cause misselection.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (get_, find_, list_, search_). The convention is predictable and readable throughout.

    Tool Count5/5

    Seven tools are well-scoped for an observability server covering trace retrieval, error finding, performance analysis, and service discovery. Each tool appears to earn its place without excessive overlap or missing essentials.

    Completeness5/5

    The surface covers the full trace lifecycle: discovery (list_services, list_operations), retrieval (get_trace, search_traces), error analysis (find_errors), and performance stats (get_operation_stats, get_slow_traces). No obvious gaps for a read-only OTEL/Jaeger server.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues