Datadog
Query Datadog observability data and manage platform features with Datadog's official MCP server
Monitoring & ObservabilitySaaS & API Integrations
About
Investigate logs, metrics, traces, monitors, dashboards, incidents, hosts, RUM, and more through Datadog’s vendor-hosted MCP server.
See Datadog’s official MCP server documentation for setup instructions, authentication options, permissions, and current capabilities.
Features
- Core observability: Search logs, metrics, traces, monitors, dashboards, incidents, hosts, services, events, notebooks, and RUM data.
- Product toolsets: Enable additional Datadog product-specific toolsets when needed, such as alerting, dashboards, security, synthetics, workflows, and Database Monitoring.
- Datadog authorization: OAuth authenticates as the Datadog user and respects their Datadog roles and resource permissions.
What you’ll need to connect
- Datadog account: The MCP server is available on supported commercial Datadog sites. It is not supported for Datadog GovCloud.
- OAuth access: Complete the Datadog OAuth flow when prompted. Your role requires
mcp_readfor read tools,mcp_writefor write tools, and the underlying Datadog resource permissions. For non-interactive connections, optionally provide a Datadog Personal Access Token (PAT) or Service Access Token (SAT). - Regional endpoint: This entry uses Datadog’s US1 endpoint. For another Datadog site, follow the official setup guide to use that site’s endpoint.
Important considerations
- The default core toolset includes read tools and notebook create/edit tools. Enable additional toolsets only when needed to conserve context and limit the available actions.
- Datadog documents fair-use limits of 50 tool calls per 10 seconds and 50,000 monthly tool calls, subject to change.
- Datadog retains remote-MCP usage, error, identity, and relevant prompt-context data for 120 days. Review the official service documentation before connecting sensitive workloads.
⚠️ Upgrade notice
If you’re upgrading this server, note that this replaces the Obot-hosted Datadog server with Datadog’s official hosted MCP server.
- Reconnect required: Connect with Datadog OAuth or a Personal or Service Access Token. The previous API key, application key, and site settings are no longer used.
- Region: This entry connects to Datadog US1.
- Tool changes: Tool names, parameters, permissions, and available toolsets change.
Configuration
Request headers
| Header | Description | Required |
|---|---|---|
Authorization | Optional. Use a Datadog PAT or SAT when OAuth is unavailable. | No |
Remote runtime
- Fixed U R L
https://mcp.datadoghq.com/v1/mcp