MCP Tools DirectoryAbout this integration
Jaeger MCP — search traces, inspect spans, map service dependencies (read-only).
- Transport
- stdio
- Authentication
- unknown
- Initial setup
- credentials
- Runtime
- unattended
- Evidence
- documented
- Version
- 0.1.1
- Package
- jaeger-mcp
- Last compatibility test
- Not independently tested
Connect your agent
jaeger-mcpPublisher documentation and executable manifest were reviewed. The package and Jaeger endpoint were not executed or independently security-audited. Publisher read-only and forecasting claims are documented, not runtime-verified here.
Capabilities: Search and inspect Jaeger traces, Compare traces and time windows, Analyze spans, dependencies, anomalies, and critical paths, Produce publisher-described performance and capacity forecasts
Connected profiles
Additional details
io.github.mshegolev/jaeger-mcp
Source ↗ · Checked 2026-09-170.1.1
Source ↗ · Checked 2026-09-17CC0-1.0; package licenses are separate
Source ↗ · Checked 2026-09-17pypi
Source ↗ · Checked 2026-09-17JAEGER_URL
Source ↗ · Checked 2026-09-17jaeger-mcp
Source ↗ · Checked 2026-09-190.6.3
Source ↗ · Checked 2026-09-19The Python console script runs as a stdio MCP server and uses a required Jaeger Query service URL with bounded timeout, retry, and cache settings.
Source ↗ · Checked 2026-09-19Authentication is deployment-dependent: the publisher documents bearer token, HTTP Basic authentication, or no authentication. The native taxonomy has no accurate mixed/basic value, so authentication remains unknown rather than being mislabeled OAuth.
Source ↗ · Checked 2026-09-19Local stdio launch uses jaeger-mcp or uvx jaeger-mcp and requires JAEGER_URL; optional token or Basic-auth environment variables match the Jaeger deployment.
Source ↗ · Checked 2026-09-19Publisher documentation reviewed; package and integration endpoint not executed or independently security-audited.
Source ↗ · Checked 2026-09-19