Tracehub-mcp Server

Tracehub-mcp is an MCP integration. Query OTel traces across Jaeger, Tempo, Traceloop, Datadog, Sentry, X-Ray, New Relic, Honeycomb.

Packages and local setup

The published pypi package is tracehub-mcp, version 0.12.2. Its declared MCP transport is stdio.

The package declares BACKEND_TYPE (required): Which observability backend to query.; BACKEND_URL (required): Backend API endpoint, e.g. http://localhost:16686 for Jaeger, https://api.datadoghq.com for Datadog, https://api.newrelic.com/graphql for New Relic, or https://api.honeycomb.io for Honeycomb. For the X-Ray backend this is decorative only (e.g. https://xray.us-east-1.amazonaws.com) - never dereferenced for a live request.; BACKEND_API_KEY: API key or auth token. Required for Traceloop, Datadog, Sentry, New Relic, and Honeycomb; not used by Jaeger, Tempo, or X-Ray. For New Relic this must be a User API key, not an Ingest or License key; for Honeycomb this must be a Configuration Key, not an Ingest or Management key.; BACKEND_AWS_REGION: AWS region, e.g. us-east-1. Required for the X-Ray backend only - X-Ray authenticates via boto3's standard AWS credential chain, not BACKEND_API_KEY.; BACKEND_NEWRELIC_ACCOUNT_ID: New Relic account ID, required for the New Relic backend only - NerdGraph queries are user-scoped, not account-scoped, so this identifies which account's data to read.; BACKEND_HONEYCOMB_DATASET: Honeycomb dataset slug, required for the Honeycomb backend only - the Query Data API is dataset-scoped.; 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..

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository. This profile uses version 0.12.2 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related monitoring & observability MCP servers for tools that cover the same kind of work.