Enterprise DNAEnterprise DNA

MCP Servers

traceloop/opentelemetry-mcp-server

Unified MCP server for querying OpenTelemetry traces across multiple backends (Jaeger, Tempo, Traceloop, etc.), enabling AI agents to analyze distributed traces for automated debug

Our verdict

Not reviewed yet

We have not reviewed traceloop/opentelemetry-mcp-server yet

No one at Enterprise DNA has checked this listing against its sources. The description comes from public listings gathered automatically. Any fact below shows where it came from and when it was last checked.

How we review records

From the listing

About traceloop/opentelemetry-mcp-server

This is a Model Context Protocol server that provides a unified interface for querying OpenTelemetry traces from multiple backends such as Jaeger, Tempo, and Traceloop. It enables AI agents to programmatically access distributed trace data for automated debugging and observability analysis.

Best for

Developers building AI agents for observability and distributed tracing

Use cases

  • Automated root cause analysis from trace data
  • AI-driven debugging of distributed system failures
  • Unified trace querying across different observability backends

Notes

188 stars on GitHub. Last updated 2026-04-20. Licensed Apache-2.0.

Pros

  • Connects to multiple OpenTelemetry backends through a single MCP interface
  • Designed specifically for AI agents to integrate with trace data
  • Open source with a Python codebase for easy customization

Cons

  • Relies on existing OpenTelemetry instrumentation in the target systems
  • Requires an MCP compatible AI agent to leverage the server
  • Relatively small community with 188 stars on GitHub

Key facts

What we have checked

Days since the last commit
8
Checked GitHub
GitHub forks
24
Checked GitHub
GitHub stars
205
Checked GitHub
Days to a first reply on issues
361
Checked GitHub
Open issues
7
Checked GitHub
Releases in the last 90 days
0
Checked GitHub

Each value shows when we last confirmed it and where it came from. Values we have not confirmed are left out, never guessed.

How to use

How to set it up

As the listing publishes it. We have not run this install.

Install

uvx opentelemetry-mcp --backend jaeger --url http://localhost:16686

Tools exposed

  • search_traces
  • search_spans
  • get_trace
  • get_llm_usage
  • list_services
  • find_errors
  • list_llm_models
  • get_llm_model_stats
  • get_llm_expensive_traces
  • get_llm_slow_traces
  • BACKEND_TYPE
  • BACKEND_URL
  • BACKEND_API_KEY
  • BACKEND_TIMEOUT
  • LOG_LEVEL
  • MAX_TRACES_PER_QUERY

Clients the listing names (not checked here)

Claude Desktop, Claude Code, Cursor, Windsurf, ChatGPT

Example client config

{
  "mcpServers": {
    "opentelemetry-mcp": {
      "command": "pipx",
      "args": [
        "run",
        "opentelemetry-mcp"
      ],
      "env": {
        "BACKEND_TYPE": "jaeger",
        "BACKEND_URL": "http://localhost:16686"
      }
    }
  }
}

Install

Add traceloop/opentelemetry-mcp-server to your client

Not verified yet

No install recipe yet. We write one for Claude Code, Claude Desktop, Cursor, VS Code, Codex and ChatGPT when the server is in the official MCP registry with a package or remote address we can use.

Until then, follow the project's own README, or the setup the listing publishes under How to set it up.

Works with

What traceloop/opentelemetry-mcp-server connects to

No confirmed connections yet. A product appears here when the server's registry name, repo, homepage or name ties it to that product, and a client appears when we have an install recipe for it.

Stars and usage

How traceloop/opentelemetry-mcp-server is growing

GitHub stars

204 to 205

stars. 31 Oct 2026 to 13 Nov 2026, 3 readings.

Source: GitHub. Checked .

Health and security

Is traceloop/opentelemetry-mcp-server looked after, and what do its setup files show

Health score

45 out of 100

Does someone look after this repository? It does not say the code is good or safe. Worked out from GitHub signals checked . How it is worked out

PartPointsWhat we saw
Recent activity30 of 30Last push 8 days ago
Releases0 of 150 releases in 90 days
Issue replies0 of 20First reply in 361 days (median)
Maintainer15 of 15Owned by an organisation
Official source0 of 20Community server

Alternatives

Alternatives to traceloop/opentelemetry-mcp-server

RecordTypeHow we knowChecked
98lukehall/renoun-mcpAlternative to thisMCP serverMatched from the listing text
Agent Cost LogAlternative to thisMCP serverMatched from the listing text
Agent ObservabilityAlternative to thisMCP serverMatched from the listing text

Compare

Compare traceloop/opentelemetry-mcp-server side by side

Sources

Where this comes from

  • GitHubRegistry

    Checked · Days since the last commit, GitHub forks, GitHub stars, Days to a first reply on issues, Open issues, Releases in the last 90 days

A source shows what was published when we checked it. It does not certify security, performance or a working installation. Read our method.

Changelog

What changed

No changes recorded yet. Releases, price changes and deprecations appear here, with their dates, once we track them for this record.

Free 27-page guide

Get the free Developer’s Field Guide

A 27-page field guide to the AI coding workflow with Claude. Claude Code, MCP servers, the prompt patterns that work, and what to delegate. Free.

Enter your work email. We send it straight over, plus a few short notes worth knowing. Unsubscribe any time.

No spam. Unsubscribe any time.