Independent by design · no pay-to-rank placements  · How we evaluate tools →
Anclum Submit
T

traceloop/opentelemetry-mcp-server

Query traces in Jaeger, Tempo and other backends

Before you install: a copy-paste command is available · no license recorded · link reachable

Apache-2.0 license
View on GitHub ↗Link checked 2026-11-12 · HTTP 200 · opens the vendor's own site
Install & config
  1. Copy the command above
  2. Paste it as one entry under mcpServers in claude_desktop_config.json — local servers take command + args (example: clients)
  3. Restart your client
Client config (built from the install command this repo gives)
{
  "mcpServers": {
    "traceloop-opentelemetry-mcp-server": {
      "command": "uvx",
      "args": ["opentelemetry-mcp"]
    }
  }
}

Parsed from the README we fetched on 2026-11-06; we have not executed it.

command/args come from the install command the repository states. When it is ambiguous, the project README wins.
VS Code (.vscode/mcp.json - the key is servers)
{
  "servers": {
    "traceloop-opentelemetry-mcp-server": {
      "command": "uvx",
      "args": ["opentelemetry-mcp"]
    }
  }
}
Same server, but VS Code keeps it under <code>servers</code>.
Claude Code (command line)
claude mcp add --transport stdio traceloop-opentelemetry-mcp-server -- uvx opentelemetry-mcp
Claude Code does not read a config file; add the server with this command.
Key names differ by client: Clients & CLI
Source
collected from the abordage/awesome-mcp list · type: MCP server
Harvest history
first seen 2026-11-05 · last seen 2026-11-14 · seen 10× · listed by 10 sources
Score
score 1,003 · 10 sources · mcp
Install
uvx opentelemetry-mcp
FAQ (answers come from our records)
How do I install it?
The repository provides this install command: uvx opentelemetry-mcp. It comes from the repository itself; we cannot guarantee it runs as-is in your client.
Who is it for?
We filed it under these tags: MCP 服务. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
first catalogued 2026-11-05;last seen 2026-11-14。There is no official certification or quality rating here — we record sources and dates only.
Third-party quality signals

# OpenTelemetry MCP Server

以下摘录自该仓库的 README(片段) · 在 GitHub 读完整 README →

Query and analyze LLM traces with AI assistance. Ask Claude to find expensive API calls, debug errors, compare model performance, or track token usage—all from your IDE.
An MCP (Model Context Protocol) server that connects AI assistants to OpenTelemetry trace backends (Jaeger, Tempo, Traceloop), with specialized support for LLM observability through OpenLLMetry semantic conventions.
See it in action:
https://github.com/user-attachments/assets/e2106ef9-0a58-4ba0-8b2b-e114c0b8b4b9
## Table of Contents
Quick Start
Installation
Features
Configuration
Tools Reference
Example Queries
Common Workflows
Troubleshooting
Development
Support
## Quick Start
No installation required! Configure your client to run the server directly from PyPI:
json
// Add to claudedesktopconfig.json:
"mcpServers": {
"opentelemetry-mcp": {
"command": "pipx",
"args": ["run", "opentelemetry-mcp"],
"env": {
"BACKENDTYPE": "jaeger",
"BACKENDURL": "http://localhost:16686"
Or use uvx (alternative):
json
"mcpServers": {
"opentelemetry-mcp": {
"command": "uvx",
"args": ["opentelemetry-mcp"],
"env": {
"BACKENDTYPE": "jaeger",
"BACKENDURL": "http://localhost:16686"
That's it! Ask Claude: "Show me traces with errors from the last hour"
## Installation
### For End Users (Recommended)
bash
# Run without installing (recommended)
pipx run opentelemetry-mcp --backend jaeger --url http://localhost:16686
# Or with uvx
uvx opentelemetry-mcp --backend jaeger --url http://localhost:16686
This approach:
✅ Always uses the latest version
✅ No global installation needed
✅ Isolated environment automatically
✅ Works on all platforms
### Per Client Integration
Claude Desktop
Configure the MCP server in your Claude Desktop config file:
macOS: ~/Library/Application Support/Claude/claudedesktopconfig.json
Windows: %APPDATA%\Claude\claudedesktopconfig.json
Using pipx (recommended):
json
"mcpServers": {
"opentelemetry-mcp": {
"command": "pipx",
"args": ["run", "opentelemetry-mcp"],
"env": {
"BACKENDTYPE": "jaeger",
"BACKENDURL": "http://localhost:16686"
Using uvx (alternative):
json
"mcpServers": {
"opentelemetry-mcp": {
"command": "uvx",
"args": ["opentelemetry-mcp"],
"env": {
"BACKENDTYPE": "jaeger",
"BACKENDURL": "http://localhost:16686"
For Traceloop backend:
json
"mcpServers": {
"opentelemetry-mcp": {
"command": "pipx",
"args": ["run", "opentelemetry-mcp"],
"env": {
"BACKENDTYPE": "traceloop",
"BACKENDURL": "https://api.traceloop.com",
"BACKENDAPIKEY": "yourtraceloopapikeyhere"
Using the repository instead of pipx?
If you're developing locally with the cloned repository, use one of these configurations:
Option 1: Wrapper script (easy backend switching)
json
"mcpServers": {
"opentelemetry-mcp": {
"command": "/absolute/path/to/opentelemetry-mcp-server/startlocally.sh"
Option 2: UV directly (for multiple backends)
json
"mcpServers": {
"opentelemetry-mcp-jaeger": {
"command": "uv",
"args": [
"--directory",
"/absolute/path/to/opentelemetry-mcp-server",
"run",
"opentelemetry-mcp"
],
"env": {
"BACKENDTYPE": "jaeger",
"BACKENDURL": "http://localhost:16686"
Claude Code
Claude Code works with MCP servers configured in your Claude Desktop config. Once configured above, you can use the server with Claude Code CLI:
bash
# Verify the server is available
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[![Listed on Anclum](https://anclum.com/badge/listed.svg)](https://anclum.com/en/s/traceloop-opentelemetry-mcp-server/)
Source
awesome · https://github.com/traceloop/opentelemetry-mcp-server
Browse by field
MCP servers
Listed by
10 independent sources
added
today

More like this

All 6,229 →

Filed under

Every tag opens the full list for that filter. Counts are the live catalogue figures.

Browse all fields →

← Back to index