Happy slice of mcp pizzaMCP.pizza

mcp-server-datadog

MCP.Pizza Chef: winor30

Twenty-one tools reach into a Datadog account: incidents, monitor states, log searches, dashboards, metric history, request traces, host lists and real-user browsing data. Four of them change things rather than just look — muting a host, unmuting it, scheduling quiet time and cancelling it — and none of the four asks you to confirm, so a loosely worded request can silence live alerting. This is a community project, not Datadog's own. It needs two credentials from your account, and the incident filter promised in the readme does not exist in the code.

Coding
Data

Use This MCP server To

Ask which of my monitors are alerting right now Search my logs for errors in the last hour Look up the details of an ongoing incident Check how many machines are currently reporting in Silence alerts on one machine during maintenance Pull a metric's history for a specific time window Find the slowest pages real visitors are hitting

README

Datadog MCP Server

DISCLAIMER: This is a community-maintained project and is not officially affiliated with, endorsed by, or supported by Datadog, Inc. This MCP server utilizes the Datadog API but is developed independently as part of the Model Context Protocol ecosystem.

NPM VersionBuild and Testcodecovsmithery badge

MCP server for the Datadog API, enabling incident management and more.

mcp-server-datadog MCP server

Features

  • Observability Tools: Provides a mechanism to leverage key Datadog monitoring features, such as incidents, monitors, logs, dashboards, and metrics, through the MCP server.
  • Extensible Design: Designed to easily integrate with additional Datadog APIs, allowing for seamless future feature expansion.

Tools

mcp-server-datadog FAQ

Do I need keys?
Yes, two of them: a Datadog key and a Datadog application key, both created in your account settings. Datadog itself is a paid product, so you need a plan there before any of this is useful.
Can it change anything, or only look?
It can change things. Four tools mute a machine, unmute it, schedule quiet time and cancel it. They run the moment they are called, with no confirmation step and no read-only mode to switch on.
Is this Datadog's official tool?
No. The project says so itself: it is built independently by a community developer and is not endorsed or supported by Datadog.
Can I use this to work out why a service went down?
Yes. Ask for the incident, then for the failing monitors, then search the logs and traces around that time window, all in one conversation.
Can I filter incidents by status or priority?
No, despite the readme saying so. The code only accepts a page size and a starting position, so you get incidents in order and have to sift them yourself.
Which apps does it work in?
Claude Desktop is the documented target, with a one-line Smithery installer. Any app that accepts a small tool-server config entry will run it too.
What if my Datadog account is not in the United States?
There is a region setting you can add alongside your keys, so European and other regional accounts are supported.
How hard is the setup?
Moderate. Paste a config block containing the command and your two keys, then restart the app. The fiddly part is generating the right keys in Datadog.
Is it maintained?
Reasonably. The most recent change landed in mid-2026 and there are open issues, so it is alive but not fast-moving.