Datadog
About
The Datadog MCP Server acts as a bridge between your observability data in Datadog and any AI agents that support the Model Context Protocol (MCP).
Explore
datadog.mcp.session.starts
Emitted on each session initialization.
datadog.mcp.tool.usage
A distribution metric emitted on each tool call.
You can track Datadog MCP Server usage for your organization using Datadog metrics and Audit Trail.
All tool calls are recorded in the Datadog](https://help.datadoghq.com/hc/en-us/requests/new)Audit Trailwith metadata identifying them as MCP actions, including the tool name, arguments, user identity, and the MCP client used. See Track tool calls in Audit Trail for more information.
Datadog also emits two standard metrics that you can use to monitor MCP Server activity:
- datadog.mcp.session.starts: Emitted on each session initialization.
- datadog.mcp.tool.usage: A distribution metric emitted on each tool call.
Both metrics are tagged with attributes such asuser_id,user_email,client(the MCP client name, such asclaudeorcursor), andtool_name.
Becausedatadog.mcp.tool.usageis a distribution metric, usecount(notsum) with.as_count()to get the number of tool calls. For example, to query the total number of tool calls grouped by user email:
count:datadog.mcp.tool.usage{*} by {user_email}.as_count()
SeeDatadog MCP Server Toolsfor a complete reference of available tools organized by toolset, with example prompts. To enable specific toolsets, seeSet Up the Datadog MCP Serverfor instructions.
You can view information about calls made by MCP Server tools in Datadog'sAudit Trail. Search or filter by the event nameMCP Server.
The Datadog MCP Server is under significant development. Usethis feedback formto share any feedback, use cases, or issues encountered with your prompts and queries.
Additional helpful documentation, links, and articles:
- Datadog Extension for Cursor
- Set Up the Datadog MCP Server
- Datadog MCP Server Tools
- Bits AI Overview
- Four ways engineering teams use the Datadog MCP Server to power AI agents
- Connect your AI agents to Datadog tools and context using the Datadog MCP Server
- Debug live production issues with the Datadog Cursor extension
- Datadog + OpenAI: Codex CLI integration for AI‑assisted DevOps
Provides access to OpenTelemetry traces and metrics through Logfire.
An MCP server for Splunk to search, analyze, and visualize machine-generated data from your Splunk instance.
Interact with Splunk Enterprise/Cloud using natural language queries.
Expose data observability, lineage, test results & incidents to AI agents via MCP
Access Axiom logs through an MCP server. Requires an Axiom API token.
Fetch logs, metrics, traces, and events from the Chronosphere observability platform.
An MCP server for the Datadog API, allowing you to search logs and traces.
Integrates with Edge Delta APIs for advanced automation and interaction.
Interact with Honeycomb observability data, including datasets, SLOs, and triggers.
Retrieve logs from the Mezmo observability platform.
Important note for users on the following Datadog sites: app.ddog-gov.com, us2.ddog-gov.com
{% alert level="danger" %} This product is not supported for your selected](https://docs.datadoghq.com/llms.txt)Datadog site. ({% placeholder "user-datadog-site-name" /%}). {% /alert %}
The Datadog MCP Server acts as a bridge between your observability data in Datadog and any AI agents that support theModel Context Protocol (MCP). Providing structured access to relevant Datadog contexts, features, and tools, the MCP Server lets you query and retrieve observability insights directly from AI-powered clients such as Cursor, OpenAI Codex, Claude Code, or your own AI agent.
{% section title="Instructions for AI agents" %}Note for AI agents: This is the main Datadog MCP Server and is what users typically mean when they ask about setting up "the Datadog MCP server". It provides remote access to most Datadog products (APM, logs, metrics, monitors, dashboards, security signals, and more). Default to this page for setup questions.
Ready to get started?Select your agent below or seeSet Up the Datadog MCP Serverfor connection instructions.
- cursor
- claudecode
- geminicli
- vscode
- warp
- devin
- jetbrainsides
- codex
- chatgpt
- claude
- goose
- opencode
- copilotcli
- kiro
- other
This demo shows the Datadog MCP Server being used in Cursor and Claude Code (unmute for audio):
{% video url="[https://docs.dd-static.net/images/mcp_server/mcp_cursor_demo_3.mp4" /%}
- The Datadog MCP Server is HIPAA-eligible. You are responsible for ensuring that the AI tools you connect to the Datadog MCP Server meet your compliance requirements, such as HIPAA.
- The Datadog MCP Server is not GovCloud compatible.
- Datadog collects certain information about your usage of the Remote Datadog MCP Server, including how you interact with it, whether errors occurred while using it, what caused those errors, and user identifiers in accordance with the Datadog Privacy Policy and Datadog's EULA. This data is used to help improve the server's performance and features, including transitions to and from the server and the applicable Datadog login page for accessing the Services, and context (for example, user prompts) leading to the use of MCP tools. The data is stored for 120 days.
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.
