PlugWiki
Datadog MCP Server logo

Datadog MCP Server: Connect Datadog to Claude, Cursor and VS Code

OfficialRemote

Datadog's own server that lets your AI assistant search logs, metrics, traces and monitors in your Datadog account.

This is Datadog's own server, and once you sign in with your Datadog account your AI assistant can read your logs, metrics, traces, monitors, incidents, dashboards and notebooks. It runs on Datadog's servers, so there is nothing to install. Each Datadog site has its own address, and using the wrong one is the most common reason sign-in fails. An admin must also turn on MCP Access for your organization before anyone can connect.

Good for

  • On-call engineers who want Claude or Cursor to dig through logs and traces during an incident
  • Developers who debug production issues from inside their editor
  • Platform and SRE teams who tune monitors, dashboards and alert thresholds
  • Security teams who review detection signals and findings

Works in

5 supported · 5 with issues · 3 should work

Tap an app to see how to set it up and any known problems.

Install Datadog MCP

Claude Code

  1. 1

    Copy this prompt.

    Add the Datadog MCP server to Claude Code. Run this command:
    
    /plugin install datadog@claude-plugins-official
    
    Then check that it loaded and tell me if I need to sign in or restart.
  2. 2

    Paste it into Claude Code. It shows the change and asks before running it.

Requires Datadog account with MCP Access turned on, Sign-in with your Datadog account (OAuth).

Read-only mode: Choose read-only access when you sign in with OAuth, or ask an admin to give you only the mcp_read permission. You can also add `?omit_tools=` to the address to drop single tools.

An org admin must turn on MCP Access under Organization Settings, then MCP, before anyone can connect. The plugin is Datadog's recommended route. Run /ddsetup afterwards, pick your Datadog site and sign in, then /ddtoolsets to choose toolsets. If you add the server by hand, remove the plugin first to avoid a clash, and swap in your site's address from the pattern below. Your site decides the address: put mcp. in front of your Datadog site and end with /v1/mcp. Sites are US1 (mcp.datadoghq.com), US3 (mcp.us3.datadoghq.com), US5 (mcp.us5.datadoghq.com), EU1 (mcp.datadoghq.eu), AP1 (mcp.ap1.datadoghq.com), AP2 (mcp.ap2.datadoghq.com) and UK1 (mcp.uk1.datadoghq.com). The wrong site is the most common reason sign-in fails. Government sites are not supported. Only the core tools load by default. Add ?toolsets=apm,llmobs (or ?toolsets=all) to the address to load more.

From the vendor's docs. Source.

Tools

  • Finds log lines that match your filters

    Core toolset. Searches your logs by time, query, service, host and storage tier, and returns the matching log entries.

    Try: “Show me error logs from the nginx service in the last hour.”

    Read · search_datadog_logs

  • Counts and totals logs with SQL

    Core toolset. Runs SQL over your logs to count, group and total them, which suits statistics more than reading single lines.

    Try: “Count error logs by service in the last hour.”

    Read · analyze_datadog_logs

  • Charts metric values over time

    Core toolset. Queries current or past metric data with custom queries and aggregations, so you can see how a number moved over a period.

    Try: “Show me CPU utilization metrics for all hosts in the last 4 hours.”

    Read · get_datadog_metric

  • Shows a metric's tags and details

    Core toolset. Returns a metric's metadata, its available tags and the values of those tags, so you know what you can filter or group by.

    Try: “What tags are available for the system.cpu.user metric?”

    Read · get_datadog_metric_context

  • Lists the metrics you have

    Core toolset. Lists the metrics in your account, with options to filter by name or tag and to include metadata.

    Try: “Show me all available Redis metrics.”

    Read · search_datadog_metrics

  • Lists monitors and their status

    Core toolset. Retrieves monitors with their current status, thresholds and alert conditions, so you can see what is firing.

    Try: “List all monitors that are currently alerting.”

    Read · search_datadog_monitors

  • Lists incidents by state and severity

    Core toolset. Retrieves a list of incidents with their state, severity and other details.

    Try: “Show me all active incidents by severity.”

    Read · search_datadog_incidents

  • Shows the details of one incident

    Core toolset. Retrieves detailed information about a single incident. It does not include the incident timeline.

    Try: “What's the status of incident ABC123?”

    Read · get_datadog_incident

  • Finds events like deploys and alerts

    Core toolset. Searches events such as monitor alerts, deployments, infrastructure changes, security findings and service status changes.

    Try: “Show me all deployment events from the last 24 hours.”

    Read · search_datadog_events

  • Lists your monitored hosts

    Core toolset. Lists and filters the hosts Datadog monitors, for example by tag or by whether they have stopped reporting.

    Try: “List unhealthy hosts that haven't reported in the last hour.”

    Read · search_datadog_hosts

  • Finds services, owners and dependencies

    Core toolset. Searches the Datadog Catalog for who owns a service and what sits upstream and downstream of it.

    Try: “What downstream services does the payment API depend on?”

    Read · search_datadog_entities

  • Finds traced requests that match filters

    Core toolset. Retrieves spans from APM traces filtered by service, time, resource and similar fields.

    Try: “Show me spans with errors from the checkout service.”

    Read · search_datadog_spans

