Jaeger MCP

Install

Works with Claude Code, Codex, VS Code, Cursor, Windsurf, Claude Desktop. Read the repository before you give any tool access to your data.

npx agentmarket install connector/mshegolev-jaeger-mcp

About

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this server can do and what it asks for, from its tool list and install config. Checked Oct 25, 2026.

Tools

15 read · 0 write · 0 deleteRead-only

Secrets

2 (API keys, tokens or passwords)

Install scripts

Not scanned yet

Runs as

Python package

Tools (15)

Read from the source code; the running server may differ. Descriptions are the server’s own words; hidden characters are shown as [U+…].

• jaeger_compare_tracesCompare Tracesread-only

  Compare two traces structurally — find added, removed, and changed spans. Fetches both traces from Jaeger and performs a structural diff by matching spans on ``(operationName, serviceName, parentOperation)`` — not span IDs, which differ across traces. Reports duration deltas and tag differences for changed spans. Examples: - Use when: "What changed between a fast and slow request?" → pass the trace IDs of both requests; inspect ``changed_spans`` for duration deltas. - Use when: "Did a deployment add new service calls?" → compare a pre-deploy trace with a post-deploy…

• jaeger_compare_windowsCompare Time Windowsread-only

  Compare aggregate trace behavior between two time periods for a service. Fetches traces from both time windows, aggregates span statistics per operation, then compares the aggregate behavior to detect performance changes. Examples: - Use when: "Did our latest deployment affect performance?" → compare pre-deploy and post-deploy time windows for the service. - Use when: "Which operations got slower after the database upgrade?" → check the comparison_p95_us and p95_delta_pct columns for increases. - Use when: "Are we seeing new error patterns?" → look for operation…

• jaeger_critical_pathCritical Path Analysisread-only

  Identify the critical path and top bottlenecks in a trace. Finds the longest-duration span chain (critical path) from root to leaf, and ranks spans by self-time to find actual performance bottlenecks. Examples: - Use when: "Why is this trace so slow?" → call with the slow trace ID; examine the critical_path_duration_us and critical_path_percentage to see how much of the total time is spent on the longest path. - Use when: "Which operations are consuming the most CPU/self-time?" → check the bottlenecks list sorted by self_time_us descending. - Use when: Deb…

