Skip to main content
Glama

otel-mcp

Ein MCP-Server, der OpenTelemetry-Traces, -Metriken und -Logs gleichzeitig an einen oder mehrere OTLP-Endpunkte sendet, und zwar in einem der drei OTLP-Wire-Formate:

  • grpc — OTLP/gRPC (Protobuf über HTTP/2)

  • http/protobuf — OTLP/HTTP binäres Protobuf

  • http/json — OTLP/HTTP proto3-JSON (spezifikationskonform)

Er enthält außerdem Profile zur Werkzeug-Nachahmung, die realistische Signalbündel erzeugen, die wie bekannte Tools geformt sind (Nginx, Postgres, Redis, Kafka, AWS-Lambda, Kubernetes-Pod, generischer gRPC-Dienst), sodass Sie einen Collector oder ein Backend mit Datenverkehr füllen können, der wie eine echte Umgebung aussieht.

Installation

uv venv
uv pip install -e .

Related MCP server: Mock MCP Server

Ausführung

otel-mcp           # stdio transport — wire into any MCP client

Oder über eine MCP-Client-Konfiguration (z. B. Claude Desktop, Claude Code):

{
  "mcpServers": {
    "otel": {
      "command": "otel-mcp"
    }
  }
}

Env-Bootstrap

Wenn OTEL_EXPORTER_OTLP_ENDPOINT beim Start gesetzt ist, wird ein Endpunkt namens default unter Verwendung der Standard-OTEL-Umgebungsvariablen registriert:

  • OTEL_EXPORTER_OTLP_ENDPOINT

  • OTEL_EXPORTER_OTLP_PROTOCOL (grpc | http/protobuf | http/json)

  • OTEL_EXPORTER_OTLP_HEADERS (durch Kommas getrennte k=v-Paare)

  • OTEL_EXPORTER_OTLP_INSECURE (gRPC TLS-Umschalter)

Tools

Endpunkt-Verwaltung

Tool

Zweck

add_endpoint

Registriert ein benanntes OTLP-Ziel (URL, Protokoll, Signale, Header, …).

remove_endpoint

Entfernt einen Endpunkt anhand des Namens.

clear_endpoints

Entfernt alle Endpunkte.

list_endpoints

Listet die aktuellen Endpunkte auf.

status

Endpunkte + verfügbare Nachahmungsprofile.

Endpunkte werden pro Aufruf ausgewählt: Jedes signalgebende Tool akzeptiert ein endpoints: [names]-Argument. Wenn Sie es weglassen, wird das Signal an alle Endpunkte gesendet, die diesen Signaltyp akzeptieren.

Rohsignal-Emission

Tool

Form der Eingabe

send_trace

{service_name, spans[]} — jeder Span hat name, kind, attributes, duration_ms, status, events[], optional parent_name für Verschachtelung.

send_metric

{service_name, metrics[]} — jede Metrik hat name, kind (counter/up_down_counter/gauge/histogram), unit, description, points[]. Histogramme akzeptieren eine Liste von Stichproben pro Punkt.

send_log

{service_name, records[]} — jeder Datensatz hat body, severity, severity_text, attributes, timestamp_ns.

Nachahmung (Mimicry)

Tool

Zweck

list_mimic_profiles

Zeigt jedes Profil mit seinen Parametern an.

mimic_tool

Führt ein Profil aus und sendet dessen Bündel einmalig.

generate_load

Führt ein Profil in einer Schleife aus, um anhaltenden Datenverkehr zu simulieren.

Integrierte Profile:

Profil

Wie es aussieht

nginx / http-server

Server-Spans mit HTTP-Semconv, Zugriffslogs, Anforderungszählern & Latenz-Histogrammen.

postgres

DB-Client-Spans mit db.system=postgresql + Verbindungspool-Metriken.

redis

DB-Client-Spans mit db.system=redis.

kafka

Producer/Consumer-Spans mit Messaging-Semconv.

aws-lambda

Server-Spans mit faas.* + cloud.* Ressourcen-Attributen, Lambda-Zugriffslogs, Aufruf-Metriken.

k8s-pod

Ressource = vollständige k8s.*-Attribute, Container-CPU/Speicher/Netzwerk-Metriken, Started-Ereignis-Log.

grpc

Server-Spans mit rpc.system=grpc.

Beispiel-Sitzung

> add_endpoint name="otel-collector" url="http://localhost:4318" protocol="http/protobuf"
> add_endpoint name="jaeger-json"    url="http://localhost:4318" protocol="http/json" signals=["traces"]
> mimic_tool profile="nginx" options={"count": 50, "error_rate": 0.1}
> mimic_tool profile="postgres"
> generate_load profile="kafka" iterations=10 interval_seconds=2
> send_trace service_name="checkout" spans=[
    {"name": "POST /checkout", "kind": "server", "duration_ms": 42, "attributes": {"http.response.status_code": 200}},
    {"name": "charge_card",    "kind": "client", "parent_name": "POST /checkout", "duration_ms": 18,
     "attributes": {"peer.service": "stripe"}}
  ]