From the official docs

Pros and cons

Good

  • It is Datadog's own server, generally available since March 2026.
  • Nothing to install: it is hosted, and you sign in with your Datadog account.
  • Covers logs, metrics, traces, monitors, incidents, dashboards, notebooks and more.
  • Respects your existing roles, Data Access Control and log restriction queries.
  • Every tool call shows up in Audit Trail.
  • An admin can switch off all write tools for the whole organization.

Watch out

  • Each Datadog site has its own address, and the wrong one breaks sign-in.
  • Only the core tools load by default, so you must name other toolsets yourself.
  • Loading every toolset fills the model's context before work starts.
  • Write access can delete dashboards, pipelines and rules.
  • Datadog GovCloud sites are not supported.
  • Sign-in expires after about an hour in some clients, so you sign in again often.
  • Fair-use limits apply, and Datadog says tools change often.

Permissions

high risk · 5 things to watch

High risk

With write access, the assistant can delete dashboards, log pipelines and other Datadog resources. Connect with read-only OAuth access, or give people only the mcp_read permission.

What it can do

Watch out for

  • Write tools can delete and reconfigure resources

    With the mcp_write permission, the assistant can delete dashboards for good, remove log indexes, pipelines and archives, and change security rules. Give people mcp_read only, or connect with read-only OAuth access. docs.datadoghq.com

  • The default tools can change notebooks and dashboards

    Even without extra toolsets, the core set can create, edit and delete notebooks, and create or overwrite dashboards. Deleted notebooks can be recovered for 30 days; drop the write tools with omit_tools if you want reads only. docs.datadoghq.com

  • Logs and traces may contain secrets or personal data

    Whatever a tool returns goes to your AI provider under your agreement with them. Limit what people can see with roles, Data Access Control and log restriction queries. docs.datadoghq.com

  • Every call is recorded in Audit Trail

    Admins can see the tool name, arguments, user and client for each call, so they can review what an agent did. docs.datadoghq.com

  • API keys work as a broad fallback

    API and application keys act with the key owner's permissions. Datadog recommends scoped keys from a service account, and a revoked sign-in keeps working until its token expires. docs.datadoghq.com

Security advisories

No published security advisories as of Nov 1, 2026.

Technical details
Turning on read-onlyAn org admin turns off MCP Write Access to hide write tools for everyone; or give users only mcp_read; or connect with read-only OAuth access. Per connection you can also drop tools with ?omit_tools=. Without ?toolsets only core loads (mostly read, plus notebook edits and dashboard create or update).
Talks tomcp.<your-datadog-site>/v1/mcp
Scopes
  • mcp_read

  • mcp_write

Alternatives

Use Datadog's own server unless you need to run something locally with API keys. The two community servers are alternatives for that case.

ServerOfficialRunsSign-inCan change thingsToolsPopularity
Datadog MCP ServerThis pageOfficialHostedAccountYes––
datadog-mcp-server (geli2001)CommunityLocalAPI key––70
datadog-mcp-server (tantiope)CommunityLocal–––6

What people say

People like how fast it makes production debugging and dislike the sign-in problems and the context cost of loading every toolset.

What people like

  • Engineers report fast production debugging when an agent has the Datadog MCP plus code access.
  • Agents pull the raw data they need without overloading their context.
  • Claude Code plugin setup is a single install command plus an interactive /ddsetup, no JSON editing.

