What can datadog-mcp-server do?

datadog metrics query and retrieval via mcp, datadog logs search and filtering via mcp, datadog events creation and querying via mcp, datadog monitors and alert rules querying via mcp, datadog infrastructure and host information retrieval via mcp, datadog trace and apm data retrieval via mcp, mcp protocol implementation and tool discovery, datadog api authentication and credential management via mcp

datadog-mcp-server

MCP ServerFree

MCP Server for Datadog API

Open Source

/ 100

8 capabilities

Capabilities8 decomposed

datadog metrics query and retrieval via mcp

Medium confidence

Exposes Datadog's metrics API through the Model Context Protocol, allowing LLM agents and tools to query time-series metrics data with configurable time ranges, aggregation functions, and tag filtering. Implements MCP resource handlers that translate natural language metric queries into Datadog API calls, returning structured JSON responses with timestamps and metric values for downstream analysis or visualization.

Solves for

Query historical metrics from Datadog to diagnose performance issues in an LLM-driven incident response workflowRetrieve aggregated metrics (avg, max, min, p95) for a specific service over a time window to feed into anomaly detection logicFilter metrics by tags (environment, region, service) to scope queries to specific infrastructure components

Best for

DevOps teams building LLM-powered incident response agents

SREs integrating observability data into AI-driven dashboards

Platform engineers automating metric collection for cost analysis workflows

Requires

Datadog account with API access enabled

Datadog API key and application key

Node.js 16+ runtime

Limitations

Requires valid Datadog API key and app key; no built-in credential rotation or key management

Query latency depends on Datadog API response time (typically 500ms-2s for large time ranges)

No built-in caching of metric results; repeated queries hit Datadog API directly

What makes it unique

Bridges Datadog's REST API into the MCP protocol, enabling LLM agents to query metrics natively without custom HTTP client code; implements MCP resource handlers that abstract Datadog's query syntax and authentication, allowing agents to reason about observability data as first-class context

vs alternatives

Simpler than building custom Datadog API clients for each agent; more standardized than direct HTTP calls because it uses MCP's protocol for tool discovery and context passing

datadog logs search and filtering via mcp

Medium confidence

Exposes Datadog's logs API through MCP, allowing agents to search and filter logs by query expressions, time ranges, and facets. Translates MCP tool calls into Datadog Logs Query Language (LQL) API requests, returning paginated log entries with metadata (timestamp, service, host, tags) for root cause analysis and debugging workflows.

Solves for

Search logs for error patterns or stack traces to diagnose application failures in an automated incident response flowFilter logs by service, environment, and time range to correlate with metric anomaliesRetrieve log facets (unique values for a field like 'service' or 'status') to understand the scope of an issue

Best for

On-call engineers using LLM agents for log-based troubleshooting

Automated incident response systems that correlate logs with metrics and traces

Teams building AI-powered log analysis and alerting workflows

Requires

Datadog account with logs enabled

Datadog API key and application key with logs read permissions

Node.js 16+ runtime

Limitations

Pagination required for large result sets; no automatic streaming of all matching logs

Datadog LQL syntax complexity may require agents to learn query patterns; no query builder abstraction

Log retention limits apply (depends on Datadog plan); older logs may not be queryable

What makes it unique

Wraps Datadog's Logs API in MCP tool definitions, enabling agents to construct and execute complex log queries without direct API knowledge; handles authentication, pagination, and response parsing transparently

vs alternatives

More accessible than raw Datadog API calls for LLM agents; standardized MCP interface allows agents to discover and use log search without hardcoded API details

datadog events creation and querying via mcp

Medium confidence

Exposes Datadog's events API through MCP, allowing agents to create custom events (e.g., deployments, alerts, incidents) and query historical events by time range and tags. Implements MCP tools that translate event creation requests into Datadog event API calls, storing structured event metadata (title, text, tags, priority) for correlation with metrics and logs.

Solves for

Create deployment events in Datadog when CI/CD pipelines complete, enabling correlation with performance metricsQuery events to understand the timeline of infrastructure changes during an incident investigationTag events with service, environment, and incident metadata to build a searchable audit trail

Best for

DevOps teams automating event tracking for deployments and infrastructure changes

Incident response teams building event timelines for post-mortems

Platform teams integrating CI/CD and observability workflows

Requires

Datadog account with events API enabled

Datadog API key with events write permissions

