Set Up the Datadog MCP Server

Docs > Bits AI > Datadog MCP Server > Set Up the Datadog MCP Server

This page explains how to set up and configure the Datadog MCP Server, which lets you retrieve telemetry insights and manage platform features directly from AI-powered clients.

Installation

Select your client to see setup instructions:

Datadog’s Cursor and VS Code extension includes built-in access to the managed Datadog MCP Server. Benefits include:

No additional MCP Server setup after you install the extension and connect to Datadog.
One-click transitions between multiple Datadog organizations.
Better fixes from Fix in Chat on Code Insights (issues from Error Tracking, Code Vulnerabilities, and Library Vulnerabilities), informed by context from the MCP Server.

To install the extension:

If you previously installed the Datadog MCP Server manually, remove it from the IDE’s configuration to avoid conflicts. Go to Cursor Settings (Shift + Cmd/Ctrl + J) and select the MCP tab.
Install the Datadog extension following these instructions. If you have the extension installed already, make sure it’s the latest version, as new features are released regularly.
Sign in to your Datadog account.
Restart the IDE.
Confirm the Datadog MCP Server is available and the tools are listed: Go to Cursor Settings (Shift + Cmd/Ctrl + J), and select the MCP tab.

You can connect Claude Code to the Datadog MCP Server using remote authentication (HTTP) or local binary authentication (stdio).

Remote authentication

Point your AI agent to the MCP Server endpoint for your regional Datadog site. For example, the endpoint for your selected site () is: .

Command line: Run:

claude mcp add --transport http datadog-mcp

Configuration file: Add to ~/.claude.json:

{
  "mcpServers": {
    "datadog": {
      "type": "http",
      "url": ""
    }
  }
}

Local binary authentication

Use this option if remote authentication is not available. After installation, you typically do not need to update the local binary to benefit from MCP Server updates, as the tools are remote.

Install the Datadog MCP Server binary (macOS and Linux):
```
curl -sSL https://coterm.datadoghq.com/mcp-cli/install.sh | bash
```
This installs the binary to ~/.local/bin/datadog_mcp_cli.
Run datadog_mcp_cli login manually to walk through the OAuth login flow and choose a Datadog site.

Configure Claude Code. Add to ~/.claude.json (replace <USERNAME> with your username):

{
  "mcpServers": {
    "datadog": {
      "type": "stdio",
      "command": "/Users/<USERNAME>/.local/bin/datadog_mcp_cli",
      "args": [],
      "env": {}
    }
  }
}

Or run: claude mcp add datadog --scope user -- ~/.local/bin/datadog_mcp_cli

Claude Desktop has limited support for remote authentication. Use local binary authentication for reliable setup.

Install the Datadog MCP Server binary:
- macOS and Linux: Install the binary to ~/.local/bin/datadog_mcp_cli:
```
curl -sSL https://coterm.datadoghq.com/mcp-cli/install.sh | bash
```
- Windows: Download the Windows version.
Run datadog_mcp_cli login manually to walk through the OAuth login flow and choose a Datadog site.
Configure Claude Desktop to use the Datadog MCP Server. Add to your Claude Desktop configuration (location varies by OS) with the stdio transport pointing to datadog_mcp_cli:
```
{
  "mcpServers": {
    "datadog": {
      "type": "stdio",
      "command": "/Users/<USERNAME>/.local/bin/datadog_mcp_cli",
      "args": [],
      "env": {}
    }
  }
}
```
On Windows, replace the command path with the location of the downloaded .exe file (for example, C:\Users\<USERNAME>\bin\datadog_mcp_cli.exe).

You can connect Codex CLI to the Datadog MCP Server using HTTP transport.

Point your AI agent to the MCP Server endpoint for your regional Datadog site. For example, the endpoint for your selected site () is: .

Edit ~/.codex/config.toml (or your Codex CLI configuration file) to add the Datadog MCP Server with HTTP transport and the endpoint URL for your site. Example configuration ():
```
[mcp_servers.datadog]
url = ""
```
Log in to the Datadog MCP Server by running:
```
codex mcp login datadog
```
This opens your browser to complete the OAuth flow. Codex stores the resulting credentials so you don’t need to log in again until the token expires.