Common complaints

  • With every toolset on, tool definitions fill the model's context before work starts, so you have to pick toolsets.
  • Sign-in breaks often across clients, mostly when the URL does not match your Datadog site or tokens expire after an hour.
  • Agents can still reach wrong conclusions from Datadog data without checking sources, so incident fixes need a human.

In their words

1 more quote

Questions

What is the Datadog MCP server URL for my region?

Put mcp. in front of your Datadog site and add /v1/mcp. US1 is https://mcp.datadoghq.com/v1/mcp and EU1 is https://mcp.datadoghq.eu/v1/mcp. US3, US5, AP1, AP2 and UK1 follow the same pattern, such as mcp.us3.datadoghq.com.

Why does Datadog sign-in fail or say 'Invalid client_id'?

Most often the URL is for the wrong Datadog site, for example the US1 address with an EU account. Switch to your own site's address, clear the client's saved sign-in for the server, and sign in again.

Why do I only see a few tools?

Only the core set loads by default. Add ?toolsets=alerting,dashboards to the URL, or ?toolsets=all for every generally available set. Preview sets such as apm must be named explicitly.

Can the AI change or delete things in my Datadog account?

Yes, if you have the mcp_write permission and permission for the resource. It can create monitors and edit or delete dashboards, notebooks, log pipelines, security rules and workflows. An admin can turn off MCP Write Access to hide all write tools.

How do I make it read-only?

Ask an admin to turn off MCP Write Access, give people only the mcp_read permission, or connect with read-only OAuth access. You can also remove single tools with ?omit_tools=.

Does it cost extra?

Datadog publishes no separate price for the MCP server. You need a Datadog account with MCP access enabled. Fair-use limits apply: 50 tool calls per 10 seconds and 100,000 per month per organization.

Does it work on Datadog for Government?

No. The US1-FED and US2-FED sites are not supported.

Does Datadog send my data to an AI provider?

The server does not. Your AI client sends tool results to its own model. A few tools, such as natural-language query building, use Datadog-hosted AI models, and support can turn that off for your organization.

Can I use API keys instead of OAuth?

Yes. Send your API key and application key as headers, or a personal or service access token as a Bearer token. Datadog recommends scoped keys from a service account.

Why does it say MCP access is disabled?

An organization admin has to turn on MCP Access in Organization Settings under MCP. When it is off, nobody in the organization can connect.

Examples

  • Check for errors from one dependency across services

    Check if there are any Redis errors in our environment.

    Source
  • List monitors grouped by their current status

    List my monitors and their statuses.

    Source
  • Find ongoing incidents linked to a latency problem

    Are there any ongoing incidents related to Redis latency?

  • Find a latency metric, graph it and tune the alert threshold

    Find the Redis latency metric, show it over the last day, and suggest a better alert threshold for its monitor.

  • Check which monitors are firing right now

    Use search_datadog_monitors to list monitors with status:alert.

    Source

Information

updated Nov 1, 2026

Publisher
Official
Transport
Streamable HTTP
Auth
OAuth

DocsClaude connectors directoryInstall guideChangelog

Other Datadog MCP servers

Sources

Docs, issue trackers and discussions this page is built from. Issues, quotes and findings above link to their own source.

Show all 14
  1. Set up the Datadog MCP Server · docs.datadoghq.com
  2. Datadog MCP Server tools · docs.datadoghq.com
  3. Datadog MCP Server changelog · github.com
  4. Datadog MCP Server overview · docs.datadoghq.com
  5. Invalid client_id · github.com
  6. news.ycombinator.com · news.ycombinator.com
  7. news.ycombinator.com · news.ycombinator.com
  8. Datadog Claude Code plugin · dev.classmethod.jp
  9. MCP tool filtering for Datadog · speakeasy.com
  10. Sign-in lasts about an hour · github.com
  11. news.ycombinator.com · news.ycombinator.com
  12. Datadog remote MCP server · datadoghq.com
  13. geli2001/datadog-mcp-server · github.com
  14. tantiope/datadog-mcp-server · github.com

Facts from the official MCP registry, GitHub, npm, PyPI and the Docker catalog. Updated Nov 1, 2026.