To allow your users to securely query observability data, monitors, and dashboards using their AI clients, you can configure the Datadog Model Context Protocol (MCP) server within the JumpCloud AI Gateway.
Prerequisites
- Before configuring specific enterprise applications, we recommend reviewing the Get Started: AI Gateway guide to familiarize yourself with the gateway architecture and core AI concepts (such as MCP servers and AI clients).
Completing Application Setup
Before you can connect this server to JumpCloud, you must configure the required authentication parameters within your Datadog workspace. See Datadog’s support documentation Set Up the Datadog MCP Server to learn more.
Ensure you meet the following prerequisites:
- Grant MCP Permissions: Users with the Datadog Standard Role have mcp_read and mcp_write permissions by default, so no additional configuration is required. If you’re using custom roles, you’ll need to grant these permissions for each role. See Datadog’s Required Permissions to learn more.
- Determine Authentication Method: Your supported authentication method depends on the JumpCloud application you associate the server with:
- API Token: If you plan to associate the server with JumpCloud's prebuilt SAML Single Sign-On (SSO) application for Datadog, you must use API token authentication. Users must create a Personal Access Token (PAT) in Datadog and enter it during gateway authentication. See Datadog’s Personal Access Tokens to learn more.
- OAuth: You can only use OAuth authentication if you associate the MCP server with an OAuth-based SSO application (such as a custom OIDC connector) or a bookmark.
- Add Redirect URLs: If you can use OAuth, you must allowlist one of the following JumpCloud redirect URLs in Datadog under Organization Settings > MCP OAuth Redirect URLs. Datadog's MCP server only allows well-known AI clients, so you must allow the correct JumpCloud URL based on your region:
- US: https://console.jumpcloud.com/userconsole/mcp/servers/callback
- EU: https://console.eu.jumpcloud.com/userconsole/mcp/servers/callback
- IN: https://console.in.jumpcloud.com/userconsole/mcp/servers/callback
Configuring the Server in JumpCloud
See Adding MCP Servers in Configure AI Gateway Integrations and use the following values to configure this server:
- App: Select Datadog (if you have an existing SSO application or bookmark), or click + Add App to create it
If your existing Datadog app uses SAML SSO and you want to use OAuth authentication, you must click + Add App to create a custom bookmark for this server instead. See Connect Apps Using Bookmarks to learn more.
- Name: Enter a name, for example Datadog.
- Prefix: Enter a value to prepend to MCP tool names.
- Note: Prefixes must be unique. Maximum 8 characters, letters and numbers only.
- URL: Enter the Datadog MCP server URL for your specific regional site. See Datadog's Getting Started with Datadog Sites to learn more. For example, the US1 site endpoint: https://mcp.datadoghq.com/v1/mcp
- Note: Datadog supports "toolsets" to limit the data exposed to the AI client. To explicitly restrict toolsets and save context window space, append them to the URL. For example: ?toolsets=apm,llmobs
- MCP Authentication method: Select OAuth or API Token.
- App API documentation link (API Token only): Enter https://docs.datadoghq.com/account_management/personal-access-tokens/
Your users will now see Datadog listed as an available application when they authenticate their AI clients through the JumpCloud AI Gateway.