Jaeger MCP — search traces, inspect spans, map service dependencies (read-only).
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"io-github-mshegolev-jaeger-mcp": {
"command": "<see-readme>",
"args": []
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Jaeger MCP — search traces, inspect spans, map service dependencies (read-only).
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
This server is missing a description. Tools and install config are also missing.If you've used it, help the community.
Add informationBe the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in maps
Verified cloud cost forecasting for AI agents. AWS, GCP, Azure pricing matrix.
Live Japan travel data: sakura, koyo, fruit picking, flowers & festivals. 1,700+ spots from JMC.
MCP server for METAR/TAF aviation weather data
I Ching hexagram analysis and geographic feng shui for Taiwan locations
MCP Security Weekly
Get CVE alerts and security updates for io.github.mshegolev/jaeger-mcp and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
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.