Datadog MCP Server

DISCLAIMER: This is a community-maintained project and is not officially affiliated with, endorsed by, or supported by Datadog, Inc. This MCP server utilizes the Datadog API but is developed independently as part of the Model Context Protocol ecosystem.

MCP server for the Datadog API, enabling incident management and more.

<a href="https://glama.ai/mcp/servers/bu8gtzkwfr"> <img width="380" height="200" src="https://glama.ai/mcp/servers/bu8gtzkwfr/badge" alt="mcp-server-datadog MCP server" /> </a>

Features

• Observability Tools: Provides a mechanism to leverage key Datadog monitoring features, such as incidents, monitors, logs, dashboards, and metrics, through the MCP server.
• Extensible Design: Designed to easily integrate with additional Datadog APIs, allowing for seamless future feature expansion.

Tools

1. list_incidents

   • Retrieve a list of incidents from Datadog.
   • Inputs:
     • filter (optional string): Filter parameters for incidents (e.g., status, priority).
     • pagination (optional object): Pagination details like page size/offset.
   • Returns: Array of Datadog incidents and associated metadata.

2. get_incident

   • Retrieve detailed information about a specific Datadog incident.
   • Inputs:
     • incident_id (string): Incident ID to fetch details for.
   • Returns: Detailed incident information (title, status, timestamps, etc.).

3. get_monitors

   • Fetch the status of Datadog monitors.
   • Inputs:
     • groupStates (optional array): States to filter (e.g., alert, warn, no data, ok).
     • name (optional string): Filter by name.
     • tags (optional array): Filter by tags.
   • Returns: Monitors data and a summary of their statuses.

4. get_logs

   • Search and retrieve logs from Datadog.
   • Inputs:
     • query (string): Datadog logs query string.
     • from (number): Start time in epoch seconds.
     • to (number): End time in epoch seconds.
     • limit (optional number): Maximum number of logs to return (defaults to 100).
   • Returns: Array of matching logs.

5. list_dashboards

   • Get a list of dashboards from Datadog.
   • Inputs:
     • name (optional string): Filter dashboards by name.
     • tags (optional array): Filter dashboards by tags.
   • Returns: Array of dashboards with URL references.

6. get_dashboard

   • Retrieve a specific dashboard from Datadog.
   • Inputs:
     • dashboard_id (string): ID of the dashboard to fetch.
   • Returns: Dashboard details including title, widgets, etc.

7. query_metrics

   • Retrieve metrics data from Datadog.
   • Inputs:
     • query (string): Metrics query string.
     • from (number): Start time in epoch seconds.
     • to (number): End time in epoch seconds.
   • Returns: Metrics data for the queried timeframe.

8. list_traces

   • Retrieve a list of APM traces from Datadog.
   • Inputs:
     • query (string): Datadog APM trace query string.
     • from (number): Start time in epoch seconds.
     • to (number): End time in epoch seconds.
     • limit (optional number): Maximum number of traces to return (defaults to 100).
     • sort (optional string): Sort order for traces (defaults to '-timestamp').
     • service (optional string): Filter by service name.
     • operation (optional string): Filter by operation name.
   • Returns: Array of matching traces from Da