Datadog MCP Server

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). 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.

Disclaimers

• 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.

Fair-use rate limits

The MCP Server comes with the following fair-use limits:

• 50 requests/10 seconds tool call burst limits
• 5000 daily tool calls
• 50,000 monthly tool calls.

These limits are subject to change and can be adjusted if your use case requires more. Please contact Datadog support for requests or questions.

Monitoring the Datadog MCP Server tool calls

You can track Datadog MCP Server usage for your organization using Datadog metrics and Audit Trail.

All tool calls are recorded in the Datadog Audit Trail with 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.calls: Emitted on each tool call, tagged with tool_name.

Both metrics are tagged with user_id, user_email, and client (the MCP client name, such as claude or cursor).

Available tools{% #available-tools %}

See Datadog MCP Server Tools for a complete reference of available tools organized by toolset, with example prompts. To enable specific toolsets, see Set Up the Datadog MCP Server for instructions.

Context efficiency

The Datadog MCP Server is optimized to provide responses in a way that AI agents get relevant context without being overloaded with unnecessary information. For example:

• Responses are truncated based on the estimated length of responses each tool provides. The tools respond to AI agents with instructions on how to request more information if the response was truncated.
• Most tools have a max_tokens parameter that enables AI agents to request less or more information.

Track tool calls in Audit Trail

You can view information about calls made by MCP Server tools in Datadog's Audit Trail. Search or filter by the event name MCP Server.

Feedback

The Datadog MCP Server is under significant development. Use this feedback form to share any feedback, use cases, or issues encountered with your prompts and queries.