Skip to main content
Glama
rezo8

Datadog Logs MCP Server

by rezo8
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to Datadog Logs MCP Server

No user-submitted related servers found.

    Related Servers

    • Datadog MCP Server

      abhi276k
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables integration with Datadog APIs to monitor and retrieve information about monitors, metrics, dashboards, logs, events, and incidents through the Model Context Protocol.
      2,000 npm
      MIT

    • SQLite MCP Server

      direkt
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables querying log data stored in SQLite databases through the Model Context Protocol, allowing natural language interactions with log analysis.
      -

    • Datadog MCP Server

      tuno-dev
      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
      1,062 npm
      MIT

    • Grafana-Loki MCP Server

      tumf
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables querying and formatting Loki logs from Grafana via the Model Context Protocol. It supports LogQL queries, label retrieval, and provides results in text, JSON, or markdown formats.
      137 PyPI
      29
      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 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose targeting different data sources: Clickhouse database queries, Cloudbeds PMS API for reservations, and Datadog logs search. There is no overlap in functionality or ambiguity about which tool to use for each specific task.

    Naming Consistency5/5

    All three tools follow a consistent verb_noun pattern with 'search_' prefix followed by the target resource (clickhouse, cloudbeds_pms, logs). The naming is perfectly uniform and predictable across the entire tool set.

    Tool Count3/5

    With only 3 tools, the server feels somewhat thin for a 'Datadog Logs MCP Server' that also includes non-Datadog tools. While the tools are well-defined, the scope appears broader than just logs, and the count may be insufficient for comprehensive coverage of the implied domains.

    Completeness2/5

    For a server named 'Datadog Logs', having only one Datadog-specific tool (search_logs) with two unrelated tools creates significant gaps. The Clickhouse tool is unimplemented, and the Cloudbeds tool seems out of scope, leaving the core Datadog functionality incomplete and fragmented.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources