Jaeger MCP Server

If you already use Jaeger, the jaeger mcp server is the piece that lets your assistant work with it directly. Jaeger MCP — search traces, inspect spans, map service dependencies (read-only).

What the server does

The existing Jaeger integrations require a running UI or custom scripts. This server:

• Speaks the standard Model Context Protocol over stdio — works with Claude Desktop, Claude Code, Cursor, and any MCP client
• Is read-only: all 12 tools carry readOnlyHint: true — zero risk of modifying trace data
• Returns dual-channel output: structured JSON (structuredContent) for programmatic use + Markdown (content) for human-readable display
• Has actionable error messages that name the exact env var to fix and suggest a next step
• Supports Bearer token, HTTP Basic auth, or no auth (common for internal deployments)
• Includes OpenAPI specification documenting the underlying Jaeger Query API (openapi.yaml)

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

• jaeger_list_services — GET /api/services
• jaeger_list_operations — GET /api/services/{service}/operations
• jaeger_search_traces — GET /api/traces
• jaeger_get_trace — GET /api/traces/{traceID}
• jaeger_get_dependencies — GET /api/dependencies
• jaeger_compare_traces — GET /api/traces/{traceID} ×2
• jaeger_span_statistics — GET /api/traces
• jaeger_critical_path — GET /api/traces/{traceID}
• jaeger_compare_windows — GET /api/traces ×2
• jaeger_detect_anomalies — GET /api/traces ×2
• jaeger_predict_degradation — GET /api/traces
• jaeger_forecast_capacity — GET /api/traces

Credentials and setup notes

Configuration is passed through the environment: JAEGER_URL, JAEGER_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Installation

Installation goes through your MCP client rather than a global install: point it at jaeger-mcp on PyPI and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

Where it fits

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Jaeger's toolset — jaeger_list_services, jaeger_list_operations, jaeger_search_traces and 9 more — is a fair guide to whether it matches your workflow. It is maintained by mshegolev; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Worth knowing first

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 12 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Jaeger.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.