Datadog MCP Server

What it does

This is Datadog's own MCP server, run by Datadog as a remote HTTP service. You point an MCP client at the endpoint for your Datadog site, sign in to your Datadog organization, and the assistant can then work with the observability data that your user account can already see. Nothing is installed locally; the GitHub repository holds only setup notes and two example agents built with the Claude Agent SDK.

Tools are grouped into toolsets that you pick with a toolsets query parameter on the URL. With no parameter you get the core set: searching logs, spans, RUM events, events, hosts, monitors, dashboards, notebooks, incidents and the service catalog, reading metrics and traces, and creating or editing notebooks. Further sets cover alerting, APM, Audit Trail, case management, dashboards, Database Monitoring, DDSQL queries, Error Tracking, feature flags, Kubernetes, profiling, RUM, security signals and findings, Synthetic tests, Watchdog, Workflow Automation and more; toolsets=all turns on the generally available ones, and an omit_tools parameter removes single tools. Datadog's tool reference lists about 360 tools across all sets.

A code-exec toolset lets the assistant send JavaScript that Datadog runs in its own sandbox against your Datadog APIs, to combine several queries in one call. Most tools query Datadog directly, but a few, such as semantic search or building a query from plain language, call AI models hosted by Datadog's providers. Responses are trimmed to fit an assistant's context, and most tools take a max_tokens argument.

What it needs

A Datadog account on a supported site (US1, US3, US5, EU, AP1, AP2 and others; not the US government sites). Your role needs the mcp_read permission, plus mcp_write for tools that change things, along with the normal permission for each product. An organization admin must have MCP Access switched on, and MCP Write Access for write tools. A client that speaks MCP over streamable HTTP.

Limits

Not available on GovCloud (ddog-gov) sites. Fair-use limits of 50 tool calls per 10 seconds and 100,000 tool calls a month, which Datadog says may change. Only the core toolset is on by default; preview toolsets such as apm, governance, investigator and remote-actions need sign-up and are not included in toolsets=all. Datadog says both the server and its tools are under significant development and may change. Each endpoint serves one Datadog site, so EU and other regions use their own hostname.

Who it suits

Teams already on Datadog who want an assistant to look into alerts, logs, traces and incidents without running anything themselves: it is official, hosted, signs in with OAuth and follows each user's existing role permissions. Because it can also create monitors, dashboards, cases and workflows, admins who want read-only use should leave MCP Write Access off. Pick something else if you are on a ddog-gov site, need to work offline, or do not use Datadog. For local code scanning (SAST, SCA, secrets, SBOM), Datadog's docs point to its separate Code Security MCP Server.