How to integrate Datadog MCP with Claude Code

Framework Integration Gradient
Datadog Logo
Claude Code Logo
divider

Introduction

Manage your Datadog directly from Claude Code with zero worries about OAuth hassles, API-breaking issues, or reliability and security concerns.

You can do this in two different ways:

  1. Via Rube - Direct and easiest approach
  2. Via Composio SDK - Programmatic approach with more control

Why Rube?

Rube is a universal MCP server with access to 850+ SaaS apps. It ensures just-in-time tool loading so Claude can access the tools it needs, a remote workbench for programmatic tool calling and handling large tool responses out of the LLM context window, ensuring the LLM context window remains clean.

Connect Datadog to Claude Code with Rube

1. Get the MCP URL

Copy and paste the below command in Claude Code to add Rube MCP.

Terminal

2. Authenticate Rube

Run /mcp to view Rube

bash
/mcp
Run /mcp to view Rube in Claude Code
Click on Rube to authenticate
Authentication flow complete

3. Ensure it's connected

Run /mcp again to verify the connection. Now, do whatever you want with Claude Code and Datadog.

Rube connected successfully

Supported Tools & Triggers

Tools
Create DashboardCreate a dashboard in datadog.
Create downtimeCreates a new downtime in datadog to suppress alerts during maintenance windows or planned outages.
Create eventCreates a new event in datadog.
Create monitorCreates a new datadog monitor to track metrics, logs, or other data sources with configurable alerting thresholds and notifications.
Create SLOCreate a service level objective (slo) in datadog.
Create Synthetic API TestCreate a synthetic api test in datadog.
Create WebhookCreate a webhook in datadog.
Delete DashboardDelete a dashboard in datadog.
Delete monitorDeletes a datadog monitor permanently.
Get DashboardGet a specific dashboard from datadog.
Get monitorRetrieves detailed information about a specific datadog monitor, including its current state, configuration, and any active downtimes.
Get Service DependenciesGet service dependency mapping from datadog apm.
Get Synthetics LocationsTool to retrieve all available public and private locations for synthetic tests in datadog.
Get host tagsRetrieves all tags associated with a specific host in datadog.
Get Trace by IDGet detailed information about a specific trace by its id.
Get usage summaryRetrieves usage summary information from datadog including api calls, hosts, containers, and other billable usage metrics.
List All TagsList all tags from datadog.
List API KeysList api keys in datadog.
List APM ServicesList apm services from datadog.
List AWS IntegrationList aws integrations in datadog.
List dashboardsLists all datadog dashboards with basic information.
List eventsLists events from datadog within a specified time range.
List hostsLists all hosts in your datadog infrastructure with detailed information including metrics, tags, and status.
List IncidentsList incidents from datadog.
List Log IndexesTool to retrieve a list of all log indexes configured in datadog.
List monitorsGet all monitor details.
List RolesList roles from datadog organization.
List service checksLists service checks from datadog.
List SLOsList service level objectives (slos) from datadog.
List Synthetics TestsList synthetics tests from datadog.
List UsersList users from datadog organization.
List WebhooksList webhooks from datadog.
Mute MonitorMute a monitor in datadog.
Query metricsQueries datadog metrics and returns time series data.
Search logsSearches datadog logs with advanced filtering capabilities.
Search Spans AnalyticsSearch and analyze span data with aggregations in datadog.
Search TracesSearch for traces in datadog apm.
Submit metricsSubmits custom metrics to datadog.
Unmute MonitorUnmute a monitor in datadog.
Update DashboardUpdate a dashboard in datadog.
Update host tagsUpdates tags for a specific host in datadog.
Update monitorUpdates an existing datadog monitor with new configuration, thresholds, or notification settings.

What is the Datadog MCP server, and what's possible with it?

The Datadog MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Datadog account. It provides structured and secure access to your monitoring and observability platform, so your agent can perform actions like creating dashboards, managing monitors, scheduling downtimes, and tracking key events on your behalf.

  • Custom dashboard creation and management: Direct your agent to build new dashboards or retrieve detailed information about existing dashboards for unified infrastructure and application monitoring.
  • Monitor setup and deletion: Easily have your agent create new monitors to track critical metrics or remove outdated ones to keep your alerting system relevant.
  • Automated downtime scheduling: Let your agent schedule maintenance windows by creating downtimes that suppress alerts during planned outages or deployments.
  • Event tracking and logging: Ask your agent to create and log significant events—like deployments or configuration changes—so your team always stays informed.
  • Service level objectives and synthetic testing: Instruct your agent to define SLOs or set up synthetic API tests for continuous reliability and performance tracking.

Connecting Datadog via Tool Router

Tool Router is the underlying tech that powers Rube. It's a universal gateway that does everything Rube does but with much more programmatic control. You can programmatically generate an MCP URL with the app you need (here Datadog) for even more tool search precision. It's secure and reliable.

How the Tool Router works

The Tool Router follows a three-phase workflow:

  1. Discovery: Searches for tools matching your task and returns relevant toolkits with their details.
  2. Authentication: Checks for active connections. If missing, creates an auth config and returns a connection URL via Auth Link.
  3. Execution: Executes the action using the authenticated connection.

Step-by-step Guide

Prerequisites

Before starting, make sure you have:
  • Claude Pro, Max, or API billing enabled Anthropic account
  • Composio API Key
  • A Datadog account
  • Basic knowledge of Python or TypeScript

Install Claude Code

bash
# macOS, Linux, WSL
curl -fsSL https://claude.ai/install.sh | bash

# Windows PowerShell
irm https://claude.ai/install.ps1 | iex

