Back to MCP Servers
🧩

Query OTel traces across Jaeger, Tempo, Traceloop, Datadog, Sentry, X-Ray, New Relic, Honeycomb.

To add tracehub-mcp to Claude, run the install command below or copy the ready-made config for Claude Code, Claude Desktop, Cursor and VS Code further down. Restart your client after adding it and its tools show up in your next conversation. It needs 21 environment variables, listed below.

DevToolsData

Install

uvx tracehub-mcp@0.13.1

Environment variables

BACKEND_TYPESet in your MCP config
BACKEND_URLSet in your MCP config
BACKEND_API_KEYSet in your MCP config
BACKEND_AWS_REGIONSet in your MCP config
BACKEND_NEWRELIC_ACCOUNT_IDSet in your MCP config
BACKEND_HONEYCOMB_DATASETSet in your MCP config
BACKEND_APP_KEYSet in your MCP config
BACKEND_TEMPO_INSTANCE_IDSet in your MCP config
BACKEND_SENTRY_ORGSet in your MCP config
BACKEND_SENTRY_PROJECTSet in your MCP config
BACKEND_ENVIRONMENTSSet in your MCP config
BACKEND_TIMEOUTSet in your MCP config
BACKEND_MAX_RESPONSE_BYTESSet in your MCP config
LOG_LEVELSet in your MCP config
MAX_TRACES_PER_QUERYSet in your MCP config
SLOW_REQUEST_THRESHOLD_MSSet in your MCP config
QUERY_CACHE_TTL_SECONDSSet in your MCP config
QUERY_CACHE_MAX_ENTRIESSet in your MCP config
OTEL_EXPORTER_OTLP_ENDPOINTSet in your MCP config
OTEL_SERVICE_NAMESet in your MCP config
MCP_INCLUDE_ARGS_IN_SPANSSet in your MCP config

Install with your client

Terminal
claude mcp add tracehub --env BACKEND_TYPE=<YOUR_BACKEND_TYPE> --env BACKEND_URL=<YOUR_BACKEND_URL> --env BACKEND_API_KEY=<YOUR_BACKEND_API_KEY> --env BACKEND_AWS_REGION=<YOUR_BACKEND_AWS_REGION> --env BACKEND_NEWRELIC_ACCOUNT_ID=<YOUR_BACKEND_NEWRELIC_ACCOUNT_ID> --env BACKEND_HONEYCOMB_DATASET=<YOUR_BACKEND_HONEYCOMB_DATASET> --env BACKEND_APP_KEY=<YOUR_BACKEND_APP_KEY> --env BACKEND_TEMPO_INSTANCE_ID=<YOUR_BACKEND_TEMPO_INSTANCE_ID> --env BACKEND_SENTRY_ORG=<YOUR_BACKEND_SENTRY_ORG> --env BACKEND_SENTRY_PROJECT=<YOUR_BACKEND_SENTRY_PROJECT> --env BACKEND_ENVIRONMENTS=<YOUR_BACKEND_ENVIRONMENTS> --env BACKEND_TIMEOUT=<YOUR_BACKEND_TIMEOUT> --env BACKEND_MAX_RESPONSE_BYTES=<YOUR_BACKEND_MAX_RESPONSE_BYTES> --env LOG_LEVEL=<YOUR_LOG_LEVEL> --env MAX_TRACES_PER_QUERY=<YOUR_MAX_TRACES_PER_QUERY> --env SLOW_REQUEST_THRESHOLD_MS=<YOUR_SLOW_REQUEST_THRESHOLD_MS> --env QUERY_CACHE_TTL_SECONDS=<YOUR_QUERY_CACHE_TTL_SECONDS> --env QUERY_CACHE_MAX_ENTRIES=<YOUR_QUERY_CACHE_MAX_ENTRIES> --env OTEL_EXPORTER_OTLP_ENDPOINT=<YOUR_OTEL_EXPORTER_OTLP_ENDPOINT> --env OTEL_SERVICE_NAME=<YOUR_OTEL_SERVICE_NAME> --env MCP_INCLUDE_ARGS_IN_SPANS=<YOUR_MCP_INCLUDE_ARGS_IN_SPANS> -- uvx tracehub-mcp@0.13.1

