---
title: "Datadog MCP: review, setup & limitations · Undominated.ai"
canonical: https://undominated.ai/mcp-servers/datadog/
description: "Query Datadog telemetry and operate permitted monitoring resources from an authenticated AI client."
---

# Datadog MCP: review, setup & limitations · Undominated.ai

> Query Datadog telemetry and operate permitted monitoring resources from an authenticated AI client.

[← Explore all mcp servers](/mcp-servers/)

OBSERVABILITY / Datadog

# Datadog MCP

Query Datadog telemetry and operate permitted monitoring resources from an authenticated AI client.

 [See setup guidance ↓](#setup)[Original source ↗](https://docs.datadoghq.com/mcp_server/)

SOURCE REVIEW

 Reviewed 2026-10-14
 Evidence 3 linked sources
 Publisher Datadog
 Licence Not established
 [Read what was—and wasn’t—checked ↓](#review)

“The Datadog MCP Server acts as a bridge between your observability data in Datadog and any AI agents”

 [Datadog · upstream description ↗](https://docs.datadoghq.com/mcp_server/) Our analysis follows below.

01 / THE REASONING

## Why this made the selection.

 - Connects logs, traces, metrics, incidents and monitoring context already held in Datadog.
- Existing user permissions and configurable toolsets provide practical boundaries for an agent integration.
- The overview describes a remote MCP server that lets clients such as Cursor, OpenAI Codex, and Claude Code query Datadog products including APM, logs, metrics, monitors, dashboards, and security signals.
- Setup treats OAuth 2.0 as the usual login, separates tools that read data from tools that create or modify resources, and still requires the underlying Datadog resource permission for either.

### A good fit for

 - Correlate application symptoms across Datadog telemetry.
- Investigate or update monitoring resources within an approved role.
- Retrieving Datadog telemetry or managing platform features the signed-in user is already allowed to use, from an MCP client that can complete OAuth against the site-specific endpoint.
- A narrower connection that stays on the default core toolset, or names only selected toolsets, instead of loading every generally available tool.

### Weigh up before choosing

 - MCP read/write permissions are additional to resource permissions; this is not a read-only connector by default.
- The endpoint varies by Datadog site and is not GovCloud compatible.
- The client controls onward sharing with its model provider; Datadog also documents MCP usage logging and some AI-powered tools.
- The overview says the server is not GovCloud compatible, and the pages carry a not-supported alert for site regions gov and gov2.
- Documented fair-use limits are 50 tool calls per 10 seconds and 100,000 monthly tool calls, and the overview says those limits are subject to change.
- The server does not send Datadog data to a third-party AI provider, but the client decides what its model receives. Datadog stores MCP usage context, including user prompts that led to tool use, for 120 days. A small number of tools use AI models hosted by Datadog's providers.
- HIPAA eligibility does not make a connected AI client compliant; the overview says that remains the user's responsibility.
- If toolsets are omitted, only the core toolset is returned. Preview toolsets are not included in the all alias and must be requested by name. The ChatGPT app is in Preview and, during that preview, available for US1 customers only.
- After an OAuth grant is revoked, a client that already holds a valid access token can keep calling until that token expires. Revocation does not affect personal access tokens, service access tokens, or API and application keys.
- Organization-level MCP write can hide write tools for every user, and an IP allowlist can block unapproved origins even when the user has the required permissions. A read-only user's call to a write-enabled tool is rejected.
- The tools page says the tool list is under significant development and subject to change. get_datadog_incident does not include incident timeline data, and the assistant toolset does not create, edit, or delete Datadog resources.
- No licence name appears on these pages. The existing catalogue licence was left unchanged.
- This review did not execute the resource.
- Do not assume support for one Datadog site or the ChatGPT preview proves availability for every region and client.

02 / THE REVIEW RECORD

## What we actually inspected.

Source review has boundaries. A clear record is more useful than a “safe” badge.

### Material inspected

 - Datadog MCP overview, setup instructions, tool reference and corresponding publisher documentation source.
- https://docs.datadoghq.com/mcp_server/
- https://docs.datadoghq.com/mcp_server/setup/
- https://docs.datadoghq.com/mcp_server/tools/
- Round 2 reread of acquired publisher setup and permission evidence; see immutable wave review.

### Our findings

 - The main hosted server is distinct from Datadog’s local Code Security MCP server.
- The setup guide supports toolset selection and omit_tools; these do not replace account-level authorization.
- The overview presents one remote server for most Datadog products and tells readers to use a different, local-only Code Security MCP server for SAST, SCA, IaC, secrets, and SBOM scans.
- That server answers individual tool calls, does not receive the prompt or the model's reasoning, returns results only to the calling client, and makes no outbound calls to external domains. Most listed tools query Datadog backends with no model involved; a few use Datadog-hosted models for semantic search or natural-language queries.
- Permissions are the user's own: reading needs the read MCP permission plus the resource permission, writing needs the write MCP permission plus the resource permission, and the server cannot expose anything that user cannot already see in the Datadog UI. Admins can hide write tools organization-wide and can refuse connections from networks outside an IP allowlist.
- The tools reference groups each tool by toolset and permission and says the set is still changing. It also states things particular tools do not do, including incident timeline data on get_datadog_incident and mutating actions in the assistant toolset.
- Toolsets can be selected with the endpoint query or X-Datadog-MCP-Toolsets header; the ChatGPT app preview has a narrower site availability than generic MCP.

### Not established by this review

 - Server launch, authenticated tool calls, and release-to-source parity were not tested.
- The resource was not executed and its tools were not called.

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

## Connect a server deliberately.

[Upstream setup instructions ↗](https://docs.datadoghq.com/mcp_server/setup/)
 - Open the official setup guide and select your Datadog site to obtain its correct endpoint.
- Follow the client-specific HTTP/OAuth instructions and complete authorization.
- Have an administrator grant the needed MCP and resource permissions, then choose only relevant toolsets.

### Before you start

 - A supported Datadog site and account.
- MCP Read permission and relevant resource permissions; MCP Write plus resource write permission for mutations.

### Compatibility

Claude Code · Codex · Cursor · VS Code

### Transports

Streamable HTTP

### Remote OAuth or scoped access token

 - Reads authorized telemetry and account objects.
- Write-enabled tools can change monitoring resources when both MCP and resource permissions allow it.

### Cost model

Datadog product entitlements and account usage apply; check the current MCP fair-use limits and AI-client terms.

04 / FOLLOW THE EVIDENCE

## The source trail.

Our notes are separate from the original resource. Check upstream before adopting a new version.

 - [Datadog MCP setup and scope ↗](https://docs.datadoghq.com/mcp_server/) Checked 2026-10-14 https://docs.datadoghq.com/mcp_server/ Supports: summary, upstreamDescription, whySelected, bestFor, limitations, install, access, compatibility, transports, review
- [Datadog regional setup, permissions and authentication ↗](https://docs.datadoghq.com/mcp_server/setup/) Checked 2026-10-14 https://docs.datadoghq.com/mcp_server/setup/ Supports: install, access, compatibility, transports, limitations
- [Datadog tool reference ↗](https://docs.datadoghq.com/mcp_server/tools/) Checked 2026-10-14 https://docs.datadoghq.com/mcp_server/tools/ Supports: summary, bestFor, review, access

KEEP COMPARING

## Other approaches to consider.

Related by category or shared topics. These are alternatives to inspect, not a measured quality order.

 [### Axiom MCP ↗ Queries Axiom telemetry and manages observability resources through an account-authorized hosted connection.](/mcp-servers/axiom/)[### Checkly MCP Server ↗ Checkly's hosted MCP server over Streamable HTTP: inspect check status and results, test sessions, RCA and result assets, trigger deployed checks, manage monitors and groups, environment variables and status-page incidents. OAuth is recommended; user and service API keys are the documented alternatives.](/mcp-servers/checkly/)[### Cloud Observability MCP ↗ Thirteen Cloud Logging, Monitoring, Trace, and Error Reporting list or get tools over stdio. No write tool is registered in this package.](/mcp-servers/gcloud-observability/)

 [AI Tools ↗](/tools/)[Skills ↗](/skills/)[Agents ↗](/agents/)[MCP Servers ↗](/mcp-servers/)[Workflows ↗](/workflows/)

## Continue your investigation

 - [Inspect resource evidence](/tools/)
- [Choose a host](/agents/)
- [Inspect reusable workflows](/skills/)
- [Use Undominated data](/api/)
