Datadog MCP Server

What Datadog MCP Server does

Datadog MCP Server exposes Datadog observability and security data to AI agents through MCP. The available Datadog areas include logs, metrics, APM traces, monitors, dashboards, and security signals. This makes the server relevant for agents that need to investigate telemetry, inspect monitoring configuration, or work with Datadog security data without leaving an MCP-compatible client.

Access follows the permissions of the Datadog user who signs in. An agent therefore works within that user's existing Datadog authorization rather than receiving unrestricted access to the account.

How it works

The service is hosted by Datadog and connects to clients over HTTP. Authentication can use OAuth, allowing the client to sign in as a Datadog user, or credentials consisting of an access token together with API and application keys.

Datadog operates separate endpoints for its different sites. The endpoint shown for the US1 site is only an example of this site-specific arrangement; clients should use the endpoint associated with the Datadog site containing the account and data they need to access.

Setup and configuration

Configure an MCP client to use the hosted Datadog endpoint for the appropriate Datadog site. Select OAuth when the client supports the hosted sign-in flow. The alternative authentication method uses a Datadog access token, API key, and application key.

Before connecting, confirm that the selected Datadog identity has permission to view or work with the resources the agent will use. The server applies that identity's permissions when exposing Datadog information to the client.

Tools and capabilities

Datadog MCP Server gives agents access to these Datadog resource areas:

• Logs for investigating recorded application and infrastructure events
• Metrics for examining measured system and service behavior
• APM traces for tracing application requests and performance
• Monitors for reviewing Datadog monitoring resources
• Dashboards for accessing Datadog dashboard information
• Security signals for working with Datadog security-related events

The server is intended for MCP clients that can make HTTP connections and complete one of its supported authentication flows.

Limitations and notes

Permissions are inherited from the signed-in Datadog user or the credentials used for access. Results and available operations therefore depend on Datadog authorization.

Datadog site selection matters: each site has its own server endpoint. Use the endpoint matching the site that hosts the relevant Datadog account rather than assuming the US1 endpoint applies to every deployment.