Skip to content
CosmosCLIChangelog
Context EnginePricingDocsBlog
CustomersCareersStatus PageTrust CenterSecurity
Talk to SalesSign in
Book demo

OpenTelemetry

Remote MCP·Local·STDIO

MCP server for OpenTelemetry trace backends (Jaeger, Tempo, Traceloop). Search traces, analyze spans, find errors, track LLM token usage, and compare model performance.

Good for:Trace analysisError debuggingLLM token trackingPerformance monitoring

Installation path

Open Augment→Go to Configuration→Select MCP Registry→Click "Add Server"

Choose Add Server, select Local MCP, use uvx as the command, pass opentelemetry-mcp as the argument, and set BACKEND_TYPE and BACKEND_URL.

Setup steps

  1. 01

    Install uv

    Install uv with brew install uv or pipx install uv.

  2. 02

    Open Add Server

    Configuration → MCP Registry → Add Server in Cosmos.

  3. 03

    Pick the Local MCP tab

  4. 04

    Set the command

    Command

    uvx
  5. 05

    Add the arguments

    Args

    opentelemetry-mcp
  6. 06

    Set environment variables

    Set BACKEND_TYPE (jaeger, tempo, or traceloop) and BACKEND_URL. For Traceloop, add BACKEND_API_KEY.

    BACKEND_TYPE

    BACKEND_TYPE=jaeger

    BACKEND_URL

    BACKEND_URL=http://localhost:16686

    BACKEND_API_KEY

    BACKEND_API_KEY=your_api_key
  7. 07

    Click Add, then enable

    Toggle on Cosmos Agent or CLI.

Local command

Suggested name: opentelemetry

uvx opentelemetry-mcp

Requires Python 3.11+ and uv (or pipx). Supports Jaeger, Grafana Tempo, and Traceloop backends.

Authentication

Backend-specific. Set BACKEND_TYPE and BACKEND_URL. Traceloop requires BACKEND_API_KEY.

VariableExampleRequired
BACKEND_TYPEjaegerYes
BACKEND_URLhttp://localhost:16686Yes
BACKEND_API_KEYyour_api_keyYes
Official documentation →
← All MCPsWorkflows →