Skip to main content
Glama
datadog-logs-mcp

datadog-logs-mcp

by bgrgndzz

Related Servers

Alternatives to datadog-logs-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      C
      quality
      D
      maintenance
      Enables interaction with Datadog's monitoring platform to search logs, search trace spans, and perform trace span aggregation for analysis.
      3
      MIT
    • 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
      -
    • A
      license
      A
      quality
      C
      maintenance
      Enables read-only querying of Grafana Loki logs through tools like label discovery, LogQL queries, and recent log retrieval, without requiring knowledge of the Loki API.
      4
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables read-only querying and exploration of Grafana Loki logs and LogQL metrics, including labels, fields, volume, stats, patterns, rules, and contextual log retrieval, with responses shaped for context windows.
      14
      95 npm
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to search logs, query metrics, manage dashboards, analyze APM traces, and control monitors via Datadog APIs.
      30
      MIT

    TDQS

    A4.1/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool targets a distinct operation: search_logs filters and returns multiple entries, get_log fetches a single entry by ID, and aggregate_logs computes metrics. There is no meaningful overlap, making tool selection unambiguous.

    Naming Consistency5/5

    All tool names follow the same verb_noun snake_case pattern (search_logs, get_log, aggregate_logs), which is predictable and consistent across the set.

    Tool Count5/5

    Three tools is a well-scoped count for a log-focused server. It covers the core operations (search, retrieve, aggregate) without unnecessary bloat or thinness.

    Completeness4/5

    The set covers the primary log reading and analysis workflow: searching, fetching by ID, and aggregating metrics. Minor gaps like log index listing or log ingestion are absent but not essential for the apparent purpose.