Node.js 16+ runtime

Limitations

Event creation is asynchronous; no guarantee of immediate visibility in Datadog UI

Event retention depends on Datadog plan; older events may be archived or deleted

No built-in deduplication; duplicate event creation requests will create multiple events

What makes it unique

Provides bidirectional event integration (create and query) through MCP, enabling agents to both emit events (for audit trails) and consume them (for timeline reconstruction); abstracts Datadog's event API authentication and payload formatting

vs alternatives

Simpler than building custom event emission logic; MCP interface allows agents to discover event capabilities without hardcoded API knowledge

datadog monitors and alert rules querying via mcp

Medium confidence

Exposes Datadog's monitors API through MCP, allowing agents to query existing monitors, alert rules, and their current status. Implements MCP resource handlers that fetch monitor definitions (thresholds, conditions, notification rules) and current alert state, enabling agents to understand alerting configuration and correlate alerts with incidents.

Solves for

Retrieve monitor definitions to understand what thresholds triggered an alert during incident investigationQuery alert status across all monitors to get a snapshot of system healthIdentify monitors related to a specific service or metric to scope incident impact

Best for

On-call engineers investigating alerts and understanding monitor configuration

Incident response teams building context about what triggered an alert

Automation teams building alert-aware workflows that adjust based on monitor state

Requires

Datadog account with monitors configured

Datadog API key with monitors read permissions

Node.js 16+ runtime

Limitations

Read-only access to monitors; cannot create or modify monitors via MCP (API limitation)

Monitor state is point-in-time; no historical alert state tracking

Large numbers of monitors may require pagination; no built-in filtering by type or status

What makes it unique

Provides agents with read access to monitor configuration and state through MCP, enabling them to reason about alerting rules and correlate alerts with infrastructure changes; abstracts Datadog's monitor API pagination and filtering

vs alternatives

Enables agents to understand alert context without manual API calls; MCP interface standardizes monitor discovery across different agent frameworks

datadog infrastructure and host information retrieval via mcp

Medium confidence

Exposes Datadog's infrastructure API through MCP, allowing agents to query host information, tags, and metadata. Implements MCP tools that fetch host lists, host details (OS, agent version, IP addresses), and host tags for infrastructure topology understanding and resource allocation analysis.

Solves for

Retrieve host information to understand which servers are affected by a metric anomaly or alertQuery host tags to identify infrastructure topology (environment, region, service) for scoping incident impactCheck agent status and versions to diagnose monitoring gaps or outdated agent deployments

Best for

Infrastructure teams investigating host-level issues and resource allocation

Incident response teams understanding infrastructure topology during incidents

Automation teams building host-aware remediation workflows

Requires

Datadog account with infrastructure monitoring enabled

Datadog API key with infrastructure read permissions

Node.js 16+ runtime

Limitations

Host data is eventually consistent; recently added hosts may not appear immediately

Agent status is based on last heartbeat; offline hosts may show stale status for up to 10 minutes

Large infrastructure (thousands of hosts) requires pagination; no built-in filtering by agent version or status

What makes it unique

Provides agents with infrastructure topology context through MCP, enabling them to correlate metrics and logs with specific hosts; abstracts Datadog's host API pagination and tag filtering

vs alternatives

Simpler than building custom host inventory tools; MCP interface allows agents to discover infrastructure without hardcoded API knowledge

datadog trace and apm data retrieval via mcp

Medium confidence

Exposes Datadog's APM/traces API through MCP, allowing agents to query distributed traces, span data, and service dependencies. Implements MCP tools that fetch traces by service, operation, or error status, returning span hierarchies and latency information for performance analysis and debugging distributed systems.

Solves for

Query traces for a specific service to understand request flow and identify latency bottlenecksRetrieve error traces to diagnose application failures and understand error propagation across servicesAnalyze service dependencies and call graphs to understand system architecture and failure impact

Best for

Backend engineers debugging performance issues in distributed systems

SREs investigating latency spikes and service dependencies

Incident response teams understanding request flow during outages

Requires

Datadog account with APM enabled

Services instrumented with Datadog APM agents

Datadog API key with traces read permissions

Limitations

Trace retention depends on Datadog plan; older traces may not be queryable

Trace sampling may result in incomplete data for high-volume services

Large traces with many spans can be slow to retrieve and parse

What makes it unique

