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
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.
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
- GitHub forks
- 24
- GitHub stars
- 205
- Days to a first reply on issues
- 361
- Open issues
- 7
- Releases in the last 90 days
- 0
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:16686Tools exposed
search_tracessearch_spansget_traceget_llm_usagelist_servicesfind_errorslist_llm_modelsget_llm_model_statsget_llm_expensive_tracesget_llm_slow_tracesBACKEND_TYPEBACKEND_URLBACKEND_API_KEYBACKEND_TIMEOUTLOG_LEVELMAX_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
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
204 to 205
Health and security
Is traceloop/opentelemetry-mcp-server looked after, and what do its setup files show
Health score
45 out of 100
| Part | Points | What we saw |
|---|---|---|
| Recent activity | 30 of 30 | Last push 8 days ago |
| Releases | 0 of 15 | 0 releases in 90 days |
| Issue replies | 0 of 20 | First reply in 361 days (median) |
| Maintainer | 15 of 15 | Owned by an organisation |
| Official source | 0 of 20 | Community server |
Alternatives
Alternatives to traceloop/opentelemetry-mcp-server
| Record | Type | How we know | Checked |
|---|---|---|---|
| 98lukehall/renoun-mcpAlternative to this | MCP server | Matched from the listing text | |
| Agent Cost LogAlternative to this | MCP server | Matched from the listing text | |
| Agent ObservabilityAlternative to this | MCP server | Matched from the listing text |
Compare
Compare traceloop/opentelemetry-mcp-server side by side
Sources
Where this comes from
- GitHubRegistry
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.
Open-source & AI alternatives
Swap-in tools that solve the same job. Weigh the trade-offs before you commit.
98lukehall/renoun-mcp
Various
Structural observability for AI conversations. Detects loops, stuck states, breakthroughs, and convergence patterns across 17 channels without analyzing content. MCP server + REST
Agent Cost Log
botrecipe
Agent Cost Log: cost log for AI agents: cost per run, per tool, per model and per day from one call or an OpenTelemetry export
Agent Observability
blueskylineassets
Agent observability: structured logging, cost tracking, and compliance audit trails
Pairs with
Other entries in the index that connect to this one. Click through to see the chain.
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.