Datadog MCP Server
Aembit supports the official Datadog MCP server, which lets AI Agent: A software workload that authenticates to systems, requests credentials, and accesses resources, either on behalf of a person or on its own. Aembit secures AI agents with the same identity-first model it uses for any workload. User-driven agents such as Claude Desktop also carry a blended identity that ties access to both the user and the agent.Learn more query monitors, logs, metrics, and other Datadog data through Model Context Protocol: A standard protocol for AI agent and server interactions that defines how AI assistants communicate with external tools and data sources.Learn more(opens in new tab) tools.
The following steps configure Datadog as an MCP Server: A server that implements the Model Context Protocol to provide tools, resources, or data to AI agents and MCP clients.Learn more(opens in new tab) behind the Aembit MCP Identity Gateway: A component that brokers MCP traffic between MCP clients and target MCP servers, validating authorization and presenting Aembit-managed credentials on each request.Learn more. Each user authenticates with their own Datadog identity, and MCP Identity Gateway injects their token into MCP requests.
This guide builds the Gateway-to-Server Policy: The Access Policy that authorizes the MCP Identity Gateway to access an MCP server on behalf of authenticated users—the Gateway itself is the Client Workload. Also called right-side auth; each MCP server behind the Gateway needs its own.Learn more—the second of the two Access Policy: Access Policies define, enforce, and audit access between Client and Server Workloads by cryptographically verifying workload identity and contextual factors rather than relying on static secrets.Learn more the MCP Identity Gateway requires. You create the first, the Client-to-Gateway Policy: The Access Policy that validates which MCP client can connect to the MCP Identity Gateway and authenticates users through your Identity Provider. Also called left-side auth; you create one per MCP client and Gateway combination.Learn more, during Gateway setup.
Prerequisites
Section titled “Prerequisites”Before you begin, ensure you have the following:
- A Datadog administrator who can change Organization Settings, to enable MCP access and add the Callback URL to the redirect URL allowlist
- A configured Aembit MCP Identity Gateway
Requirements and considerations
Section titled “Requirements and considerations”Before you configure Datadog, review these requirements and behaviors specific to the Datadog MCP server.
- Use User-Based Auth. Aembit supports User-Based Auth for Datadog.
- Allowlist the Callback URL first. Until the Credential Provider’s Callback URL is on your organization’s
MCP OAuth Redirect URLs list, user authorization fails with
invalid_redirect_uri, even though Discover succeeds. - Match your Datadog site. The MCP server host must belong to the site that hosts your Datadog organization. A host for another site fails to connect or authorize.
- No government sites. Datadog does not offer the MCP server on the
US1-FEDandUS2-FEDsites. - Network restrictions apply. If your organization enables the Datadog IP allowlist, allow the network address that MCP Identity Gateway connects from.
Enable the MCP server in Datadog
Section titled “Enable the MCP server in Datadog”A Datadog organization administrator turns on MCP access and grants the MCP permissions before users can authenticate. Each Datadog site serves the MCP server from its own host, so find yours first.
-
Find your organization’s Datadog site and its MCP server host. Use this host wherever this guide shows
mcp.<datadog-site>.Datadog site MCP server host US1 mcp.datadoghq.comUS3 mcp.us3.datadoghq.comUS5 mcp.us5.datadoghq.comEU1 mcp.datadoghq.euAP1 mcp.ap1.datadoghq.comAP2 mcp.ap2.datadoghq.comUK1 mcp.uk1.datadoghq.com -
In Datadog, go to Organization Settings and enable MCP Access. Enable MCP Write Access too if users need tools that create or change resources.
-
Confirm that each user’s role has the
mcp_readpermission, andmcp_writefor write tools. The Datadog Standard Role includes both. For a custom role, go to Organization Settings > Roles, edit the role, and select MCP Read and MCP Write. -
Grant the standard Datadog permissions for the data each user’s tools reach, such as Monitors Read for monitor queries.
For details, see MCP Server setup in the Datadog documentation.
Configure the Credential Provider
Section titled “Configure the Credential Provider”Datadog registers the OAuth client when you run Discover, so you do not create an application in Datadog. Datadog accepts only the redirect URLs your organization allowlists, so you add the Callback URL of the MCP User-Based Access Token Credential Provider: Credential Providers obtain the specific access credentials—such as API keys, OAuth tokens, or temporary cloud credentials—that Client Workloads need to authenticate to Server Workloads.Learn more to that allowlist.
- Log in to your Aembit Tenant: Aembit Tenants serve as isolated, dedicated environments within Aembit that provide complete separation of administrative domains and security configurations.Learn more.
- Go to Credential Providers and click + New.
- Enter a Name and select MCP User-Based Access Token as the Credential Type.
- Set MCP Server URL to
https://mcp.<datadog-site>/v1/mcp, using the host for your Datadog site. Click Discover to populate the Client Id, Authorization URL, and Token URL. - Make sure PKCE Required is on, then click Save.
- Copy the read-only Callback URL from the saved Credential Provider.
- In Datadog, go to Organization Settings and open MCP OAuth Redirect URLs.
- Enter the Callback URL you copied and click Add URL. If your organization does not show MCP OAuth Redirect URLs, ask Datadog support to allowlist the URL.
When you create the Access Policy that grants MCP Identity Gateway access to Datadog, use the Select Existing tab. Select the Credential Provider you saved here and click Use Selected. Do not create another Credential Provider: its Callback URL is not on the Datadog allowlist.
For details, see Adding OAuth clients in the Datadog documentation.
User authorization
Section titled “User authorization”Each user authorizes access to Datadog when they first connect through MCP Identity Gateway. The MCP User-Based Access Token Credential Provider has no administrator Authorize step.
Create the Server Workload
Section titled “Create the Server Workload”-
Go to Server Workloads in the left sidebar and click + New.
-
Configure the following fields, with your Datadog site’s MCP server host as the Host:
Field Value Name A user-friendly name Host mcp.<datadog-site>Application Protocol MCP Port 443 with TLS URL Path /v1/mcpAuthentication method HTTP Authentication Authentication scheme Bearer -
Click Save.
Create an Access Policy
Section titled “Create an Access Policy”On the Select Existing tab, select the Credential Provider you saved during Datadog setup and click Use Selected. The linked setup procedure describes creating a new Credential Provider. Reuse yours, because Datadog allowlisted only its Callback URL.
This section creates the Gateway-to-Server Access Policy, which authorizes MCP Identity Gateway to access Datadog on behalf of authenticated users.
Create an Access Policy linking MCP Identity Gateway (as the Client Workload: Client Workloads represent AI agents, software applications, scripts, or automated processes that initiate access requests to Server Workloads. They can act on behalf of a user under blended identity or operate autonomously, as when one service calls another.Learn more), the Credential Provider you created, and the Server Workload for Datadog.
For step-by-step instructions, including the Client Workload settings that identify MCP Identity Gateway, see Create the gateway-to-server Access Policy.
Verify
Section titled “Verify”After a user authorizes access, the Aembit AI Access Authorized page lists the Datadog MCP Server as Ready. The AI agent can then call Datadog MCP tools through MCP Identity Gateway.