• jaeger_detect_anomaliesDetect Anomaliesread-only

  Detect latency and error-rate anomalies for a service by comparing recent behavior to historical baseline. Fetches traces from a historical baseline window and a recent observation window, computes per-operation statistics for both, then identifies statistically significant deviations that may indicate performance issues or reliability problems. Examples: - Use when: "Are there any new performance issues in `order-service`?" → `service='order-service'` (uses default 60-minute baseline, 5-minute current). - Use when: "Be more sensitive to subtle changes" → set `sensitivity…

• jaeger_find_test_tracesread-only

  Find Jaeger traces matching the supplied tag query. Accepts any tag key-value schema (Allure, pytest, custom) without normalization. When service is omitted, searches all known services concurrently (capped at 20). Results are sorted newest-first.

• jaeger_forecast_capacityForecast Service Capacityread-only

  Forecast future throughput demands and resource requirements for a service. Provides predictions for the next 7-30 days with confidence intervals to enable infrastructure scaling decisions. Args: service: Service name to forecast capacity for days_ahead: Number of days to forecast ahead (default: 30 days) Returns: ForecastResult with throughput predictions and resource requirements

• jaeger_get_dependenciesGet Dependenciesread-only

  Retrieve the service-to-service call graph from Jaeger. Wraps ``GET /api/dependencies``. Returns directed edges (parent → child) with ``call_count`` — the number of spans where parent called child in the lookback window. Use this to understand service topology, find high fan-out services, or verify that a new service is connected as expected. Examples: - Use when: "What services does `order-service` call?" → check edges where ``parent='order-service'``. - Use when: "Map the full service dependency graph for the last 7 days" → ``lookback_hours=168``. - Use when: "Whic…

• jaeger_get_traceGet Traceread-only

  Retrieve full trace detail with all spans, service breakdown, and execution tree. Wraps ``GET /api/traces/{traceID}``. Returns every span in the trace, per-service statistics, and a flat execution tree (each node lists its child span IDs) that summarises the call hierarchy. Error spans are identified by ``tags["error"] = "true"``. Examples: - Use when: "Why is trace `abc123...` slow — show me the span breakdown" → ``trace_id='abc123...'``; inspect ``services`` for the heaviest service and ``execution_tree`` for the call hierarchy. - Use when: "Which service caused the er…

• jaeger_list_operationsList Operationsread-only

  List all operation names Jaeger has seen for a given service. Wraps ``GET /api/services/{service}/operations``. Useful for discovering which operation names to pass as filters to ``jaeger_search_traces``. Output is capped at 500 operations. Examples: - Use when: "What HTTP endpoints does `order-service` expose in tracing?" → ``service='order-service'``. - Use when: You want to search for a specific slow operation but need the exact name — list operations first, then pass it to ``jaeger_search_traces``. - Use when: Auditing which gRPC methods a service traces. …

• jaeger_list_servicesList Servicesread-only

  List all services that Jaeger has observed traces for. Wraps ``GET /api/services``. Jaeger returns all services at once — no pagination. Output is capped at 500 services with a truncation hint. Use this first to discover valid service names before calling ``jaeger_list_operations`` or ``jaeger_search_traces``. Examples: - Use when: "What services does Jaeger know about?" → call with no parameters; read the ``services`` list. - Use when: "Is `payment-service` instrumented?" → check if `payment-service` appears in the services list. - Use when: Starting a debugging ses…

• jaeger_predict_degradationPredict Performance Degradationread-only

  Predict potential performance degradation events for a service. Analyzes historical trace data patterns, critical path trends, and anomaly detection results to forecast likely performance issues 2-24 hours in advance. Args: service: Service name to analyze for potential degradation hours_back: Number of hours of historical data to analyze (default: 168 hours/1 week) Returns: PredictionResult with degradation forecast, confidence level, and recommendations

• jaeger_regression_diffread-only

  Compare two Jaeger time windows and classify per-operation regressions. Fetches traces from the baseline and comparison windows, then classifies each operation as regressed, recovered, appeared, or removed. Results are sorted by severity score (0-100) descending for easy triage.

• jaeger_search_tracesSearch Tracesread-only

  Search Jaeger traces with rich filters. Wraps ``GET /api/traces``. Returns a list of trace summaries — use ``jaeger_get_trace`` to drill into a specific trace for span details. The ``tags`` parameter accepts a JSON string so the LLM can construct arbitrary tag filters. Durations (``min_duration``/``max_duration``) are forwarded as-is to Jaeger (e.g. ``'100ms'``, ``'1.5s'``). Examples: - Use when: "Show me recent 500 errors in `order-service`" → ``service='order-service'``, ``tags='{"http.status_code":"500"}'``. - Use when: "Find slow traces (>1s) for `checkout` endpoint" …

• jaeger_span_statisticsSpan Statisticsread-only

  Compute per-operation latency percentiles and error rates across recent traces. Fetches up to ``limit`` traces for the given service (optionally filtered by operation), then aggregates all spans by operation name. For each operation reports: span count, p50/p95/p99 duration in microseconds, error count, and error rate. Duration values are in microseconds (integer). Error rate is ``error_count / span_count`` (float, 0.0–1.0). Examples: - Use when: "What are the p95 latencies for each endpoint in `order-service`?" → ``service='order-service'``; inspect each operation's ``p95_duratio…

• jaeger_test_profileread-only

  Aggregate per-operation latency hotspots across all traces matching the supplied tag query. Operations are ranked by total wall time descending so the most expensive appear first.

Signals

Stars

2

Forks

0

Open issues

1

Weekly downloads

57

Last commit

Aug 12, 2026 (2 months ago)

Last release

Aug 12, 2026 (2 months ago)

Last package publish

Aug 7, 2026 (2 months ago)

From GitHub (fetched Oct 24, 2026) and the package registry.

Details

Registry name

io.github.mshegolev/jaeger-mcp

Version

0.1.1

Auth

API key

Packages

pypi jaeger-mcp

License

MIT

Repository

github.com/mshegolev/jaeger-mcp

First seen

Oct 24, 2026

Last checked

Oct 24, 2026

Source

Official MCP Registrygithub-graphql