# Windows CMD
curl -fsSL https://claude.ai/install.cmd -o install.cmd && install.cmd && del install.cmd

To install Claude Code, use one of the following methods based on your operating system:

Set up Claude Code

bash
cd your-project-folder
claude

Open a terminal, go to your project folder, and start Claude Code:

  • Claude Code will open in your terminal
  • Follow the prompts to sign in with your Anthropic account
  • Complete the authentication flow
  • Once authenticated, you can start using Claude Code
Claude Code initial setup showing sign-in prompt
Claude Code terminal after successful login

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here

Create a .env file in your project root with the following variables:

  • COMPOSIO_API_KEY authenticates with Composio (get it from Composio dashboard)
  • USER_ID identifies the user for session management (use any unique identifier)

Install Composio library

pip install composio-core python-dotenv

Install the Composio Python library to create MCP sessions.

  • composio-core provides the core Composio functionality
  • python-dotenv loads environment variables from your .env file

Generate Composio MCP URL

import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()

COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
USER_ID = os.getenv("USER_ID")

composio_client = Composio(api_key=COMPOSIO_API_KEY)

composio_session = composio_client.create(
    user_id=USER_ID,
    toolkits=["datadog"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url

print(f"MCP URL: {COMPOSIO_MCP_URL}")
print(f"\nUse this command to add to Claude Code:")
print(f'claude mcp add --transport http datadog-composio "{COMPOSIO_MCP_URL}" --headers "X-API-Key:{COMPOSIO_API_KEY}"')

Create a script to generate a Composio MCP URL for Datadog. This URL will be used to connect Claude Code to Datadog.

What's happening:

  • We import the Composio client and load environment variables
  • Create a Composio instance with your API key
  • Call create() to create a Tool Router session for Datadog
  • The returned mcp.url is the MCP server URL that Claude Code will use
  • The script prints this URL so you can copy it

Run the script and copy the MCP URL

python generate_mcp_url.py

Run your Python script to generate the MCP URL.

  • The script connects to Composio and creates a Tool Router session
  • It prints the MCP URL and the exact command you need to run
  • Copy the entire claude mcp add command from the output

Add Datadog MCP to Claude Code

bash
claude mcp add --transport http datadog-composio "YOUR_MCP_URL_HERE" --headers "X-API-Key:YOUR_COMPOSIO_API_KEY"

# Then restart Claude Code
exit
claude

In your terminal, add the MCP server using the command from the previous step. The command format is:

  • claude mcp add registers a new MCP server with Claude Code
  • --transport http specifies that this is an HTTP-based MCP server
  • The server name (datadog-composio) is how you'll reference it
  • The URL points to your Composio Tool Router session
  • --headers includes your Composio API key for authentication

After running the command, close the current Claude Code session and start a new one for the changes to take effect.

Verify the installation

bash
claude mcp list

Check that your Datadog MCP server is properly configured.

  • This command lists all MCP servers registered with Claude Code
  • You should see your datadog-composio entry in the list
  • This confirms that Claude Code can now access Datadog tools

If everything is wired up, you should see your datadog-composio entry listed:

Claude Code MCP list showing the toolkit MCP server

Authenticate Datadog

The first time you try to use Datadog tools, you'll be prompted to authenticate.

  • Claude Code will detect that you need to authenticate with Datadog
  • It will show you an authentication link
  • Open the link in your browser (or copy/paste it)
  • Complete the Datadog authorization flow
  • Return to the terminal and start using Datadog through Claude Code

Once authenticated, you can ask Claude Code to perform Datadog operations in natural language. For example:

  • "Create downtime for nightly maintenance window"
  • "List all monitors tracking CPU usage"
  • "Create synthetic API test for login endpoint"

Complete Code

Here's the complete code to get you started with Datadog and Claude Code:

import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()

COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
USER_ID = os.getenv("USER_ID")

composio_client = Composio(api_key=COMPOSIO_API_KEY)

composio_session = composio_client.create(
    user_id=USER_ID,
    toolkits=["datadog"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url

print(f"MCP URL: {COMPOSIO_MCP_URL}")
print(f"\nUse this command to add to Claude Code:")
print(f'claude mcp add --transport http datadog-composio "{COMPOSIO_MCP_URL}" --headers "X-API-Key:{COMPOSIO_API_KEY}"')

Conclusion

You've successfully integrated Datadog with Claude Code using Composio's MCP server. Now you can interact with Datadog directly from your terminal using natural language commands.

Key features of this setup:

  • Terminal-native experience without switching contexts
  • Natural language commands for Datadog operations
  • Secure authentication through Composio's managed MCP
  • Tool Router for dynamic tool discovery and execution

Next steps:

  • Try asking Claude Code to perform various Datadog operations
  • Add more toolkits to your Tool Router session for multi-app workflows
  • Integrate this setup into your development workflow for increased productivity

You can extend this by adding more toolkits, implementing custom workflows, or building automation scripts that leverage Claude Code's capabilities.

How to build Datadog MCP Agent with another framework

FAQ

What are the differences in Tool Router MCP and Datadog MCP?

With a standalone Datadog MCP server, the agents and LLMs can only access a fixed set of Datadog tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Datadog and many other apps based on the task at hand, all through a single MCP endpoint.

Can I use Tool Router MCP with Claude Code?

Yes, you can. Claude Code fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Datadog tools.

Can I manage the permissions and scopes for Datadog while using Tool Router?

Yes, absolutely. You can configure which Datadog scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

How safe is my data with Composio Tool Router?

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Datadog data and credentials are handled as safely as possible.

Used by agents from

Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai

Never worry about agent reliability

We handle tool reliability, observability, and security so you never have to second-guess an agent action.