Server data from the Official MCP Registry
Jaeger MCP — search traces, inspect spans, map service dependencies (read-only).
Jaeger MCP — search traces, inspect spans, map service dependencies (read-only).
Valid MCP server (1 strong, 3 medium validity signals). 12 known CVEs in dependencies (0 critical, 6 high severity) Package registry verified. Imported from the Official MCP Registry.
7 files analyzed · 13 issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
This plugin requests these system permissions. Most are normal for its category.
Unverified package source
We couldn't verify that the installable package matches the reviewed source code. Proceed with caution.
Set these up before or after installing:
Environment variable: JAEGER_URL
Environment variable: JAEGER_TOKEN
Environment variable: JAEGER_USERNAME
Environment variable: JAEGER_PASSWORD
Environment variable: JAEGER_SSL_VERIFY
Add this to your MCP configuration file:
{
"mcpServers": {
"io-github-mshegolev-jaeger-mcp": {
"env": {
"JAEGER_URL": "your-jaeger-url-here",
"JAEGER_TOKEN": "your-jaeger-token-here",
"JAEGER_PASSWORD": "your-jaeger-password-here",
"JAEGER_USERNAME": "your-jaeger-username-here",
"JAEGER_SSL_VERIFY": "your-jaeger-ssl-verify-here"
},
"args": [
"jaeger-mcp"
],
"command": "uvx"
}
}
}From the project's GitHub README.
MCP server for Jaeger distributed tracing. Give Claude (or any MCP-capable agent) read access to your trace data — search traces, inspect spans, map service dependencies — without leaving the conversation.
The existing Jaeger integrations require a running UI or custom scripts. This server:
readOnlyHint: true — zero risk of modifying trace data.structuredContent) for programmatic use + Markdown (content) for human-readable display.| Tool | Endpoint | Description |
|---|---|---|
jaeger_list_services | GET /api/services | List all instrumented services |
jaeger_list_operations | GET /api/services/{service}/operations | List operation names for a service |
jaeger_search_traces | GET /api/traces | Search traces with rich filters |
jaeger_get_trace | GET /api/traces/{traceID} | Full trace detail with span tree |
jaeger_get_dependencies | GET /api/dependencies | Service-to-service call graph |
pip install jaeger-mcp
Or run directly without installing:
uvx jaeger-mcp
All configuration is via environment variables:
| Variable | Required | Default | Description |
|---|---|---|---|
JAEGER_URL | Yes | — | Jaeger query service URL, e.g. https://jaeger.example.com |
JAEGER_TOKEN | No | — | Bearer token (takes precedence over Basic auth) |
JAEGER_USERNAME | No | — | HTTP Basic auth username |
JAEGER_PASSWORD | No | — | HTTP Basic auth password |
JAEGER_SSL_VERIFY | No | true | Set false for self-signed certificates |
Copy .env.example to .env and fill in your values.
Add to your MCP config (claude_desktop_config.json or .claude/mcp.json):
{
"mcpServers": {
"jaeger": {
"command": "jaeger-mcp",
"env": {
"JAEGER_URL": "https://jaeger.example.com",
"JAEGER_TOKEN": "your-token-here"
}
}
}
}
Or with uvx (no install required):
{
"mcpServers": {
"jaeger": {
"command": "uvx",
"args": ["jaeger-mcp"],
"env": {
"JAEGER_URL": "https://jaeger.example.com"
}
}
}
}
docker run --rm -e JAEGER_URL=https://jaeger.example.com jaeger-mcp
Once configured, ask Claude:
order-service from the last hour"GET /checkout"abcdef1234567890?"postgres most frequently?"jaeger_list_servicesReturns all service names Jaeger has seen. Start here when you don't know which services are instrumented. Output is capped at 500 services with a truncation hint.
jaeger_list_operationsReturns all operation names for a given service (e.g. HTTP route names, gRPC method names). Use to discover valid operation names before filtering jaeger_search_traces.
jaeger_search_tracesThe main search tool. Filters:
service (required) — service name from jaeger_list_servicesoperation — narrow to a specific endpointtags — JSON string of tag filters, e.g. {"http.status_code":"500"} or {"error":"true"}start / end — time range in microseconds UTCmin_duration / max_duration — duration strings like "100ms", "1.5s", "2m"limit — default 20, max 1500Returns trace summaries with trace_id, duration_us, span_count, service_count, root_operation, errors_count.
jaeger_get_traceFull trace detail. Accepts a trace_id (hex string, 16-32 chars) and returns:
Error spans are identified by tags["error"] = "true".
jaeger_get_dependenciesService topology graph. Returns directed edges (parent → child) with call_count. Use lookback_hours (default 24, max 720) to control the window.
requests.Session with connection pooling.trust_env = False to bypass environment proxies (Jaeger is typically an internal service).jaeger_search_traces passes limit directly to Jaeger — avoid requesting more traces than needed.jaeger_get_trace fetches the full trace in one call — large traces (thousands of spans) may be slow.jaeger_get_dependencies aggregates over the full lookback window; large windows may be slow on busy clusters.git clone https://github.com/mshegolev/jaeger-mcp
cd jaeger-mcp
pip install -e '.[dev]'
pytest tests/ -v
ruff check src tests
ruff format src tests
MIT — see LICENSE.
Be the first to review this server!
by Modelcontextprotocol · Developer Tools
Web content fetching and conversion for efficient LLM usage
by Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
by Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
by mcp-marketplace · Developer Tools
Create, build, and publish Python MCP servers to PyPI — conversationally.