- Home
- MCP servers
- Datadog
Datadog
- typescript
65
GitHub Stars
typescript
Language
4 months ago
First Indexed
3 weeks ago
Catalog Refreshed
Documentation & install
Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.
Installation
Add the following to your MCP client configuration file.
Configuration
View docs{
"mcpServers": {
"geli2001-datadog-mcp-server": {
"command": "npx",
"args": [
"datadog-mcp-server",
"--apiKey",
"<YOUR_API_KEY>",
"--appKey",
"<YOUR_APP_KEY>",
"--site",
"<YOUR_DD_SITE>(e.g us5.datadoghq.com)"
],
"env": {
"DD_SITE": "datadoghq.com",
"DD_API_KEY": "<YOUR_API_KEY>",
"DD_APP_KEY": "<YOUR_APP_KEY>",
"DD_LOGS_SITE": "logs.datadoghq.com",
"DD_METRICS_SITE": "metrics.datadoghq.com"
}
}
}
}You can use the Datadog MCP Server to access and interact with Datadog data through a Model Context Protocol interface. It lets you retrieve monitors, dashboards, metrics, events, logs, and incidents, and exposes service-specific endpoints for logs and metrics, all through MCP clients. This guide shows practical steps to install, configure, and run the server so you can query Datadog data from your MCP-based tools.
How to use
Connect with your MCP client by starting the Datadog MCP Server locally or via an automatic tool integration. Use the server to fetch monitors, dashboards, metrics metadata, events, incidents, and logs, and to run log searches and analytics. You can configure separate endpoints for logs and metrics when needed and supply credentials securely. Use your MCP client to call any of the supported tools, such as get-monitors, get-dashboards, get-metrics, get-events, search-logs, and aggregate-logs, and handle results within your application workflows.
How to install
Follow these steps to install and prepare the Datadog MCP Server on your system.
Prerequisites include Node.js version 16 or higher and a Datadog account with API and application keys.
Install the MCP server globally using npm:
npm install -g datadog-mcp-server
If you prefer to install from source, clone the repository, install dependencies, and build the project:
# Clone the repository
git clone https://example.com/geli2001/datadog-mcp-server.git
cd datadog-mcp-server
# Install dependencies
npm install
# Build the project
npm run build
To run the server locally after installation, use the standard CLI invocation and supply your keys and site information as shown in the configuration examples.
Configuration and security
Configure credentials and site endpoints to access Datadog data. You can provide keys via environment variables or command-line arguments.
Environment variable options (example):
DD_API_KEY=your_api_key_here
DD_APP_KEY=your_app_key_here
DD_SITE=datadoghq.com
DD_LOGS_SITE=datadoghq.com
DD_METRICS_SITE=datadoghq.com
Command-line usage examples show how to start the server with required keys and optional regional endpoints. Use these patterns to tailor the server to your Datadog region and data needs.
Examples and usage notes
The server supports a broad set of tools that you can call from your MCP client. Common actions include fetching monitors, dashboards, and metrics, searching or aggregating logs, and retrieving incidents.
Troubleshooting
If you encounter access issues, verify that your API key and application key are correct and that the keys have the necessary permissions for the resources you request. Ensure you are targeting the correct region endpoint and that your MCP client is issuing valid calls to the available tools.
Notes
Region endpoints vary by site. Default is datadoghq.com for US, with EU and other regions available as needed. Separate endpoints for logs and metrics can be configured when required.
Available tools
get-monitors
Fetch monitors with optional filtering to view configurations and states.
get-monitor
Retrieve details for a specific monitor by its ID.
get-dashboards
List all dashboards available in your Datadog organization.
get-dashboard
Get a specific dashboard by its ID.
get-metrics
List available metrics exposed by Datadog.
get-metric-metadata
Retrieve metadata for a specific metric.
get-events
Fetch events from the event stream within a defined time range.
get-incidents
List incidents with optional filtering and pagination.
search-logs
Search logs using complex queries and filters.
aggregate-logs
Perform analytics and aggregations on log data.