M
mcpsmiths/tracehub-mcp
★ 1·updated 2026-11-18
View on GitHub ↗Direct link · no redirect page
We have no copy-paste install command and no public remote endpoint, so we do not print a config. The step above is reference only, not a command we can vouch for. A made-up one is worse than none. How each client wires MCP up →
- Star count
- 1 ★ · mcpsmiths/tracehub-mcp · read from the GitHub search API · (checked 2026-11-19 20:00:48)
- Source
- collected from the punkpeye/awesome-mcp-servers list · type: MCP server
- Harvest history
- first seen 2026-11-18 · last seen 2026-11-20 · seen 3× · listed by 3 sources
- Score
- score 300 · 1 ★ · 3 sources · mcp
FAQ (answers come from our records)
Who is it for?
We filed it under these tags: MCP servers. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
mcpsmiths/tracehub-mcp;first catalogued 2026-11-18;last seen 2026-11-20。There is no official certification or quality rating here — we record sources and dates only.README excerpt (English, untranslated) · Read the full README on GitHub →
# tracehub-mcp
Excerpted from the repository README (abridged)
Also listed on the official MCP registry as io.github.mcpsmiths/tracehub-mcp (the registry's own ?search= endpoint can surface an outdated version first; this exact-name endpoint always reflects the current isLatest release), and on mcprush.
Give your AI assistant a direct line into your observability backend. tracehub-mcp is an MCP (Model Context Protocol) server that lets Claude, Cursor, Windsurf, Gemini CLI, or any MCP client query OpenTelemetry traces from your LLM/GenAI application and reason about them — find expensive calls, debug errors, compare model performance, track token usage — without you copy-pasting trace JSON into a chat window.
It speaks OpenTelemetry's gen_ai. semantic conventions natively, so it understands prompts, completions, token usage, and finish reasons as first-class concepts, not just generic span attributes.
tracehub-mcp started as a fork of traceloop/opentelemetry-mcp-server (Apache 2.0) — full attribution and fork history are in NOTICE. It's grown into an 8-backend, security-hardened server maintained independently under mcpsmiths; see What's Different From Upstream below for the parts that are new here.
## Table of Contents
Quick Start
Supported Backends
What's Different From Upstream
Installation
Configuration
Diagnostics
Security Considerations
Privacy Policy
MCP Client Setup
Tools Reference
Generic Filter System
Example Queries
Common Workflows
Development
Troubleshooting
Roadmap
License
Support
## Quick Start
tracehub-mcp is on PyPI. No install step needed — uvx fetches and runs it in one shot:
json
// claude_desktop_config.json
"mcpServers": {
"tracehub-mcp": {
"command": "uvx",
"args": ["tracehub-mcp"],
"env": {
"BACKEND_TYPE": "jaeger",
"BACKEND_URL": "http://localhost:16686"
Or from Claude Code directly:
bash
claude mcp add tracehub-mcp -e BACKEND_TYPE=jaeger -e BACKEND_URL=http://localhost:16686 -- uvx tracehub-mcp
That's it. Ask your assistant: _"Show me traces with errors from the last hour."_
See MCP Client Setup for Cursor, Windsurf, VS Code, and Gemini CLI, and Installation for pip/pipx/from-source alternatives.
## Supported Backends
Jaeger — local/self-hosted, the most common open-source trace backend. No auth required (a Bearer token can be sent via BACKEND_API_KEY; credentials embedded in BACKEND_URL are rejected).
Grafana Tempo — local or Grafana Cloud, TraceQL-native search.
Traceloop — cloud LLM observability platform, API-key auth.
Datadog — cloud APM, requires an API key and an Application key.
Sentry — cloud or self-hosted, requires an auth token and an organization slug.
AWS X-Ray — SigV4-signed via boto3, requires an AWS region and standard AWS credentials (not an API key). Because OTel span attributes land in unindexed X-Ray segment metadata by default (only annotations are queryable), native server-side filtering is narrower here than for the other backends — see the Backend Support Matrix.
New Relic — NerdGraph GraphQL API, requires a User API key (not an Ingest/License key) and an account ID. Built without a live account to verify against — see the New Relic setup section below and the module docstring in backends/newrelic.py for exactly which assumptions are unverified.
Give your AI assistant a direct line into your observability backend. tracehub-mcp is an MCP (Model Context Protocol) server that lets Claude, Cursor, Windsurf, Gemini CLI, or any MCP client query OpenTelemetry traces from your LLM/GenAI application and reason about them — find expensive calls, debug errors, compare model performance, track token usage — without you copy-pasting trace JSON into a chat window.
It speaks OpenTelemetry's gen_ai. semantic conventions natively, so it understands prompts, completions, token usage, and finish reasons as first-class concepts, not just generic span attributes.
tracehub-mcp started as a fork of traceloop/opentelemetry-mcp-server (Apache 2.0) — full attribution and fork history are in NOTICE. It's grown into an 8-backend, security-hardened server maintained independently under mcpsmiths; see What's Different From Upstream below for the parts that are new here.
## Table of Contents
Quick Start
Supported Backends
What's Different From Upstream
Installation
Configuration
Diagnostics
Security Considerations
Privacy Policy
MCP Client Setup
Tools Reference
Generic Filter System
Example Queries
Common Workflows
Development
Troubleshooting
Roadmap
License
Support
## Quick Start
tracehub-mcp is on PyPI. No install step needed — uvx fetches and runs it in one shot:
json
// claude_desktop_config.json
"mcpServers": {
"tracehub-mcp": {
"command": "uvx",
"args": ["tracehub-mcp"],
"env": {
"BACKEND_TYPE": "jaeger",
"BACKEND_URL": "http://localhost:16686"
Or from Claude Code directly:
bash
claude mcp add tracehub-mcp -e BACKEND_TYPE=jaeger -e BACKEND_URL=http://localhost:16686 -- uvx tracehub-mcp
That's it. Ask your assistant: _"Show me traces with errors from the last hour."_
See MCP Client Setup for Cursor, Windsurf, VS Code, and Gemini CLI, and Installation for pip/pipx/from-source alternatives.
## Supported Backends
Jaeger — local/self-hosted, the most common open-source trace backend. No auth required (a Bearer token can be sent via BACKEND_API_KEY; credentials embedded in BACKEND_URL are rejected).
Grafana Tempo — local or Grafana Cloud, TraceQL-native search.
Traceloop — cloud LLM observability platform, API-key auth.
Datadog — cloud APM, requires an API key and an Application key.
Sentry — cloud or self-hosted, requires an auth token and an organization slug.
AWS X-Ray — SigV4-signed via boto3, requires an AWS region and standard AWS credentials (not an API key). Because OTel span attributes land in unindexed X-Ray segment metadata by default (only annotations are queryable), native server-side filtering is narrower here than for the other backends — see the Backend Support Matrix.
New Relic — NerdGraph GraphQL API, requires a User API key (not an Ingest/License key) and an account ID. Built without a live account to verify against — see the New Relic setup section below and the module docstring in backends/newrelic.py for exactly which assumptions are unverified.
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/mcpsmiths-tracehub-mcp/)
- Source
- awesome · https://github.com/mcpsmiths/tracehub-mcp
- Browse by field
- MCP servers
- Traction
- 1 ★
- Listed by
- 3 independent sources
- added
- today
More MCP servers
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.