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