MCP Tools Directory
← Browse integrations

Developer tools

io.github.mcpsmiths/tracehub-mcp

Free account · sign-in required

Contact io.github.mcpsmiths/tracehub-mcp

Loading secure sign-in…

Tools for autonomous AI agents

Official website ↗

About this integration

Query OpenTelemetry traces from LLM apps across Jaeger, Tempo, Traceloop, Datadog, and Sentry.

Transport
stdio
Authentication
unknown
Initial setup
credentials
Runtime
unattended
Evidence
documented
Version
0.8.1
Package
tracehub-mcp
Last compatibility test
Not independently tested

Connect your agent

tracehub-mcp

Publisher README and Python manifest reviewed. Authentication varies by selected backend, and the native taxonomy cannot express the documented mixture of no-auth local services, API-key services, key pairs, Basic Auth, tokens, and AWS credential-chain authentication. Backend data is explicitly untrusted. The package and backends were not executed or independently security-audited.

Repository ↗Authentication & capability evidence ↗

Capabilities: Search and hydrate OpenTelemetry traces and spans, Analyze model token use, latency, errors, and cost, Compare time windows and investigate cost or error spikes, Query multiple documented observability backends

Connected profiles

Developer toolsindustries

Additional details

Registry identifier

io.github.mcpsmiths/tracehub-mcp

Source ↗ · Checked 2026-09-17
Published version

0.8.1

Source ↗ · Checked 2026-09-17
Metadata license

CC0-1.0; package licenses are separate

Source ↗ · Checked 2026-09-17
Package ecosystem

pypi

Source ↗ · Checked 2026-09-17
Required configuration names

BACKEND_TYPE, BACKEND_URL

Source ↗ · Checked 2026-09-17
Source artifact

tracehub-mcp

Source ↗ · Checked 2026-09-19
Source manifest version

0.11.0

Source ↗ · Checked 2026-09-19
Unattended configuration

The documented default is a single-process stdio server launched with uvx; backend type and URL are supplied non-interactively through environment variables.

Source ↗ · Checked 2026-09-19
Authentication and prerequisites

Authentication is backend-specific: local Jaeger can require none, several cloud backends require API keys or tokens, Datadog also requires an application key, Tempo can use Basic Auth, and X-Ray uses the AWS credential chain; classified unknown because no single native value is accurate.

Source ↗ · Checked 2026-09-19
Connection configuration

Local MCP configuration runs uvx tracehub-mcp with BACKEND_TYPE and BACKEND_URL in the environment; the existing catalog stdio connection and null endpoint are preserved.

Source ↗ · Checked 2026-09-19
Review scope

Publisher documentation reviewed; package and integration endpoint not executed or independently security-audited.

Source ↗ · Checked 2026-09-19