Provides agents with distributed trace context through MCP, enabling them to reason about request flow and service dependencies; abstracts Datadog's trace API complexity and span hierarchy traversal

vs alternatives

Enables agents to understand distributed system behavior without manual trace UI navigation; MCP interface standardizes trace access across different agent frameworks

mcp protocol implementation and tool discovery

Medium confidence

Implements the Model Context Protocol (MCP) server specification, exposing Datadog API capabilities as discoverable MCP tools and resources. Handles MCP initialization, tool schema definition, request routing, and response formatting according to MCP specification, enabling any MCP-compatible client (Claude, custom agents) to discover and invoke Datadog operations.

Solves for

Enable Claude Desktop and other MCP clients to automatically discover available Datadog operations without manual configurationStandardize how LLM agents interact with Datadog across different frameworks and toolsProvide schema-based tool definitions that allow agents to understand parameters, required fields, and return types

Best for

Teams building LLM agents that need standardized Datadog integration

Claude Desktop users wanting native Datadog access without custom plugins

Organizations standardizing on MCP for observability tool integration

Requires

Node.js 16+ runtime

MCP client implementation (Claude Desktop, custom agent framework, etc.)

Network connectivity between MCP client and server

Limitations

Requires MCP-compatible client; not compatible with non-MCP LLM frameworks

MCP server must be running and accessible to the client (local or network)

Tool schema definitions are static; cannot dynamically adapt to Datadog API changes without server restart

What makes it unique

Implements full MCP server specification for Datadog, providing standardized tool discovery and invocation; handles MCP protocol details (initialization, schema validation, response formatting) transparently, allowing clients to treat Datadog as a native MCP resource

vs alternatives

More standardized than custom HTTP client libraries; MCP protocol enables tool discovery and schema validation that custom APIs lack

datadog api authentication and credential management via mcp

Medium confidence

Handles Datadog API authentication (API key and app key) and credential management for MCP tool invocations. Implements secure credential storage (environment variables or config files), request signing, and error handling for authentication failures, ensuring all Datadog API calls are properly authenticated without exposing credentials in logs or responses.

Solves for

Securely authenticate to Datadog API without hardcoding credentials in agent codeHandle authentication errors gracefully and provide meaningful error messages to agentsSupport multiple Datadog organizations or API keys for multi-tenant scenarios

Best for

Teams deploying MCP servers in shared environments where credential security is critical

Organizations with multiple Datadog accounts or organizations

DevOps teams automating Datadog integration with strict security policies

Requires

Datadog API key and application key

Environment variables or config file for credential storage

Node.js 16+ runtime

Limitations

Credentials must be provided via environment variables or config files; no built-in credential rotation

No support for temporary credentials or STS tokens; only static API keys

Credentials are stored in memory during server runtime; no encryption at rest

What makes it unique

Centralizes Datadog API authentication in the MCP server, preventing credential exposure in agent code or logs; implements secure credential handling patterns (environment variables, request signing) that are transparent to MCP clients

vs alternatives

More secure than agents managing credentials directly; centralized authentication enables credential rotation and audit logging at the server level

Capabilities are decomposed by AI analysis. Each maps to specific user intents and improves with match feedback.

Related Artifactssharing capabilities

Artifacts that share capabilities with datadog-mcp-server, ranked by overlap. Discovered automatically through the match graph.

MCP Server31

@winor30/mcp-server-datadog

MCP server for interacting with Datadog API

datadog log search and retrieval via mcpdatadog metric query execution via mcp protocoldatadog dashboard and widget querying via mcpdatadog event creation and annotation via mcp

4 shared capabilities

MCP Server34

@winor30/mcp-server-datadog

MCP server for interacting with Datadog API

datadog metric query execution via mcp protocoldatadog event creation and search via mcp toolsdatadog monitor state retrieval and management via mcpdatadog api error handling and response normalization

4 shared capabilities

MCP Server46

Datadog MCP Server

Query Datadog metrics, logs, and monitors via MCP.

time-series metric querying with datadog query languagelog search and filtering with datadog query syntaxdashboard creation and configuration management

3 shared capabilities

MCP Server34

@dynatrace-oss/dynatrace-mcp-server

Model Context Protocol (MCP) server for Dynatrace

log data retrieval and search with structured filteringevent and alert data retrieval with filtering and correlationdynatrace api resource exposure via mcp protocol

3 shared capabilities

MCP Server36

