Skip to main content
Glama
datadog-logs-mcp

datadog-logs-mcp

by bgrgndzz

datadog-logs-mcp

MCP server for querying Datadog logs. Use with Claude Code, Claude Desktop, or any MCP-compatible client.

Setup

{
  "mcpServers": {
    "datadog-logs": {
      "command": "npx",
      "args": ["-y", "datadog-logs-mcp"],
      "env": {
        "DD_API_KEY": "your-api-key",
        "DD_APP_KEY": "your-app-key",
        "DD_SITE": "datadoghq.com"
      }
    }
  }
}

Environment Variables

Variable

Required

Description

DD_API_KEY

Yes

Datadog API key

DD_APP_KEY

Yes

Datadog Application key

DD_SITE

No

Datadog site (default: datadoghq.com). Use datadoghq.eu, us3.datadoghq.com, us5.datadoghq.com, etc.

Related MCP server: Datadog Logs MCP Server

Tools

search_logs

Search logs using Datadog log search syntax with time range, sorting, and pagination.

get_log

Get a specific log entry by ID.

aggregate_logs

Aggregate logs with computations (count, avg, sum, min, max, percentiles) and group-by breakdowns.

list_indexes

List all configured log indexes.

License

MIT

Available Tools

3 tools
aggregate_logsA

Aggregate Datadog logs to compute metrics like count, avg, sum, min, max, percentiles. Supports group-by for breakdowns.

Inputs: query (required), compute (required), to, from, +1 more.

get_logA

Retrieve a specific Datadog log entry by its unique ID. Requires the approximate timestamp of the log to narrow the search.

Inputs: log_id (required), timestamp (required).

search_logsA

Search Datadog logs using the log search syntax. Returns matching log entries with their attributes, timestamps, and metadata.

Inputs: query (required), to, from, sort, +3 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    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.

    Related MCP Connectors

    Related MCP 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
      D
      maintenance
      Enables AI assistants to search logs, query metrics, manage dashboards, analyze APM traces, and control monitors via Datadog APIs.
      30
      MIT