Skip to main content
Glama
winor30

mcp-server-datadog

by winor30

Related Servers

Alternatives to mcp-server-datadog

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that provides comprehensive read/write access to Datadog APIs, enabling management of monitors, dashboards, logs, incidents, and more via natural language commands.
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server that provides comprehensive Datadog monitoring capabilities, enabling Claude to manage CI/CD pipelines, analyze logs, query metrics, and handle monitors and SLOs.
      -
    • A
      license
      B
      quality
      D
      maintenance
      Enables interaction with Datadog's monitoring and observability platform through the MCP protocol. Supports incident management, monitor status checks, log searches, metrics queries, APM traces, dashboard access, RUM analytics, host management, and downtime scheduling.
      13
      3 npm
      Apache 2.0
    • A
      license
      C
      quality
      F
      maintenance
      A comprehensive read-only MCP server for Datadog, providing 117 tools to query logs, APM, metrics, monitors, dashboards, SLOs, and more, with zero write capabilities for safe AI integration.
      100
      1,326 npm
      2
      MIT
    • F
      license
      B
      quality
      F
      maintenance
      Enables comprehensive Datadog monitoring capabilities including CI/CD pipeline management, service logs analysis, metrics querying, monitor and SLO management, service definitions retrieval, and team management through Claude and other MCP clients.
      13
      20
      -
    • A
      license
      B
      quality
      C
      maintenance
      Unified MCP server for DevOps engineers that provides real-time read and write access to Kubernetes, ArgoCD, Prometheus, and PagerDuty from any MCP-compatible AI agent.
      21
      43 npm
      4
      MIT

    TDQS

    B3.1/5.0

    Scored across 21 tools

    Disambiguation4/5

    Most tools target a clearly distinct resource+action pair, and the RUM group separates applications, events, grouped counts, performance, and waterfall. Minor overlap exists between get_rum_events and get_rum_grouped_event_count, and get_all_services is a log-derived helper that could be mistaken for a general listing tool.

    Naming Consistency4/5

    Names consistently use snake_case with verb_noun ordering (list_*, get_*, mute_host, schedule_downtime). There are minor deviations where 'get' is used for list-like operations (get_monitors, get_logs, get_rum_applications) instead of 'list', but the pattern remains readable.

    Tool Count4/5

    21 tools cover a broad Datadog surface (incidents, metrics, logs, monitors, dashboards, traces, hosts, downtimes, RUM), so the count is justified by the domain. It sits at the upper end of comfortable scope but each tool maps to a real capability.

    Completeness4/5

    The surface covers the key read/monitoring workflows plus some write actions (host mute/unmute, downtime schedule/cancel). Gaps remain in write coverage for incidents, monitors, and dashboards (no create/update/mute), but core observability workflows are workable.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive