Skip to main content
Glama
mshegolev

jaeger-mcp

by mshegolev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to jaeger-mcp

No user-submitted related servers found.

    Related Servers

    • jaeger-mcp-server

      serkan-ozal
      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.
      79 npm
      18
      MIT

    • OTEL MCP Server

      krackenservices
      A
      license
      B
      quality
      C
      maintenance
      Enables querying and analyzing distributed traces from Jaeger, including service discovery, trace inspection, and performance analysis, through MCP tools.
      7
      2
      Apache 2.0

    • jaeger-mcp

      parkavenue9639
      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.
      -

    • otel-mcp

      moondef
      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
      16 npm
      2
      MIT

    • pinpoint-apm-mcp

      Karma098
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides Claude and other AI agents with read-only, guardrailed access to Pinpoint APM data, enabling production debugging through traces, metrics, transactions, and service topology.
      Apache 2.0

    • tracehub-mcp

      mcpsmiths
      A
      license
      A
      quality
      A
      maintenance
      Connects AI assistants to OpenTelemetry trace backends such as Jaeger, Tempo, Traceloop, and Datadog, enabling natural-language searching of traces and spans, error discovery, and service listing. It also provides LLM-specific analytics, including token usage aggregation, model performance comparison, and identification of the most expensive or slowest traces.
      19
      79 PyPI
      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

    A3.9/5.0

    Scored across 15 tools

    Disambiguation2/5

    Several tools have overlapping purposes. jaeger_search_traces and jaeger_find_test_traces both search traces with tag filters, and jaeger_compare_windows, jaeger_detect_anomalies, and jaeger_regression_diff all compare two time windows to identify performance changes, making it easy for an agent to select the wrong one. The differences between these are subtle and not clearly delineated.

    Naming Consistency3/5

    All tools share the jaeger_ prefix and use snake_case, but the naming pattern is inconsistent: some are verb_noun (list_services, search_traces) while others are noun_phrase (span_statistics, critical_path, test_profile). This mixed convention is readable but lacks the predictability of a uniform verb_noun scheme.

    Tool Count4/5

    15 tools is at the upper boundary of a well-scoped set, but the advanced analytics tools (predict_degradation, forecast_capacity, detect_anomalies) expand the server's capability beyond basic tracing. The count is reasonable, though some tools could be merged without losing functionality.

    Completeness4/5

    The core Jaeger read operations are fully covered: service discovery, operation listing, trace search, trace detail, and dependency graph. Advanced analytics like comparisons, anomaly detection, and predictions provide extra depth, leaving few obvious gaps for a tracing-focused server.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources