Skip to main content
Glama
jsamuel1

otel-analyzer-mcp

by jsamuel1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to otel-analyzer-mcp

No user-submitted related servers found.

    Related Servers

    • otel-mcp

      moondef
      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
      16 npm
      2
      MIT

    • Uptrace MCP Server

      dimonb
      F
      license
      A
      quality
      D
      maintenance
      An MCP server for the Uptrace observability platform that enables querying traces, spans, logs, and metrics through natural language. It provides tools for error analysis, service discovery, and trace visualization within MCP-compatible clients.
      11
      2
      -

    • otel-mcp

      michigan-public-tech-org
      A
      license
      A
      quality
      D
      maintenance
      An MCP server that emits OpenTelemetry traces, metrics, and logs to OTLP endpoints in various formats. It includes tool-mimicry profiles to generate realistic traffic resembling common tools like nginx, postgres, and AWS Lambda for testing and demonstration purposes.
      11
      MIT

    • poly-observability-mcp

      hyperpolymath
      A
      license
      Not graded
      quality
      D
      maintenance
      Unified MCP server for observability and monitoring, providing tools to query metrics, logs, and traces through Prometheus, Grafana, Loki, and Jaeger.
      2
      Mozilla Public 2.0

    • observability-mcp

      blue-sky-exist
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for querying observability data from Elasticsearch, SkyWalking, and Prometheus/VictoriaMetrics, enabling AI models to search logs, traces, and metrics across environments.
      9
      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

    B3/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool targets a distinct aspect of trace management and analysis. No two tools have overlapping purposes; descriptions clearly differentiate ingestion, listing, summarizing, error analysis, performance analysis, LLM-assisted analysis, and searching by source.

    Naming Consistency4/5

    Tool names follow a consistent verb_noun snake_case pattern (e.g., load_trace, list_traces, summarize_trace). Minor deviations: analyze_errs and analyze_perf use abbreviations (errs, perf) and deep_analyze uses an adjective prefix, but these are still readable and fit the general pattern.

    Tool Count5/5

    With 8 tools, the server provides a comprehensive but focused set of operations for trace analysis: ingestion, listing, summarization, error analysis, performance analysis, LLM-assisted analysis, and source-specific searches. Each tool earns its place without redundancy.

    Completeness4/5

    The tool set covers the main lifecycle of trace analysis: loading, listing, summarizing, error and performance analysis, and advanced LLM analysis. It also includes source-specific search. A minor gap is the lack of a query/filter capability on loaded traces beyond the static listing, but overall the surface is well-rounded for typical observability tasks.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources