Datadog MCP Server

Base URL: https://api.datadoghq.com

Category	Analytics
Tools	699
Auth	API Key, OAuth2

API Info

• Contact: Datadog Support (support@datadoghq.com) — https://www.datadoghq.com/support/

---

Install

Quick Start (recommended)

OAUTH2_CLIENT_ID=YOUR_OAUTH2_CLIENT_ID \
OAUTH2_CLIENT_SECRET=YOUR_OAUTH2_CLIENT_SECRET \
API_KEY_AUTH=YOUR_API_KEY_AUTH \
APP_KEY_AUTH_API_KEY=YOUR_APP_KEY_AUTH_API_KEY \
SERVER_SITE=YOUR_SERVER_SITE \
SERVER_SUBDOMAIN=YOUR_SERVER_SUBDOMAIN \
uvx mcparmory-datadog

With pip

pip install mcparmory-datadog
OAUTH2_CLIENT_ID=YOUR_OAUTH2_CLIENT_ID \
OAUTH2_CLIENT_SECRET=YOUR_OAUTH2_CLIENT_SECRET \
API_KEY_AUTH=YOUR_API_KEY_AUTH \
APP_KEY_AUTH_API_KEY=YOUR_APP_KEY_AUTH_API_KEY \
SERVER_SITE=YOUR_SERVER_SITE \
SERVER_SUBDOMAIN=YOUR_SERVER_SUBDOMAIN \
mcparmory-datadog

MCP Client Configuration

Add to your MCP client config (e.g. Claude Desktop, Cursor, Codex):

{
  "mcpServers": {
    "datadog": {
      "command": "uvx",
      "args": ["mcparmory-datadog"],
      "env": {
        "OAUTH2_CLIENT_ID": "YOUR_OAUTH2_CLIENT_ID",
        "OAUTH2_CLIENT_SECRET": "YOUR_OAUTH2_CLIENT_SECRET",
        "API_KEY_AUTH": "YOUR_API_KEY_AUTH",
        "APP_KEY_AUTH_API_KEY": "YOUR_APP_KEY_AUTH_API_KEY",
        "SERVER_SITE": "YOUR_SERVER_SITE",
        "SERVER_SUBDOMAIN": "YOUR_SERVER_SUBDOMAIN"
      }
    }
  }
}

Set OAUTH2_SCOPES to a comma-separated list of scopes your app requires (e.g. OAUTH2_SCOPES=scope_a,scope_b). Some OAuth2 providers may also use additional scope env vars such as OAUTH2_USER_SCOPES; open .env to see all generated scope buckets and descriptions.

---

Credentials

Set the following environment variables (via MCP client env config, shell export, or .env file):

• OAUTH2_CLIENT_ID — OAuth2 client ID
• OAUTH2_CLIENT_SECRET — OAuth2 client secret
• API_KEY_AUTH — API Key Authentication (DD-API-KEY)
• APP_KEY_AUTH_API_KEY — API Key Authentication (DD-APPLICATION-KEY)
• SERVER_SITE — The regional site for Datadog customers. (default: datadoghq.com)
• SERVER_SUBDOMAIN — The subdomain where the API is deployed. (default: api)

Do not commit credentials to version control.

OAuth2

Add this redirect URI to your OAuth provider's allowed redirect URIs:

http://localhost:9400/callback

If you change OAUTH2_CALLBACK_PORT in .env, update the redirect URI to match.

On first use, a browser window opens automatically for OAuth authorization. Grant access when prompted — tokens are saved to tokens/oauth2_tokens.json and refreshed automatically.

Re-authorization: Delete tokens/oauth2_tokens.json and restart the server.

---

Run Locally

First, configure your credentials in .env (see Credentials above).

pip install -r requirements.txt
python server.py

Connect MCP Client

Edit .mcp.json and replace <SERVER_DIR> with the absolute path to this directory, then add to your MCP client configuration.

Example (if server is at /home/user/mcp-servers/datadog):

{
  "mcpServers": {
    "datadog": {
      "command": "python",
      "args": ["/home/user/mcp-servers/datadog/server.py"]
    }
  }
}

---

Docker

Pre-built image (recommended)

docker run -p 8000:8000 -p 9400:9400 -v ./tokens:/app/tokens \
  -e OAUTH2_CLIENT_ID=YOUR_OAUTH2_CLIENT_ID \
  -e OAUTH2_CLIENT_SECRET=YOUR_OAUTH2_CLIENT_SECRET \
  -e API_KEY_AUTH=YOUR_API_KEY_AUTH \
  -e APP_KEY_AUTH_API_KEY=YOUR_APP_KEY_AUTH_API_KEY \
  -e SERVER_SITE=YOUR_SERVER_SITE \
  -e SERVER_SUBDOMAIN=YOUR_SERVER_SUBDOMAIN \
  ghcr.io/mcparmory/datadog:latest

Build from source

First, configure your credentials in .env (see Credentials above).

docker build -t datadog .
mkdir -p tokens
docker run -p 8000:8000 -p 9400:9400 -v ./tokens:/app/tokens --env-file .env datadog

Before running, make sure ports 8000, 9400 are free. If you changed the callback port in .env, update the -p port mapping and your OAuth provider's redirect URI to match.

On first run, the server prints an authorization URL — check docker logs for the URL. Open it in your browser to complete OAuth consent. Tokens are persisted to ./tokens/ via the volume mount so re-authorization is not needed on subsequent runs.

MCP client config (Docker)

For Docker, use SSE transport in your MCP client config:

{
  "mcpServers": {
    "datadog": {
      "type": "sse",
      "url": "http://localhost:8000/sse"
    }
  }
}

---

Files

• .env - Credentials and server configuration
• .mcp.json - MCP client config template
• Dockerfile - Container build
• LICENSE - MIT license for this generated code
• requirements.txt - Python dependencies
• README.md - This file
• server.py - MCP server entry point
• _auth.py - Authentication handlers
• _models.py - Request/response models
• _validators.py - Input validation

Note: Files starting with . are hidden by default on macOS/Linux. Use ls -a in terminal or enable "Show hidden files" in your file manager to see .env and .mcp.json.

---

_{Generated by MCP Blacksmith · Quickstart docs · Report a bug}