Available

Datadog MCP server

Datadog unifies metrics, logs, and traces for cloud applications, helping engineering teams monitor systems and get alerted before small issues become outages. Connect through Arc0 to use the actions your identity is allowed to call.

DevOps and monitoringAPI key and application keyMCP + RESTdatadoghq.com
AUDIT LOG · DATADOGPOLICY: acme-support
09:41:07 · claude · u_8f2read
datadog.list_monitors
List monitors✓ allowed · 212ms
09:41:08 · claude · u_8f2read
datadog.get_monitor
Get monitor✓ allowed · 164ms
09:41:09 · claude · u_8f2write
datadog.post_event
Post event✓ approved · approved by user
ILLUSTRATIVE POLICY TRACE · NOT A LIVE RECEIPT
01 · USE CASES

Agent workflows for Datadog.

01

List active monitor downtimes

Use when checking current mute state before changing alerting or reconciling a mute/unmute. Returns active v2 downtime matches, scopes and expiry. Inspect every page; empty data alone does not prove unmuted if more matches exist. Requires monitors_downtime.

02

List monitors

Use when discovering monitor IDs in an organization. Returns one bounded page; filter by monitor tags to limit the scope.

03

Search monitors

Use when finding monitors by status, tags or text before inspecting or changing alerting. Total count describes all matches, not the current page.

02 · ACTIONS

11 Datadog actions, graded by risk.

These actions come from the Arc0 registry. Your identity, provider permissions and Arc0 policies determine which actions can run.

read

8

Look things up, subject to your permissions.

  • datadog.list_monitor_downtimes
    List active monitor downtimes

    Use when checking current mute state before changing alerting or reconciling a mute/unmute. Returns active v2 downtime matches, scopes and expiry. Inspect every page; empty data alone does not prove unmuted if more matches exist. Requires monitors_downtime.

  • datadog.list_monitors
    List monitors

    Use when discovering monitor IDs in an organization. Returns one bounded page; filter by monitor tags to limit the scope.

  • datadog.search_monitors
    Search monitors

    Use when finding monitors by status, tags or text before inspecting or changing alerting. Total count describes all matches, not the current page.

  • datadog.get_monitor
    Get monitor

    Use when inspecting a known monitor, its query and alert state. Use list_monitor_downtimes for current mute state and to reconcile uncertain alerting changes.

  • datadog.search_events
    Search events

    Use when investigating events within an explicit window of at most 24 hours. Returns at most 100 entries and a cursor. Content may be sensitive; inspect meta status and warnings for partial results.

  • datadog.search_logs
    Search logs

    Use when investigating logs within an explicit window of at most 24 hours. Returns at most 100 entries and a cursor. Content may be sensitive; inspect meta status and warnings for partial results.

  • datadog.query_metrics
    Query metric timeseries

    Use when comparing metric values during an incident within an explicit window of at most 24 hours. Scope the query to relevant series; missing samples may be null.

  • datadog.list_incidents
    List incidents

    Use when discovering incidents for triage. Returns one bounded page of incident status and titles without responders or notification handles. Requires Incident Management access.

write

3

Create and change things. Allow, or ask the user first.

  • datadog.mute_monitor
    Mute monitor

    Use when suppressing alerts during approved maintenance. First read list_monitor_downtimes; do not change an existing mute: a new end can shorten someone else’s longer or indefinite mute. Recipients stop receiving alerts. Read downtimes before retrying an uncertain result.

  • datadog.unmute_monitor
    Unmute monitor

    Use when restoring notifications for a monitor after approved maintenance. Configured alert recipients may receive alerts again. Do not use on a mute owned by someone else; read list_monitor_downtimes before retrying.

  • datadog.post_event
    Post event

    Use when posting an approved operational event. Monitors and @mentions may notify configured recipients; avoid private notes. May incur event usage charges even on timeout. Aggregation is not deduplication; search before retrying an uncertain post.

destructive

0

Delete, cancel or archive. Ask first, or deny outright.

  • No destructive actions.
03 · POLICIES AND AUDIT

Control access to Datadog.

Connect the intended Datadog account, authorize your AI client and set policies for its tools.

Provider permissions and Arc0 policy both apply. Allow reads, require approval for selected writes, or deny destructive actions. The audit log records execution decisions.

Configure policies and approvals

Example policy choices

  • Read actions: allow where authorized
  • datadog.post_event: require approval

Arc0 MCP endpoint: https://api.arc0.ai/mcp

04 · AUTH AND DATA

How Datadog connects.

Connect Datadog using API key and application key. OAuth grants the provider scopes shown during consent; API keys and other credentials retain the permissions configured at the provider. Arc0 stores credentials in its encrypted vault and does not pass them to the model. Disconnect to remove access through Arc0; revoke a key at the provider to invalidate it there. Token refresh and provider-side revocation depend on the authentication lane and provider.

The connection serves authorized calls through Arc0 MCP and REST. How Arc0 handles credentials →

AUTH
API key and application key
CREDENTIALS
Per-tenant encrypted vault
MODEL SEES
Results only, never credentials
AUDIT LOG
Every call, on every plan
05 · AI CLIENTS

Use Datadog with your AI client.

Sign in to Arc0 and connect Datadog in My apps. Then authorize your AI client separately. It only receives tools and accounts allowed for that identity.

Datadog with Claude

Claude Desktop + Claude Code

  1. In Claude Desktop, add Arc0 through the remote MCP settings and use OAuth. Follow the generic remote-client steps if your account’s interface differs.
  2. For Claude Code, run the command below. Open /mcp, select Arc0, and authenticate in your browser. Select your workspace and review access.
  3. Check the connection with claude mcp get arc0.
claude mcp add --transport http --scope user arc0 https://api.arc0.ai/mcp
Full MCP setup and troubleshooting
All apps for Claude
Datadog with ChatGPT

ChatGPT on the web

  1. Open Plugins in ChatGPT, select the plus button, then Add custom MCP server.
  2. Name it Arc0, enter the server URL below, and choose OAuth. Use dynamic client registration if asked; no Arc0 API key is needed.
  3. Review the notice and select Create as a plugin. Complete Arc0 sign-in, workspace selection and consent, then install and select the plugin in your conversation. Labels and access vary by account; managed workspaces may require administrator approval.
https://api.arc0.ai/mcp
Full MCP setup and troubleshooting
All apps for ChatGPT
Datadog with OpenAI Codex

Codex app + CLI

  1. Run the registration command below. The app and CLI share ~/.codex/config.toml.
  2. Complete browser OAuth, choose your Arc0 workspace, and review access. If authentication does not start, run codex mcp login arc0.
  3. Check codex mcp list, then open a new Codex chat. Inspect an existing arc0 entry before changing it.
codex mcp add arc0 --url https://api.arc0.ai/mcp
Full MCP setup and troubleshooting
All apps for OpenAI Codex
Datadog with Cursor

Remote MCP setup

  1. Add Arc0 in your client’s remote MCP settings using the server URL below.
  2. Choose OAuth, sign in to Arc0, select the intended workspace and review access.
  3. Confirm the server is connected and start with an allowed read. These are generic remote-MCP steps; consult your client’s settings for its current interface.
https://api.arc0.ai/mcp
Full MCP setup and troubleshooting
All apps for Cursor
Datadog with VS Code

Remote MCP setup

  1. Add a remote HTTP MCP server named Arc0 using the URL below.
  2. Use OAuth and finish Arc0 sign-in, workspace selection and consent.
  3. Confirm discovery succeeds before requesting a read. These are generic remote-MCP steps; client UI and availability may differ.
https://api.arc0.ai/mcp
Full MCP setup and troubleshooting
Datadog with Any MCP client

Streamable HTTP

  1. Use a client that supports remote MCP over Streamable HTTP. Add the server URL below and choose OAuth.
  2. For a client without OAuth, use a self-bound API key with execute permission in the X-API-Key header. Store it in secret storage or an environment variable, outside source control. Never send both an API key and an OAuth bearer token.
  3. Use the MCP clients guide for the SDK transport example and Embedded identity for business-managed end users.
https://api.arc0.ai/mcp
Full MCP setup and troubleshooting

After setup, ask your agent to find an allowed read action, load its schema, and execute it on the intended account. Check Activity for the receipt. A connected MCP client alone does not confirm a successful provider call.

07 · FAQ

Datadog and Arc0, answered.

Q01

Does Datadog work with Claude Desktop and Claude Code?

Yes, after connecting the account and authorizing the client. Use Arc0’s remote MCP endpoint with OAuth. Claude Code has a documented registration command; Desktop uses the generic remote-client setup.

Q02

Can I use Datadog with OpenAI Codex, ChatGPT and Cursor?

Yes, after connecting the account and authorizing the client. Codex and ChatGPT have setup instructions in Arc0’s MCP clients guide. Cursor uses the generic remote-MCP steps. Tool access remains scoped to the authorized identity.

Q03

Is this the official Datadog MCP server?

This is Arc0’s integration page, not a claim of an official Datadog server. Arc0 adds a shared connection, policy and audit experience across apps. Consult Datadog for its own current MCP offerings.

Q04

Which Datadog actions are supported?

11 registry-defined actions: 8 read, 3 write and 0 destructive. Provider permissions, access enablement and Arc0 policy determine what can execute.

Q05

Which permissions does Datadog need?

Connect Datadog using API key and application key. OAuth grants the provider scopes shown during consent; API keys and other credentials retain the permissions configured at the provider. Arc0 stores credentials in its encrypted vault and does not pass them to the model. Disconnect to remove access through Arc0; revoke a key at the provider to invalidate it there. Token refresh and provider-side revocation depend on the authentication lane and provider.

Q06

Can I restrict writes in Datadog?

You can deny write and destructive actions or require approval. Provider scopes and Arc0 action policies are separate controls; a policy does not grant additional provider permissions.

Q07

What does Datadog through Arc0 cost?

See Arc0 pricing for current connectivity plans. The provider may require its own subscription or charge per request. Arc0 plan allowances do not make third-party data or paid actions free.

Get started

Plug Datadog into your agent.

Datadog MCP server: 11 actions including list active monitor downtimes, list monitors, search monitors. Connect through Arc0.

Free to build · MCP + REST · Audit log on every plan

Datadog and its logo are trademarks of their respective owners. Arc0 is not affiliated with or endorsed by Datadog.