Datadog’s Cursor and VS Code extension includes built-in access to the managed Datadog MCP Server. Benefits include:

No additional MCP Server setup after you install the extension and connect to Datadog.
One-click transitions between multiple Datadog organizations.

To install the extension:

If you previously installed the Datadog MCP Server manually, remove it from the IDE’s configuration to avoid conflicts. Open the command palette (Shift + Cmd/Ctrl + P) and run MCP: Open User Configuration.
Install the Datadog extension following these instructions. If you have the extension installed already, make sure it’s the latest version.
Sign in to your Datadog account.
Restart the IDE.
Confirm the Datadog MCP Server is available and the tools are listed: Open the chat panel, select agent mode, and click the Configure Tools button.

The following clients can connect to the Datadog MCP Server: Goose, Kiro, Kiro CLI, Cline, and other MCP-compatible clients. Use remote authentication when your client supports it. For Cline or when remote authentication is unreliable, use local binary authentication.

Remote authentication

Point your AI agent to the MCP Server endpoint for your regional Datadog site. For example, the endpoint for your selected site () is: .

Add the Datadog MCP Server to your client’s configuration using the HTTP transport and the endpoint above. Example config file locations:

Client	Configuration file
Gemini CLI	`~/.gemini/settings.json`
Kiro CLI	`~/.kiro/settings/mcp.json`

Example JSON configuration ():

{
  "mcpServers": {
    "datadog": {
      "type": "http",
      "url": ""
    }
  }
}

Local binary authentication

Local authentication is recommended for Cline and when remote authentication is unreliable.

Install the Datadog MCP Server binary:
- macOS and Linux: Install the binary to ~/.local/bin/datadog_mcp_cli:
```
curl -sSL https://coterm.datadoghq.com/mcp-cli/install.sh | bash
```
- Windows: Download the Windows version.
Run datadog_mcp_cli login manually to walk through the OAuth login flow and choose a Datadog site.
Configure your AI client to use the stdio transport with datadog_mcp_cli as the command. Example:
```
{
  "mcpServers": {
    "datadog": {
      "type": "stdio",
      "command": "/Users/<USERNAME>/.local/bin/datadog_mcp_cli",
      "args": [],
      "env": {}
    }
  }
}
```
On Windows, replace the command path with the location of the downloaded .exe file (for example, C:\Users\<USERNAME>\bin\datadog_mcp_cli.exe).

Supported clients

Client	Developer	Notes
Cursor	Cursor	Datadog Cursor & VS Code extension recommended.
Claude Code	Anthropic
Claude Desktop	Anthropic	Limited support for remote authentication. Use local binary authentication as needed.
Codex CLI	OpenAI
VS Code	Microsoft	Datadog Cursor & VS Code extension recommended.
Goose, Kiro, Kiro CLI, Cline	Various	See the Other tab above. Use local binary authentication for Cline if remote authentication is unreliable.

The Datadog MCP Server is under significant development, and additional supported clients may become available.

Authentication

The MCP Server uses OAuth 2.0 for authentication. If you cannot go through the OAuth flow (for example, on a server), you can provide a Datadog API key and application key as DD_API_KEY and DD_APPLICATION_KEY HTTP headers.

For example, based on your selected Datadog site ():

{
  "mcpServers": {
    "datadog": {
      "type": "http",
      "url": "",
      "headers": {
          "DD_API_KEY": "<YOUR_API_KEY>",
          "DD_APPLICATION_KEY": "<YOUR_APPLICATION_KEY>"
      }
    }
  }
}

For security, use a scoped API key and application key from a service account that has only the required permissions.

Test access to the MCP Server

Install the MCP inspector, a developer tool for testing and debugging MCP servers.
```
npx @modelcontextprotocol/inspector
```
In the inspector’s web UI, for Transport Type, select Streamable HTTP.
For URL, enter the MCP Server endpoint for your regional Datadog site.
For example, for :
Click Connect, then go to Tools > List Tools.
Check if the available tools appear.