Can AI agents automate Datadog?

Datadog observability is automatable today through a public HTTP REST API and a first-party remote MCP Server. The API uses resource-oriented URLs, JSON, and standard HTTP status codes. Write calls need an API key in DD-API-KEY; read calls also need an Application key in DD-APPLICATION-KEY. Official clients exist for Java, Python, Ruby, Go, TypeScript, and Rust. Site hosts include US1, EU, and other regional endpoints. The remote MCP Server at https://mcp.datadoghq.com/v1/mcp (US1) bridges APM, logs, metrics, monitors, dashboards, security signals, and related products into MCP clients with user-based OAuth that inherits existing RBAC. Toolsets can be limited with a query parameter or X-Datadog-MCP-Toolsets header. Fair-use limits are 50 requests per 10 seconds and 50,000 monthly tool calls, adjustable through Datadog support. MCP is HIPAA-eligible and not GovCloud compatible. Several toolsets, including APM, are Preview. Audit Trail records every MCP tool call. This record excludes the separate local Code Security MCP Server. Pup CLI is Datadog's official terminal and high-scale agent interface to the same platform. Computer-use viability is unassessed. API and MCP both score 8; API is the best path because it does not carry the MCP monthly tool-call cap or GovCloud exclusion.

Best path today: api · Overall automatability: 8/10