Skip to content
Agentmart
Submit a tool

Datadog MCP

Full Datadog API access: monitors, logs, metrics, traces, dashboards, and observability tools

Connector by TANTIOPE · GitHub account verified by the MCP Registry

IndexedApache-2.0Local (stdio)★ 6
Write a review

Install

Works with Claude Code, Codex, VS Code, Cursor, Windsurf, Claude Desktop. Read the repository before you give any tool access to your data.

npx agentmarket install connector/tantiope-datadog-mcp

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Full Datadog API access: monitors, logs, metrics, traces, dashboards, and observability tools

Reviews

Write a review

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this server can do and what it asks for, from its tool list and install config. Checked Oct 25, 2026.

Tools
8 read · 12 write · 0 delete · 3 not yet classified
Secrets
2 (API keys, tokens or passwords)
Install scripts
Not scanned yet
Runs as
Node.js package

Tools by what they do 23

Read from the source code; the running server may list different tools.

Read 8 · Look things up without changing anything.

  • auth
  • logs
  • metrics
  • rum
  • schema
  • security
  • traces
  • usage

Write 12 · Create, change, send or run things.

  • downtimes
  • hosts
  • incidents
  • logs_archives
  • logs_indexes
  • logs_pipelines
  • notebooks
  • slos
  • synthetics
  • tags
  • teams
  • users

Not yet classified 3 · We could not tell from the name and description.

  • dashboards
  • events
  • monitors

Secrets and settings it asks for

Secrets: values you paste in that let it act as you.

  • DD_API_KEY
  • DD_APP_KEY

Other settings (environment variables or headers).

  • DD_SITE

Tools (23)

