datadog.com
datadog.com logo

Datadog

Integrates with Datadog's API to enable incident management, including listing and retrieving incident information for s...

Created byApr 22, 2025

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.

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
  1. get_incident
  1. get_monitors
  1. get_logs
  1. list_dashboards
  1. get_dashboard
  1. query_metrics
  1. list_traces
  1. list_hosts
  1. get_active_hosts_count
  1. mute_host
  1. unmute_host
  1. list_downtimes
  1. schedule_downtime
  1. cancel_downtime
  1. get_rum_applications
  1. get_rum_events
  1. get_rum_grouped_event_count
  1. get_rum_page_performance
  1. get_rum_page_waterfall

Setup

Datadog Credentials

You need valid Datadog API credentials to use this MCP server:
  • DATADOG_API_KEY: Your Datadog API key
  • DATADOG_APP_KEY: Your Datadog Application key
  • DATADOG_SITE (optional): The Datadog site (e.g. datadoghq.eu)
Export them in your environment before running the server:

Installation

Installing via Smithery

To install Datadog MCP Server for Claude Desktop automatically via Smithery:

Manual Installation

Usage with Claude Desktop

To use this with Claude Desktop, add the following to your claude_desktop_config.json:
On MacOS: ~/Library/Application Support/Claude/claude_desktop_config.jsonOn Windows: %APPDATA%/Claude/claude_desktop_config.json
Or specify via npx:

Debugging

Because MCP servers communicate over standard input/output, debugging can sometimes be tricky. We recommend using the MCP Inspector. You can run the inspector with:
The inspector will provide a URL you can open in your browser to see logs and send requests manually.

Contributing

Contributions are welcome! Feel free to open an issue or a pull request if you have any suggestions, bug reports, or improvements to propose.

License

This project is licensed under the Apache License, Version 2.0.

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.

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
  1. get_incident
  1. get_monitors
  1. get_logs
  1. list_dashboards
  1. get_dashboard
  1. query_metrics
  1. list_traces
  1. list_hosts
  1. get_active_hosts_count
  1. mute_host
  1. unmute_host
  1. list_downtimes
  1. schedule_downtime
  1. cancel_downtime
  1. get_rum_applications
  1. get_rum_events
  1. get_rum_grouped_event_count
  1. get_rum_page_performance
  1. get_rum_page_waterfall

Setup

Datadog Credentials

You need valid Datadog API credentials to use this MCP server:
  • DATADOG_API_KEY: Your Datadog API key
  • DATADOG_APP_KEY: Your Datadog Application key
  • DATADOG_SITE (optional): The Datadog site (e.g. datadoghq.eu)
Export them in your environment before running the server:

Installation

Installing via Smithery

To install Datadog MCP Server for Claude Desktop automatically via Smithery:

Manual Installation

Usage with Claude Desktop

To use this with Claude Desktop, add the following to your claude_desktop_config.json:
On MacOS: ~/Library/Application Support/Claude/claude_desktop_config.jsonOn Windows: %APPDATA%/Claude/claude_desktop_config.json
Or specify via npx:

Debugging

Because MCP servers communicate over standard input/output, debugging can sometimes be tricky. We recommend using the MCP Inspector. You can run the inspector with:
The inspector will provide a URL you can open in your browser to see logs and send requests manually.

Contributing

Contributions are welcome! Feel free to open an issue or a pull request if you have any suggestions, bug reports, or improvements to propose.

License

This project is licensed under the Apache License, Version 2.0.