Skip to main content
Glama
Sign In
otel-instrumentation-mcp

otel-instrumentation-mcp

by liatrio-labs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to otel-instrumentation-mcp

No user-submitted related servers found.

    Related Servers

    • tracehub-mcp

      mcpsmiths
      A
      license
      A
      quality
      A
      maintenance
      Connects AI assistants to OpenTelemetry trace backends (Jaeger, Grafana Tempo, Traceloop, Datadog, Sentry, AWS X-Ray, New Relic and Honeycomb) for natural-language trace and span search, error triage, cross-backend correlation, and LLM analytics such as token usage, model performance and the most expensive or slowest traces.
      19
      162 PyPI
      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.
      16 npm
      14
      MIT

    • Production Monitoring MCP

      kowshik3383
      A
      license
      A
      quality
      B
      maintenance
      Connects AI agents to live observability stacks including Sentry, GitHub, Vercel, Better Stack, and Cloudflare, enabling end-to-end incident investigation, deployment correlation, root cause analysis, and regression triage.
      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

    • DevContext

      sid-stack001
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables coding agents to access live runtime observability data such as logs, deploys, and health metrics for evidence-based incident triage.
      1
      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

    A3.7/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool targets a distinct purpose: rules, spec, docs, examples, semantic conventions, repos, issues, and search. There's no overlap; even the two 'by language' tools differentiate between documentation and examples.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with snake_case, using clear prefixes like get_, list_, search_. Suffixes like _by_language are applied uniformly, making the naming predictable and easy to navigate.

    Tool Count5/5

    With 9 tools, the server is well-scoped for its purpose as a reference and documentation resource for OpenTelemetry instrumentation. Each tool serves a clear role without being excessive or insufficient.

    Completeness4/5

    The tool set covers essential aspects: rules, spec, docs, examples, conventions, and repository interaction. A minor gap is the lack of a direct tool to compute or evaluate an instrumentation score, but the provided tools offer foundational information for that purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources