Skip to content

Datadog

Updated View as Markdown

Inspect monitor health and dashboard identities. Prepare an operational brief from the monitoring evidence.

Example workflows

Copy a prompt into your connected AI client after connecting this integration. Choose resources you can access and review the supported command before running it.

List monitor health summaries

Help me with this task in Datadog: List monitor health summaries. Ask me for any required inputs and confirm the resources and scope before calling the command. Read one response page. Turn the returned data into a concise working summary with original IDs, dates and source links when available. Separate missing information from confirmed results and tell me whether more pages remain. Do not invent fields or change data.

Explore this command: datadog.monitors.list

Read monitor health summary

Help me with this task in Datadog: Read monitor health summary. Ask me for any required inputs and confirm the resources and scope before calling the command. Read one response page. Turn the returned data into a concise working summary with original IDs, dates and source links when available. Separate missing information from confirmed results and tell me whether more pages remain. Do not invent fields or change data.

Explore this command: datadog.monitors.get

What you can do (3)

What you can do

Available commands: 3 (3 read, 0 write). Enable only the commands your application needs.

Command Effect
List monitor health summaries — datadog.monitors.list Read
Read monitor health summary — datadog.monitors.get Read
List dashboard identities — datadog.dashboards.list Read

Connect and use

Connect and use

This connection uses your provider account.

Connect this integration, enter your provider credentials, choose commands and save. Complete provider authorization if prompted.

Get your provider credentials

Follow these steps for Datadog, then enter the issued values in the connection form below.

  1. In your selected Datadog US1 or EU1 organization, open Organization Settings, create or reuse an API key and an application key with read access to the monitors and dashboards you need. Choose us1 or eu1 here, then save the two keys in Datadog API key and Datadog application key. EU1 uses app.datadoghq.eu; US1 uses app.datadoghq.com. Do not enter a password or OAuth token. This subset returns health/identity summaries only and does not modify monitors or dashboards.

Official credential setup

Where to enter credentials

In the integration page, sign in, choose your workspace and open Connect. If a Credentials choice is shown, select Use my credentials. Fill the following connection fields and save. Provider credentials belong in this form, never in an MCP configuration or tool input.

Connection field Requirement
Datadog site Required
Datadog API key Required
Datadog application key Required

Open API keys and create a Tooluse.net key for the enabled commands.

Set TOOLUSE_API_KEY in your client and use the shared MCP configuration.

Configure Claude Code, Codex or Cursor once

Permissions and results

If you have more than one workspace, check the selected workspace in the connection or API-key dialog before saving. Roles, enabled commands, expiry and revocation use Tooluse.net's existing permissions. Disabling a connection or revoking a key immediately prevents new calls.

Send one Claude tool_use block per request. Keep the same Idempotency-Key when retrying the same request; use a new key for a new call. The response includes the shared Tooluse.net receipt and Claude tool_result. Check both HTTP status and the returned tool result before treating a call as successful.

Your connection's daily allowance and key permissions also apply. Adding a connection does not make a provider request.

Calls return the shared execution receipt and a Claude tool_result. Provider output varies by operation; consult the provider documentation for its response fields. Unconfirmed calls should be checked before retrying.

Call from your client

Use the shared MCP configuration. Refresh your client's tool list after saving the connection or changing key permissions, then call the returned tool name with the example input below.

Configure Claude Code, Codex or Cursor once

Discover your enabled tools

List permitted tools in Claude format. Read every page using page and size (maximum 100) until all results have been received. Use the returned name, not a catalog capability identifier, in the tool_use block.

curl 'https://api.tooluse.net/v1/tools' \
  -H "Authorization: Bearer $TOOLUSE_API_KEY"

Find this command in the tool list permitted by your key. Replace svc_FROM_YOUR_TOOL_LIST with its returned name. Use a new Idempotency-Key for each new call and retain it when retrying that same call.

HTTP call

curl 'https://api.tooluse.net/v1/tool-calls' \
  -H "Authorization: Bearer $TOOLUSE_API_KEY" \
  -H 'Content-Type: application/json' \
  -H 'Idempotency-Key: replace-with-a-new-call-id' \
  --data '{
  "type": "tool_use",
  "id": "toolu_example",
  "name": "svc_FROM_YOUR_TOOL_LIST",
  "input": {
    "query": {
      "page": 0,
      "page_size": 20
    }
  }
}'

Send one Claude tool_use block per request. Keep the same Idempotency-Key when retrying the same request; use a new key for a new call. The response includes the shared Tooluse.net receipt and Claude tool_result. Check both HTTP status and the returned tool result before treating a call as successful.

Commands

List monitor health summaries — datadog.monitors.list

Read one explicit monitor page containing identity and overall health, without monitor query/message content or notification secrets.

This is a read operation. Provider rate limits and data access rules still apply.

Connect and use

Parameters

Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.

Parameter Type Required in parent Description Constraints
query object Required additionalProperties: false
query.page integer Required Zero-based page number minimum: 0; maximum: 9007199254740991
query.page_size integer Required Results on this page minimum: 1; maximum: 100

Full JSON Schema

Full JSON Schema

Example input

{
  "query": {
    "page": 0,
    "page_size": 20
  }
}

At most 1 provider requests per invocation; timeout: 30 seconds.

Read monitor health summary — datadog.monitors.get

Read one authorized monitor identity and overall state by ID, excluding its query, message and notification configuration.

This is a read operation. Provider rate limits and data access rules still apply.

Connect and use

Parameters

Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.

Parameter Type Required in parent Description Constraints
path object Required additionalProperties: false
path.monitorId integer Required Monitor ID minimum: 1; maximum: 9007199254740991

Full JSON Schema

Full JSON Schema

Example input

{
  "path": {
    "monitorId": 12345
  }
}

At most 1 provider requests per invocation; timeout: 30 seconds.

List dashboard identities — datadog.dashboards.list

Read one dashboard-summary page using explicit count and start offset. Dashboard widgets, queries, share tokens and author details are excluded.

This is a read operation. Provider rate limits and data access rules still apply.

Connect and use

Parameters

Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.

Parameter Type Required in parent Description Constraints
query object Required additionalProperties: false
query.count integer Required Results on this page minimum: 1; maximum: 100
query.start integer Required Zero-based result offset minimum: 0; maximum: 9007199254740991

Full JSON Schema

Full JSON Schema

Example input

{
  "query": {
    "count": 20,
    "start": 0
  }
}

At most 1 provider requests per invocation; timeout: 30 seconds.

Errors

Check the key's expiry, revocation, workspace and allowed operations.

Reuse the same idempotency key only for the same request.

The connection or provider limit has been reached. Check the receipt before retrying.

Test the connection

Open the integration's commands below to inspect parameters and examples. Start with a read command for an account or resource you can access. Refresh your client's tool list, use the returned tool name, and check the execution result and usage. Provider charges and permissions still apply. Never test a write against production data without reviewing it.

Official provider documentation

Type to search…

↑↓ navigate↵ selectEsc close