Run this in a terminal to add the server to Claude Code.

What this does

tracehub-mcp exposes a set of tools to Claude over the Model Context Protocol. After you add it to claude_desktop_config.json (snippet above) and restart Claude Desktop, those tools become callable inside any conversation.

Requirements

This server needs the following environment variables to be set before it can run:

BACKEND_TYPE
BACKEND_URL
BACKEND_API_KEY
BACKEND_AWS_REGION
BACKEND_NEWRELIC_ACCOUNT_ID
BACKEND_HONEYCOMB_DATASET
BACKEND_APP_KEY
BACKEND_TEMPO_INSTANCE_ID
BACKEND_SENTRY_ORG
BACKEND_SENTRY_PROJECT
BACKEND_ENVIRONMENTS
BACKEND_TIMEOUT
BACKEND_MAX_RESPONSE_BYTES
LOG_LEVEL
MAX_TRACES_PER_QUERY
SLOW_REQUEST_THRESHOLD_MS
QUERY_CACHE_TTL_SECONDS
QUERY_CACHE_MAX_ENTRIES
OTEL_EXPORTER_OTLP_ENDPOINT
OTEL_SERVICE_NAME
MCP_INCLUDE_ARGS_IN_SPANS

Set these via the env object in your MCP config (see claude_desktop_config.json snippet above).

Frequently asked questions

How do I install tracehub-mcp?

Run the Claude Code command in the install section to add tracehub-mcp to Claude Code, or copy the ready-made config for your client from the install section on this page. Restart your client afterwards and the tools appear in your next conversation.

Which clients work with tracehub-mcp?

This page carries setup and config for Claude Code, Claude Desktop, Cursor and VS Code. Any other MCP client that accepts a standard server config can connect to tracehub-mcp as well.

Does tracehub-mcp need an API key?

Yes. Before it can run, set these environment variables: BACKEND_TYPE, BACKEND_URL, BACKEND_API_KEY, BACKEND_AWS_REGION, BACKEND_NEWRELIC_ACCOUNT_ID, BACKEND_HONEYCOMB_DATASET, BACKEND_APP_KEY, BACKEND_TEMPO_INSTANCE_ID, BACKEND_SENTRY_ORG, BACKEND_SENTRY_PROJECT, BACKEND_ENVIRONMENTS, BACKEND_TIMEOUT, BACKEND_MAX_RESPONSE_BYTES, LOG_LEVEL, MAX_TRACES_PER_QUERY, SLOW_REQUEST_THRESHOLD_MS, QUERY_CACHE_TTL_SECONDS, QUERY_CACHE_MAX_ENTRIES, OTEL_EXPORTER_OTLP_ENDPOINT, OTEL_SERVICE_NAME, MCP_INCLUDE_ARGS_IN_SPANS. They go in the env block of your MCP config.

Imported from the Official MCP Registry. The details above come from the registry entry; the maker can claim this listing to correct them, add docs, and see its traffic.

Is this your MCP server?

Claim this listing to see its traffic, fix details yourself, and skip the review queue on future updates.

Listed on clauderules.net

Add this badge to your README

Show visitors this server is listed in the ClaudeRules directory. The badge links straight to this listing.

Markdown
[![Listed on clauderules.net](https://clauderules.net/api/badge/io-github-mcpsmiths-tracehub-mcp)](https://clauderules.net/mcp/io-github-mcpsmiths-tracehub-mcp)
HTML
<a href="https://clauderules.net/mcp/io-github-mcpsmiths-tracehub-mcp" target="_blank" rel="noopener noreferrer"><img src="https://clauderules.net/api/badge/io-github-mcpsmiths-tracehub-mcp" alt="Listed on clauderules.net" /></a>