InnerVault

tracehub-mcp

Stale Official MCP Registry, io.github.mcpsmiths

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

Open the source (opens github.com) https://github.com/mcpsmiths/tracehub-mcp

Before you use it

  • Runs on your computer with your permissions. Read what it can do before connecting it to an agent.
  • Needs credentials: BACKEND_API_KEY, BACKEND_APP_KEY. Use a key with the least access you can.

What it is

MCP servers from io.github.mcpsmiths.

The problem it solves and who it suits haven't been reviewed by InnerVault. The description above is the source's own.

How to get it

pypi package (stdio)

tracehub-mcp@0.13.1

From the server's entry in the official MCP Registry

Settings it asks for

  • 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…
  • BACKEND_API_KEY secret · 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…
  • 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…
  • BACKEND_HONEYCOMB_DATASET · Honeycomb dataset slug, required for the Honeycomb backend only - the Query Data API is dataset-scoped.
  • BACKEND_APP_KEY secret · 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…
  • 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.

Related

  1. GitHub MCP server

    MCP servers

    GitHub's official MCP server. It lets an agent read and work with repositories, issues and pull requests.

    Hand-checked InnerVault (hand-checked), GitHub 34.3k ★MIT

    https://api.githubcopilot.com/mcp/
  2. Apify MCP server

    MCP servers

    Lets an agent run Apify's ready-made scrapers to pull data from websites, search engines, maps and social platforms.

    Hand-checked InnerVault (hand-checked), Apify 16.0k ★MIT

  3. Official MCP Registry

    MCP servers

    The MCP project's own registry of public MCP servers, so you can look for a connector before building one.

    Hand-checked InnerVault (hand-checked), MCP project Moving from MIT to Apache-2.0

  4. MCP reference servers

    MCP servers

    Small example servers from the MCP project (filesystem, git, fetch, memory and more) that show how MCP works.

    Hand-checked InnerVault (hand-checked), MCP project Moving from MIT to Apache-2.0

  5. Anthropic's guide to adding MCP servers to Claude Code, with examples of local and remote servers.

    Hand-checked InnerVault (hand-checked), Anthropic Anthropic documentation

  6. Playwright MCP

    MCP servers

    Lets an agent drive a real browser: open pages, click, fill in forms and read what's on screen.

    Hand-checked InnerVault (hand-checked), Microsoft Apache-2.0

    claude mcp add playwright npx @playwright/mcp@latest