Skip to main content
Glama
Sign In
Adiakys

OtlpDashboard

by Adiakys
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

Related Servers

Alternatives to OtlpDashboard

No user-submitted related servers found.

    Related Servers

    • OpenSearch Logs MCP Server

      luis-dominguez-stori
      F
      license
      A
      quality
      D
      maintenance
      Enables querying OpenTelemetry logs stored in OpenSearch across development and production environments. Provides tools for searching logs by various criteria including free-text Lucene queries, trace IDs, service names, error levels, and specific fields.
      8
      -

    • LGTM MCP Server

      pokgak
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides read-only access to Loki, Prometheus, and Tempo APIs, enabling natural language queries for logs, metrics, and traces. Supports multiple instances and authentication via bearer tokens.
      1
      MIT

    • Tempo MCP Server

      UjjwalSk
      A
      license
      B
      quality
      D
      maintenance
      Enables querying Grafana Tempo traces and spans with flexible filtering, including TraceQL queries, tag-based filters, duration ranges, and aggregated statistics.
      6
      7 npm
      GPL 3.0

    • fanout

      labstack
      A
      license
      Not graded
      quality
      A
      maintenance
      Self-hosted OpenTelemetry backend in one Go binary. Its MCP server exposes tools for service health, latency, topology, trace inspection, log search, read-only SQL over traces, logs and metrics, and dashboards.
      10
      Apache 2.0

    • otel-mcp-server

      shiftyp
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables natural language querying and analysis of OpenTelemetry traces, metrics, and logs stored in Elasticsearch/OpenSearch, allowing AI assistants to investigate performance issues, find root causes, and explore system behavior.
      3 npm
      14
      MIT

    • otel-pocket

      kanchingyg
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables coding agents to query a local OTLP trace collector: list recent traces, inspect span trees and critical paths, flag SQL N+1 loops, surface gen_ai metrics, and diagnose slow traces with a local OpenAI-compatible model.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool has a distinct signal+action scope: listing services per telemetry type, querying records/points per signal, and fetching a single trace by id. The only potential overlap between list_metrics and query_metric_points is clearly resolved by the descriptions: one discovers instruments, the other reads points for a specific series.

    Naming Consistency5/5

    All names use a consistent snake_case verb_noun pattern (get_trace, list_*_services, query_logs, query_traces, query_metric_points). The get/list/query verbs are used coherently for detail, discovery, and time-window retrieval.

    Tool Count5/5

    Eight tools is well-scoped for a read-only OTLP observability dashboard covering logs, metrics, and traces. Each tool maps to a clear part of the discovery/query workflow without obvious filler.

    Completeness4/5

    The surface covers service discovery and querying for all three telemetry signals, plus trace detail retrieval. A notable minor gap is that query_logs and query_traces appear to support only time-window queries, with no service filter despite dedicated service-listing tools, so agents may need to scan and filter client-side.

    Maintenance

    ActivityMaintained
    ResponsivenessWithin a week

    Resources