Skip to content
Custom Connectors
SolutionsConnectorsPricingResourcesBlog
Build my connector

Connect Datadog to Claude Code

Let Claude manage monitors, mute alerts, and update incidents in Datadog. From the terminal, inside the sessions where you already work.

Build my connectorTalk to us

How do you connect Datadog to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Datadog, you add a Datadog MCP server: a small hosted service that exposes Datadog's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Datadog account. No API keys pasted into config files.

claude mcp add --transport http datadog https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in Datadog once connected?

Full read-write Datadog access lets Claude create and edit monitors, mute or unmute monitors during a deploy, add notes and status updates to an active incident, and adjust dashboards. The triage and on-call follow-up that used to mean tab-switching happen where your telemetry already lives, once you approve.

  • Create or edit a monitor with thresholds and notification targets
  • Mute an alert or downtime window during a planned deploy
  • Post a status update or note to an active incident
  • Mute or unmute a monitor during a maintenance window
  • Add a widget or update a dashboard from a saved query
  • Tag hosts or services to keep monitor scopes accurate

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Datadog access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the Datadog API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Datadog changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Datadog connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same Datadog connector work in claude.ai and Claude Code?
Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Datadog account, so access always matches what that person can already see and do.
Do I need to host or maintain anything myself?
No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Datadog's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.
Is it safe to give a coding agent write access to Datadog?
Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Datadog account it signs in with. Revoking access is one click in Datadog.

More on the Datadog connector

Datadog connector for claude.aiSentry + Claude CodePagerDuty + Claude CodeGitHub + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connectorTalk to us