@dynatrace-oss/dynatrace-mcp-server

Model Context Protocol (MCP) server for Dynatrace

dynatrace api resource exposure via mcp protocoldynatrace metric and log query execution

2 shared capabilities

MCP Server23

mcp.natoma.ai

** – A Hosted MCP Platform to discover, install, manage and deploy MCP servers by **[Natoma Labs](https://www.natoma.ai)**

mcp server monitoring, logging, and observability integration

1 shared capability

Best For

✓DevOps teams building LLM-powered incident response agents
✓SREs integrating observability data into AI-driven dashboards
✓Platform engineers automating metric collection for cost analysis workflows
✓On-call engineers using LLM agents for log-based troubleshooting
✓Automated incident response systems that correlate logs with metrics and traces
✓Teams building AI-powered log analysis and alerting workflows
✓DevOps teams automating event tracking for deployments and infrastructure changes
✓Incident response teams building event timelines for post-mortems

Known Limitations

⚠Requires valid Datadog API key and app key; no built-in credential rotation or key management
⚠Query latency depends on Datadog API response time (typically 500ms-2s for large time ranges)
⚠No built-in caching of metric results; repeated queries hit Datadog API directly
⚠Limited to Datadog's query syntax and aggregation functions; cannot extend with custom metrics logic
⚠Pagination required for large result sets; no automatic streaming of all matching logs
⚠Datadog LQL syntax complexity may require agents to learn query patterns; no query builder abstraction

Requirements

Datadog account with API access enabledDatadog API key and application keyNode.js 16+ runtimeMCP client implementation (Claude Desktop, custom agent framework, etc.)Datadog account with logs enabledDatadog API key and application key with logs read permissionsMCP client with tool-calling supportDatadog account with events API enabled

Input / Output

Accepts: metric query strings (e.g., 'avg:system.cpu{env:prod}' in Datadog query language), time range specifications (ISO 8601 timestamps or relative durations like '1h', '7d'), aggregation parameters (rollup interval, function type), Datadog Logs Query Language (LQL) expressions (e.g., 'service:api status:error'), time range parameters (ISO 8601 or relative), facet field names for aggregation, event title and description text, event tags (key:value pairs for service, environment, etc.), event priority level (low, normal, high), time range for event queries, monitor ID or name for specific lookups, filter criteria (monitor type, status, tags), pagination parameters, host name or ID for specific lookups, filter criteria (tag filters, agent status), service name and operation name for trace filtering, time range for trace queries, filter criteria (error status, latency thresholds), span ID or trace ID for specific lookups, MCP protocol messages (tool calls, resource requests), JSON-formatted tool parameters, API key and app key (via environment or config), Datadog API endpoint URL (with region support)

Produces: JSON-structured metric data with timestamps and values, Aggregated statistics (mean, max, min, percentiles), Tag-filtered result sets, JSON array of log entries with full metadata, Facet aggregations (unique field values and counts), Pagination tokens for result set navigation, confirmation of event creation with event ID, JSON array of historical events with metadata, event aggregations by tag, JSON monitor definitions with thresholds and conditions, current alert state (triggered, resolved, no data), notification rule metadata, JSON host metadata (OS, agent version, IP addresses), host tags and custom metadata, agent status and last heartbeat timestamp, JSON trace data with span hierarchies and timing, service dependency graphs, error information and stack traces from spans, MCP protocol responses with tool results, JSON-structured data from Datadog API, error messages and status codes, authenticated HTTP requests to Datadog API, error messages for authentication failures

UnfragileRank

Adoption15%(30% weight)

Quality17%(25% weight)

Ecosystem45%(25% weight)

Match Graph10%(15% weight)

Freshness75%(5% weight)

UnfragileRank is computed from adoption signals, documentation quality, ecosystem connectivity, match graph feedback, and freshness. No artifact can pay for a higher rank.

Type: MCP Server

8 capabilities

Visit datadog-mcp-server→

Package Details

npm

Registry

1.0.9

Version

Weekly Downloads

About

MCP Server for Datadog API

Alternatives to datadog-mcp-server

IntelliCode50Extension

AI-assisted development

Compare →

GitHub Copilot Chat53Extension

AI chat features powered by Copilot

Compare →

GitHub Copilot52Extension

Your AI pair programmer

Compare →

Claude Code for VS Code52Extension

Claude Code for VS Code: Harness the power of Claude Code without leaving your IDE

Compare →

Are you the builder of datadog-mcp-server?

Claim this artifact to get a verified badge, access match analytics, see which intents users search for, and manage your listing.

Claim this artifact →Verification via email

Get the weekly brief

New tools, rising stars, and what's actually worth your time. No spam.

Data Sources

mcp registry

Looking for something else?

Search →

Capabilities8 decomposed

datadog metrics query and retrieval via mcp

Medium confidence

Solves for

Best for

DevOps teams building LLM-powered incident response agents

SREs integrating observability data into AI-driven dashboards

Platform engineers automating metric collection for cost analysis workflows

Requires

Datadog account with API access enabled

Datadog API key and application key

Node.js 16+ runtime

Limitations

Requires valid Datadog API key and app key; no built-in credential rotation or key management

Query latency depends on Datadog API response time (typically 500ms-2s for large time ranges)

No built-in caching of metric results; repeated queries hit Datadog API directly

What makes it unique

vs alternatives

Simpler than building custom Datadog API clients for each agent; more standardized than direct HTTP calls because it uses MCP's protocol for tool discovery and context passing

datadog logs search and filtering via mcp

Medium confidence

Solves for

Best for

On-call engineers using LLM agents for log-based troubleshooting

Automated incident response systems that correlate logs with metrics and traces

Teams building AI-powered log analysis and alerting workflows

Requires

Datadog account with logs enabled

Datadog API key and application key with logs read permissions

Node.js 16+ runtime

Limitations

Pagination required for large result sets; no automatic streaming of all matching logs

Datadog LQL syntax complexity may require agents to learn query patterns; no query builder abstraction

Log retention limits apply (depends on Datadog plan); older logs may not be queryable

What makes it unique

vs alternatives

More accessible than raw Datadog API calls for LLM agents; standardized MCP interface allows agents to discover and use log search without hardcoded API details

datadog events creation and querying via mcp

Medium confidence

Solves for

Best for

DevOps teams automating event tracking for deployments and infrastructure changes

Incident response teams building event timelines for post-mortems

Platform teams integrating CI/CD and observability workflows

Requires

Datadog account with events API enabled

Datadog API key with events write permissions

Node.js 16+ runtime

Limitations

Event creation is asynchronous; no guarantee of immediate visibility in Datadog UI

Event retention depends on Datadog plan; older events may be archived or deleted

No built-in deduplication; duplicate event creation requests will create multiple events

What makes it unique

vs alternatives

Simpler than building custom event emission logic; MCP interface allows agents to discover event capabilities without hardcoded API knowledge

datadog monitors and alert rules querying via mcp

Medium confidence

Solves for

Best for

On-call engineers investigating alerts and understanding monitor configuration

Incident response teams building context about what triggered an alert

Automation teams building alert-aware workflows that adjust based on monitor state

Requires

Datadog account with monitors configured

Datadog API key with monitors read permissions

Node.js 16+ runtime

Limitations

Read-only access to monitors; cannot create or modify monitors via MCP (API limitation)

Monitor state is point-in-time; no historical alert state tracking

Large numbers of monitors may require pagination; no built-in filtering by type or status

What makes it unique

vs alternatives

Enables agents to understand alert context without manual API calls; MCP interface standardizes monitor discovery across different agent frameworks

datadog infrastructure and host information retrieval via mcp

Medium confidence

Solves for

Best for

Infrastructure teams investigating host-level issues and resource allocation

Incident response teams understanding infrastructure topology during incidents

Automation teams building host-aware remediation workflows

Requires

Datadog account with infrastructure monitoring enabled

Datadog API key with infrastructure read permissions

Node.js 16+ runtime

Limitations

Host data is eventually consistent; recently added hosts may not appear immediately

Agent status is based on last heartbeat; offline hosts may show stale status for up to 10 minutes

Large infrastructure (thousands of hosts) requires pagination; no built-in filtering by agent version or status

What makes it unique

Provides agents with infrastructure topology context through MCP, enabling them to correlate metrics and logs with specific hosts; abstracts Datadog's host API pagination and tag filtering

vs alternatives

Simpler than building custom host inventory tools; MCP interface allows agents to discover infrastructure without hardcoded API knowledge

datadog trace and apm data retrieval via mcp

Medium confidence

Solves for

Best for

Backend engineers debugging performance issues in distributed systems

SREs investigating latency spikes and service dependencies

Incident response teams understanding request flow during outages

Requires

Datadog account with APM enabled

Services instrumented with Datadog APM agents

Datadog API key with traces read permissions

Limitations

Trace retention depends on Datadog plan; older traces may not be queryable

Trace sampling may result in incomplete data for high-volume services

Large traces with many spans can be slow to retrieve and parse

What makes it unique

Provides agents with distributed trace context through MCP, enabling them to reason about request flow and service dependencies; abstracts Datadog's trace API complexity and span hierarchy traversal

vs alternatives

Enables agents to understand distributed system behavior without manual trace UI navigation; MCP interface standardizes trace access across different agent frameworks

mcp protocol implementation and tool discovery

Medium confidence

Solves for

Best for

Teams building LLM agents that need standardized Datadog integration

Claude Desktop users wanting native Datadog access without custom plugins

Organizations standardizing on MCP for observability tool integration

Requires

Node.js 16+ runtime

MCP client implementation (Claude Desktop, custom agent framework, etc.)

Network connectivity between MCP client and server

Limitations

Requires MCP-compatible client; not compatible with non-MCP LLM frameworks

MCP server must be running and accessible to the client (local or network)

Tool schema definitions are static; cannot dynamically adapt to Datadog API changes without server restart

What makes it unique

vs alternatives

More standardized than custom HTTP client libraries; MCP protocol enables tool discovery and schema validation that custom APIs lack

datadog api authentication and credential management via mcp

Medium confidence

Solves for

Best for

Teams deploying MCP servers in shared environments where credential security is critical

Organizations with multiple Datadog accounts or organizations

DevOps teams automating Datadog integration with strict security policies

Requires

Datadog API key and application key

Environment variables or config file for credential storage

Node.js 16+ runtime

Limitations

Credentials must be provided via environment variables or config files; no built-in credential rotation

No support for temporary credentials or STS tokens; only static API keys

Credentials are stored in memory during server runtime; no encryption at rest

What makes it unique

vs alternatives

More secure than agents managing credentials directly; centralized authentication enables credential rotation and audit logging at the server level

Capabilities are decomposed by AI analysis. Each maps to specific user intents and improves with match feedback.

Alternatives to datadog-mcp-server

IntelliCode50Extension

AI-assisted development

Compare →

GitHub Copilot Chat53Extension

AI chat features powered by Copilot

Compare →

GitHub Copilot52Extension

Your AI pair programmer

Compare →

Claude Code for VS Code52Extension

Claude Code for VS Code: Harness the power of Claude Code without leaving your IDE

Compare →

datadog-mcp-server

Capabilities8 decomposed

datadog metrics query and retrieval via mcp

datadog logs search and filtering via mcp

datadog events creation and querying via mcp

datadog monitors and alert rules querying via mcp

datadog infrastructure and host information retrieval via mcp

datadog trace and apm data retrieval via mcp

mcp protocol implementation and tool discovery

datadog api authentication and credential management via mcp

Related Artifactssharing capabilities

@winor30/mcp-server-datadog

@winor30/mcp-server-datadog

Datadog MCP Server

@dynatrace-oss/dynatrace-mcp-server

@dynatrace-oss/dynatrace-mcp-server

mcp.natoma.ai

Best For

Known Limitations

Requirements

Input / Output

UnfragileRank

Package Details

About

Categories

Alternatives to datadog-mcp-server

Are you the builder of datadog-mcp-server?

Get the weekly brief

Data Sources

datadog-mcp-server

Capabilities8 decomposed

datadog metrics query and retrieval via mcp

datadog logs search and filtering via mcp

datadog events creation and querying via mcp

datadog monitors and alert rules querying via mcp

datadog infrastructure and host information retrieval via mcp

datadog trace and apm data retrieval via mcp

mcp protocol implementation and tool discovery

datadog api authentication and credential management via mcp

Related Artifactssharing capabilities

@winor30/mcp-server-datadog

@winor30/mcp-server-datadog

Datadog MCP Server

@dynatrace-oss/dynatrace-mcp-server

@dynatrace-oss/dynatrace-mcp-server

mcp.natoma.ai

Best For

Known Limitations

Requirements

Input / Output

UnfragileRank

Package Details

About

Categories

Alternatives to datadog-mcp-server

Are you the builder of datadog-mcp-server?

Get the weekly brief

Data Sources