Hinzufügen eines neuen Nachahmungsprofils

  1. Schreiben Sie eine Funktion, die ein MimicBundle in src/otel_mcp/mimics.py zurückgibt.

  2. Registrieren Sie sie im PROFILES-Dictionary am Ende dieser Datei.

  3. Rufen Sie list_mimic_profiles auf, um zu bestätigen, dass die Parameter übernommen wurden.

Profile bleiben deklarativ: Jedes gibt Span-/Metrik-/Log-Spezifikationen zurück, die durch dieselbe Generator-Pipeline fließen, sodass sie automatisch die korrekte Ressourcen-Zusammenführung, Wire-Format-Unterstützung und Fan-Out erben.

Available Tools

11 tools
add_endpointA

Register an OTLP destination.

Args: name: Unique identifier used by other tools to target this endpoint. url: Collector URL. gRPC: host:port or http://host:port. HTTP: base URL (/v1/traces etc. is appended automatically). protocol: One of grpc, http/protobuf, http/json. signals: Subset of traces, metrics, logs. Defaults to all. headers: Headers added to every request (auth tokens, tenant ids, ...). insecure: gRPC only — disable TLS. timeout_seconds: Per-request timeout. overwrite: If an endpoint with this name already exists, replace it.

Inputs: name (required), url (required), protocol, signals, +4 more. Returns: object

clear_endpointsB

Remove all endpoints.

Inputs: no named parameters. Returns: object

generate_loadA

Repeatedly run a mimic profile to simulate sustained traffic.

Blocks for roughly iterations * interval_seconds seconds. For true background loops use an external scheduler — this tool is synchronous by design so the caller sees per-iteration results.

Inputs: profile (required), iterations, interval_seconds, endpoints, +1 more. Returns: object

list_endpointsB

List registered endpoints.

Inputs: no named parameters. Returns: object

list_mimic_profilesB

List available tool-mimicry profiles.

Inputs: no named parameters. Returns: object

mimic_toolB

Emit a realistic bundle of signals mimicking a known tool.

Args: profile: One of nginx, postgres, redis, kafka, aws-lambda, k8s-pod, grpc. Call list_mimic_profiles for profile-specific parameters. endpoints: Fan-out target endpoints. Defaults to all registered. options: Keyword args passed to the profile (e.g. {"count": 50}).

Inputs: profile (required), endpoints, options. Returns: object

remove_endpointC

Remove an endpoint by name.

Inputs: name (required). Returns: object

send_logB

Send one or more log records.

Each record dict accepts: body, severity (trace/debug/info/warn/ error/fatal), severity_text, attributes, timestamp_ns.

Inputs: service_name (required), records (required), resource_attributes, endpoints. Returns: object

send_metricB

Send one or more metric instruments.

Each metric dict accepts: name, kind (counter/up_down_counter/gauge/ histogram), unit, description, points (list of {value, attributes}). For histograms, value may be a list of samples.

Inputs: service_name (required), metrics (required), resource_attributes, endpoints. Returns: object

send_traceA

Send one or more spans to the targeted endpoints.

Each span dict accepts: name, kind (internal/server/client/producer/ consumer), attributes, duration_ms, status (ok/error/unset), status_message, events (list of {name, attributes}), parent_name (to nest spans within the same batch).

If endpoints is omitted, fans out to every endpoint that accepts traces.

Inputs: service_name (required), spans (required), resource_attributes, endpoints. Returns: object

statusA

Report configured endpoints and available profiles.

Inputs: no named parameters. Returns: object

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.7/5.0

    Scored across 11 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose with no ambiguity. Tools like add_endpoint, remove_endpoint, and clear_endpoints handle endpoint management, while send_log, send_metric, and send_trace target specific telemetry signals. Mimic_tool and generate_load are for simulation, and list_endpoints/list_mimic_profiles/status are for querying, all with non-overlapping functions.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern using snake_case, such as add_endpoint, list_endpoints, send_log, and mimic_tool. This uniformity makes the set predictable and easy to understand, with no deviations in naming conventions.

    Tool Count5/5

    With 11 tools, this server is well-scoped for OpenTelemetry management and simulation. It covers endpoint configuration, telemetry emission, mimicry, and status reporting without being overly sparse or bloated, with each tool serving a clear and necessary role.

    Completeness5/5

    The tool set provides complete coverage for the OpenTelemetry domain, including CRUD operations for endpoints (add, remove, clear, list), sending all signal types (logs, metrics, traces), simulation capabilities (mimic, generate_load), and querying (status, list profiles). There are no obvious gaps that would hinder agent workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server implementation that enables dynamic configuration of OpenTelemetry Collectors, allowing users to add, remove, and configure receivers, processors, and exporters through MCP tools.
      52
      GPL 3.0
    • A
      license
      B
      quality
      D
      maintenance
      A mock MCP server for testing MCP client implementations and development workflows. Supports tools, prompts, and resources across multiple transport protocols (stdio, HTTP, SSE).
      1
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      MCP server for analyzing OpenTelemetry traces with performance and error diagnosis, supporting loading from files, AWS X-Ray, and CloudWatch.
      8
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      MCP server that gives AI agents access to your application's OpenTelemetry traces for querying, analysis, and debugging.
      5
      11 npm
      2
      MIT