Tracehub MCP runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 17 Sep 2026.
Query OpenTelemetry traces from LLM apps across Jaeger, Tempo, Traceloop, Datadog, and Sentry.
Today is the operative word: we check Tracehub MCP every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add tracehub-mcp -- uvx tracehub-mcp
{
"mcpServers": {
"tracehub-mcp": {
"args": [
"tracehub-mcp"
],
"command": "uvx"
}
}
}
[mcp_servers.tracehub-mcp]
command = "uvx"
args = ["tracehub-mcp"]
{
"mcpServers": {
"tracehub-mcp": {
"args": [
"tracehub-mcp"
],
"command": "uvx"
}
}
}
{
"mcpServers": {
"tracehub-mcp": {
"args": [
"tracehub-mcp"
],
"command": "uvx"
}
}
}
This one needs environment variables set before it will start:
BACKEND_TYPE (Which observability backend to query.), BACKEND_URL (Backend API endpoint, e.g. http://localhost:16686 for Jaeger or https://api.datadoghq.com for Datadog.), BACKEND_API_KEY (API key or auth token. Required for Traceloop, Datadog, and Sentry; not used by Jaeger or Tempo.), BACKEND_APP_KEY (Datadog Application key, required in addition to BACKEND_API_KEY for the Datadog backend only.), BACKEND_TEMPO_INSTANCE_ID (Grafana Cloud stack/instance ID, used with BACKEND_API_KEY for Basic Auth (Tempo backend only, required for Grafana Cloud-hosted Tempo, not needed for self-hosted Tempo).), BACKEND_SENTRY_ORG (Sentry organization slug, required for the Sentry backend only.), BACKEND_SENTRY_PROJECT (Sentry project slug, optional for the Sentry backend - narrows queries to one project.), BACKEND_ENVIRONMENTS (Comma-separated environments for the Traceloop backend only.), BACKEND_TIMEOUT (Request timeout in seconds.), LOG_LEVEL (Logging level.), MAX_TRACES_PER_QUERY (Maximum traces validated per query (1-1000).), SLOW_REQUEST_THRESHOLD_MS (Logs a WARNING for any backend request slower than this, independent of LOG_LEVEL. Unset disables slow-request logging.), OTEL_EXPORTER_OTLP_ENDPOINT (Enables opt-in OTel self-instrumentation of tool calls when set. Unset means zero overhead - no TracerProvider is configured and no middleware is registered.), OTEL_SERVICE_NAME (Service name reported in self-instrumentation spans, only used when OTEL_EXPORTER_OTLP_ENDPOINT is set.), MCP_INCLUDE_ARGS_IN_SPANS (Include tool call arguments/results as OTel span attributes when self-instrumentation is enabled. Off by default since they may contain sensitive data.).
The author declared them in the registry entry; get the values from the project itself.
Access New Relic observability data through MCP - query metrics, logs, traces, entities, and more
MCP server for querying Foxhound traces from Claude Code, Cursor, and other MCP clients
Open-source agent that observes and fixes your application. Query logs, traces, metrics, incidents.
Query application logs, traces, and metrics from your AI coding assistant via Foam's MCP server.
Query Honeycomb observability data: traces, events, metrics, SLOs, triggers, and boards.
Full Datadog API access: monitors, logs, metrics, traces, dashboards, and observability tools
Query logs from Graylog: get streams, search messages, aggregate, and get full data.
Track and query EzStat metrics from Claude, Cursor, or any MCP agent. StatHat-compatible.
Answers built from our own checks of this server.