Read from the source code; the running server may differ. Descriptions are the server’s own words; hidden characters are shown as [U+…].

  • auth

    Validate Datadog API credentials. Use this to verify that the API key and App key are correctly configured before performing other operations.

  • dashboards

    Access Datadog dashboards and visualizations. Actions: - list: Filter dashboards by name/tags - get: Retrieve full dashboard config including widgets (useful for learning patterns) - create: Create new dashboard - update: Modify existing dashboard - delete: Remove dashboard - validate: Test dashboard config without creating (helps debug widget definitions) Widget formats supported: - Simple: { "type": "timeseries", "requests": [{ "q": "avg:metric{*}" }] } - Advanced: { "type": "timeseries", "requests": [{ "queries": [...], "formulas": [...] }] } Tags must use key:value format (e.g., ["team:…

  • downtimes

    Manage Datadog scheduled downtimes for maintenance windows. Actions: list, get, create, update, cancel, listByMonitor. Use for: scheduling maintenance, preventing false alerts during deployments, managing recurring maintenance windows.

  • events

    Track Datadog events. Actions: list, get, create, search, aggregate, top, timeseries, incidents, discover, histogram. For monitor alerts, use tags: ["source:alert"]. IMPORTANT — re-evaluation vs transition: - source:alert events INCLUDE renotifies and re-evaluations (every Datadog re-evaluation of an alerting monitor emits an event). A "how many times did monitor X fire" question answered with source:alert alone over-counts. - To restrict to real state transitions, pass transitionType (e.g. ["alert","alert recovery"]). This appends @monitor.transition.transition_type:(...) to the query an…

  • hosts

    Manage Datadog infrastructure hosts. Actions: list (with filters), totals (counts), mute (silence alerts), unmute. Use for: infrastructure inventory, host health, silencing noisy hosts during maintenance.

  • incidents

    Manage Datadog incidents for incident response. Actions: list, get, search, create, update, delete. Use for: incident management, on-call response, postmortems, tracking MTTR/MTTD.

  • logs

    Search Datadog logs with grep-like text filtering. Actions: search (find logs), aggregate (count/group). Key filters: keyword (text grep), pattern (regex), service, host, status (error/warn/info). Time ranges: "1h", "3d@11:45:23". CORRELATION: Logs contain dd.trace_id in attributes for linking to traces and APM metrics. SAMPLING: Use sample:"diverse" for error investigation (dedupes by message pattern), sample:"spread" for time distribution. TOKEN TIP: Use compact:true to reduce payload size (strips heavy fields) when querying large volumes.

  • logs_archives

    Manage Datadog Logs archives (long-term log retention to S3 / GCS / Azure Blob). Actions: list, get, create, update, delete, reorder, get_order. Archives accept destinations of type 's3', 'gcs', or 'azure_storage'; per-provider credential and integration fields (S3 IAM role ARN, GCS service account, Azure tenant/secret) are forwarded unchanged. Mutations (create, update, delete, reorder) are blocked when the server is in read-only mode.

  • logs_indexes

    Manage Datadog Logs indexes (filters, retention, exclusion filters, daily limits). Actions: list, get, update, reorder, get_order. Datadog identifies indexes by 'name', not 'id'. Note: create/delete are UI-only per Datadog and not supported through the API. Mutations (update, reorder) are blocked when the server is in read-only mode.

  • logs_pipelines

    Manage Datadog Logs pipelines (parsing & processor chains). Actions: list, get, create, update, delete, reorder, get_order. Pipelines run sequentially on incoming logs; reorder changes the structure of downstream data. Mutations are blocked when the server is in read-only mode. Unknown processor types in 'config.processors' are forwarded to Datadog unchanged.

  • metrics

    Query Datadog metrics. Actions: - query: Get timeseries data (requires from/to time range, PromQL query) - search: Find metrics by name (grep-like, NO time param needed) - list: Get recently active metrics (last 24h, optionally filter by tag) - metadata: Get metric details (unit, type, description) APM METRICS (auto-generated from traces): Keyed by OPERATION name (e.g. express.request, pg.query), NOT service name. Filter by service using tags: {service:my-service} PERCENTILES (p50/p75/p90/p95/p99) — use the ROOT metric (distribution type): p95:trace.express.request{service:my-service} AVG…

  • monitors

    Manage Datadog monitors. Actions: list, get, search, create, update, delete, mute, unmute, top, history, preview, test_notification. Filters: name, tags, groupStates (alert/warn/ok/no data). get/create/update return the full options object so callers can safely read-then-patch. create/update accept a config object validated against a typed schema covering the documented Datadog Monitor fields: - Top-level: name, type, query, message, tags, priority (1-5, nullable), restrictedRoles, multi, options. - options.* validated keys grouped by category: - notification: notifyNoData, noDataT…

  • notebooks

    Manage Datadog Notebooks. Actions: list (search notebooks), get (by ID with cells), create (new notebook), update (modify notebook), delete (remove notebook). Use for: runbooks, incident documentation, investigation notes, dashboards as code.

  • rum

    Query Datadog Real User Monitoring (RUM) data. Actions: applications (list RUM apps), events (search RUM events), aggregate (group and count events), performance (Core Web Vitals: LCP, FCP, CLS, FID, INP), waterfall (session timeline with resources/actions/errors). Use for: frontend performance, user sessions, page views, errors, resource loading.

  • schema

    Get valid enum values for Datadog API fields. Returns palettes, widget types, aggregators, comparators, time spans, and other valid values for constructing dashboards, monitors, metrics queries, and SLOs. Use this to discover valid options before creating or updating Datadog resources.

Show 8 more tools
  • security

    Query Datadog Security Monitoring. Actions: rules (list detection rules), signals (search security signals), findings (list security findings). Use for: threat detection, compliance, security posture, incident investigation.

  • slos

    Manage Datadog Service Level Objectives. Actions: list (with SLI status & error budget), get, create, update, delete, history. SLO types: metric-based, monitor-based. Each list/get/create/update response includes a `url` field deep-linking to the Datadog UI. Use for: reliability tracking, error budgets, SLA compliance, performance targets.

  • synthetics

    Manage Datadog Synthetic tests (API and Browser). Actions: list, get, create, update, delete, trigger, results. Use for: uptime monitoring, API testing, user journey testing, performance testing, canary deployments.

  • tags

    Manage Datadog host tags. Actions: list (all host tags), get (tags for specific host), add (create tags), update (replace tags), delete (remove all tags). Use for: infrastructure organization, filtering, grouping.

  • teams

    Manage Datadog teams. Actions: list (with filters), get (by ID), members (list team members). Use for: team organization, access management, collaboration.

  • traces

    Analyze APM traces for request flow and latency debugging. Actions: search (find spans), aggregate (group stats), services (list APM services). Key filters: minDuration/maxDuration ("500ms", "2s"), httpStatus ("5xx", ">=400"), status (ok/error), errorMessage (grep). APM METRICS: Traces auto-generate metrics in trace.<operation>.* namespace (e.g. trace.express.request). Use metrics tool to query: avg:trace.express.request.duration{service:my-service}. For percentiles (p95), use the root metric WITHOUT .duration suffix: p95:trace.express.request{service:my-service}

  • usage

    Query Datadog usage metering data. Actions: summary (overall usage), hosts (infrastructure), logs, custom_metrics, indexed_spans, ingested_spans. Use for: cost management, capacity planning, usage tracking, billing analysis.

  • users

    Manage Datadog users. Actions: list (with filters), get (by ID). Use for: access management, user auditing, team organization.

Signals

Stars
6
Forks
4
Open issues
6
Last commit
Jun 29, 2026 (4 months ago)
Last release
Jun 29, 2026 (4 months ago)

From GitHub (fetched Oct 24, 2026).

Details

Registry name
io.github.TANTIOPE/datadog-mcp
Version
1.0.9
Auth
API key
Packages
npm datadog-mcp
License
Apache-2.0
Repository
github.com/tantiope/datadog-mcp-server
First seen
Oct 24, 2026
Last checked
Oct 24, 2026
Source
Official MCP Registrygithub-graphql
Cite this page

Datadog MCP. Agent Mart. https://agentmart.dev/connectors/tantiope-datadog-mcp (last updated 2026-10-24)