From f487ecbbbe6c2a19d3c3040a044b7d363ed48ce6 Mon Sep 17 00:00:00 2001 From: Sumedha Mehta Date: Thu, 19 Feb 2026 15:34:30 -0500 Subject: [PATCH 1/5] Make MCP Server docs use dynamic region URLs - Add mcp_server_endpoint to regions.config.js for all supported sites - Replace hardcoded MCP URLs in setup.md with region-param shortcodes - Replace hardcoded MCP URLs in bits_ai/mcp_server/_index.md Toolsets section - Endpoint and examples now update based on docs site selector (US1, US3, EU1, etc.) Co-authored-by: Cursor --- assets/scripts/config/regions.config.js | 9 +++++ content/en/bits_ai/mcp_server/_index.md | 14 ++++---- content/en/bits_ai/mcp_server/setup.md | 44 ++++++++++--------------- 3 files changed, 33 insertions(+), 34 deletions(-) diff --git a/assets/scripts/config/regions.config.js b/assets/scripts/config/regions.config.js index 633db1d3a09..602d9e899a1 100644 --- a/assets/scripts/config/regions.config.js +++ b/assets/scripts/config/regions.config.js @@ -652,6 +652,15 @@ export default { ap2: 'intake.synthetics.ap2.datadoghq.com', gov: 'intake.synthetics.ddog-gov.com' }, + mcp_server_endpoint: { + us: 'https://mcp.datadoghq.com/api/unstable/mcp-server/mcp', + us3: 'https://mcp.us3.datadoghq.com/api/unstable/mcp-server/mcp', + us5: 'https://mcp.us5.datadoghq.com/api/unstable/mcp-server/mcp', + eu: 'https://mcp.datadoghq.eu/api/unstable/mcp-server/mcp', + ap1: 'https://mcp.ap1.datadoghq.com/api/unstable/mcp-server/mcp', + ap2: 'https://mcp.ap2.datadoghq.com/api/unstable/mcp-server/mcp', + gov: 'N/A' + }, cursor_mcp_install_deeplink: { us: 'cursor://anysphere.cursor-deeplink/mcp/install?name=datadog-onboarding-us1&config=eyJ1cmwiOiJodHRwczovL21jcC5kYXRhZG9naHEuY29tL2FwaS91bnN0YWJsZS9tY3Atc2VydmVyL21jcD90b29sc2V0cz1vbmJvYXJkaW5nIiwidHlwZSI6Im9hdXRoIn0=', us3: 'cursor://anysphere.cursor-deeplink/mcp/install?name=datadog-onboarding-us3&config=eyJ1cmwiOiJodHRwczovL21jcC51czMuZGF0YWRvZ2hxLmNvbS9hcGkvdW5zdGFibGUvbWNwLXNlcnZlci9tY3A/dG9vbHNldHM9b25ib2FyZGluZyIsInR5cGUiOiJvYXV0aCJ9', diff --git a/content/en/bits_ai/mcp_server/_index.md b/content/en/bits_ai/mcp_server/_index.md index 4c7e070ebf1..549ee39d276 100644 --- a/content/en/bits_ai/mcp_server/_index.md +++ b/content/en/bits_ai/mcp_server/_index.md @@ -39,16 +39,14 @@ This demo shows the Datadog MCP Server being used in Cursor and Claude Code (unm ## Disclaimers - -- The Datadog MCP Server is not supported for production use during the Preview. -- Only Datadog organizations that have been specifically allowlisted can use the Datadog MCP Server. It is not available to the general public. - The Datadog MCP Server is HIPAA-eligible. You are responsible for ensuring that the AI tools you connect to the Datadog MCP Server meet your compliance requirements, such as HIPAA. +- The Datadog MCP Server is not GovCloud compatible. - Datadog collects certain information about your usage of the Remote Datadog MCP Server, including how you interact with it, whether errors occurred while using it, what caused those errors, and user identifiers in accordance with the Datadog Privacy Policy and Datadog's EULA. This data is used to help improve the server's performance and features, including transitions to and from the server and the applicable Datadog login page for accessing the Services, and context (for example, user prompts) leading to the use of MCP tools. The data is stored for 120 days. ## Requirements -Datadog users must have the `Incidents Read` [permission][18] to use the MCP Server. +Datadog users must have the `MCP Read`[permission][18] to use the MCP Server for read-access and `MCP Write`[permission][18] for write access. For setup instructions, see [Set Up the Datadog MCP Server](/bits_ai/mcp_server/setup). @@ -65,9 +63,9 @@ The Datadog MCP Server supports _toolsets_, which allow you to use only the tool To use a toolset, include the `toolsets` query parameter in the endpoint URL when connecting to the MCP Server ([remote authentication](/bits_ai/mcp_server/setup?tab=remote-authentication#connect-in-supported-ai-clients) only). For example: -- `https://mcp.datadoghq.com/api/unstable/mcp-server/mcp` retrieves only the core tools (this is the default if `toolsets` is not specified). -- `https://mcp.datadoghq.com/api/unstable/mcp-server/mcp?toolsets=synthetics` retrieves only Synthetic Testing-related tools. -- `https://mcp.datadoghq.com/api/unstable/mcp-server/mcp?toolsets=core,synthetics,software-delivery` retrieves core, Synthetic Testing, and Software Delivery tools. +- `https://mcp.{{< region-param key="dd_site" code="true" >}}/api/unstable/mcp-server/mcp` retrieves only the core tools (this is the default if `toolsets` is not specified). +- `https://mcp.{{< region-param key="dd_site" code="true" >}}/api/unstable/mcp-server/mcp?toolsets=synthetics` retrieves only Synthetic Testing-related tools. +- `https://mcp.{{< region-param key="dd_site" code="true" >}}/api/unstable/mcp-server/mcp?toolsets=core,synthetics,software-delivery` retrieves core, Synthetic Testing, and Software Delivery tools. ## Available tools @@ -345,7 +343,7 @@ The Datadog MCP Server is under significant development. During the Preview, use [1]: https://modelcontextprotocol.io/ [15]: /api/latest/events/ [16]: /account_management/audit_trail/ -[18]: /account_management/rbac/permissions/#case-and-incident-management +[18]: /account_management/rbac/permissions/#mcp [19]: https://docs.google.com/forms/d/e/1FAIpQLSeorvIrML3F4v74Zm5IIaQ_DyCMGqquIp7hXcycnCafx4htcg/viewform [20]: /synthetics/ [21]: /continuous_integration/ diff --git a/content/en/bits_ai/mcp_server/setup.md b/content/en/bits_ai/mcp_server/setup.md index 69a10080699..8d1606e27d8 100644 --- a/content/en/bits_ai/mcp_server/setup.md +++ b/content/en/bits_ai/mcp_server/setup.md @@ -13,21 +13,17 @@ further_reading: text: "Datadog Extension for Cursor" --- -{{< callout url="https://www.datadoghq.com/product-preview/datadog-mcp-server/" >}} -The Datadog MCP Server is in Preview. There is no charge for using the Datadog MCP Server during the Preview, but pricing may change when the feature becomes generally available. If you're interested in the MCP server and need access, complete this form. -{{< /callout >}} - -This page explains how to set up and configure the Datadog MCP Server, which lets you query and retrieve observability insights directly from AI-powered clients such as Cursor, OpenAI Codex, Claude Code, or your own AI agent. +This page explains how to set up and configure the Datadog MCP Server, which lets you retrieve telemetry insights and manage and use platform features directly from AI-powered clients such as Cursor, OpenAI Codex, Claude Code, or your own AI agent. ## Client compatibility -The following AI clients are known to be compatible with the Datadog MCP Server. +The following AI clients are compatible with the Datadog MCP Server.
The Datadog MCP Server is under significant development, and additional supported clients may become available.
| Client | Developer | Notes | |--------|------|------| -| [Cursor][8] | Anysphere | Datadog [Cursor & VS Code extension](#connect-in-cursor-and-vs-code) recommended. | +| [Cursor][8] | Cursor | Datadog [Cursor & VS Code extension](#connect-in-cursor-and-vs-code) recommended. | | [Claude Code][5] | Anthropic | | | [Claude Desktop][6] | Anthropic | Limited support for remote authentication. Use [local binary authentication](?tab=localbinaryauthentication#connect-in-supported-ai-clients) as needed. | | [Codex CLI][7] | OpenAI | | @@ -37,6 +33,14 @@ The following AI clients are known to be compatible with the Datadog MCP Server. | [Kiro CLI][10] | Amazon | | | [Cline][17] | Cline Bot | Limited support for remote authentication. Use [local binary authentication](?tab=localbinaryauthentication#connect-in-supported-ai-clients) as needed. | +## Connect in Claude Code + + For Claude Code, run (use the endpoint shown above for your site): + ```bash + claude mcp add --transport http datadog-mcp {{< region-param key="https://mcp.{{< region-param key="dd_site" code="true" >}}/api/unstable/mcp-server/mcp" code="true" >}} + ``` + + ## Connect in Cursor and VS Code Datadog's [Cursor and VS Code extension][12] includes built-in access to the managed Datadog MCP Server. Benefits include: @@ -67,27 +71,15 @@ The following instructions are for all [MCP-compatible clients][21]. For Cursor {{% tab "Remote authentication" %}} This method uses the MCP specification's [Streamable HTTP][1] transport mechanism to connect to the MCP Server. -Point your AI agent to the MCP Server endpoint for your regional [Datadog site][2]. For example, if you're using `app.datadoghq.com` to access Datadog, use the endpoint for the US1 site. +Point your AI agent to the MCP Server endpoint for your regional [Datadog site][2]. The endpoint updates automatically based on the site selected in the region selector at the top of the documentation. -If your organization uses a [custom sub-domain][3], use the endpoint that corresponds to your regional Datadog site. For example, if your custom sub-domain is `myorg.datadoghq.com`, use the US1 endpoint. +If your organization uses a [custom sub-domain][3], use the endpoint that corresponds to your regional Datadog site. -| Datadog Site | MCP Server Endpoint | -|--------|------| -| **US1** (`app.datadoghq.com`) | `https://mcp.datadoghq.com/api/unstable/mcp-server/mcp` | -| **US3** (`us3.datadoghq.com`) | `https://mcp.us3.datadoghq.com/api/unstable/mcp-server/mcp` | -| **US5** (`us5.datadoghq.com`) | `https://mcp.us5.datadoghq.com/api/unstable/mcp-server/mcp` | -| **EU1** (`app.datadoghq.eu`) | `https://mcp.datadoghq.eu/api/unstable/mcp-server/mcp` | -| **AP1** (`ap1.datadoghq.com`) | `https://mcp.ap1.datadoghq.com/api/unstable/mcp-server/mcp` | -| **AP2** (`ap2.datadoghq.com`) | `https://mcp.ap2.datadoghq.com/api/unstable/mcp-server/mcp` | +**MCP Server endpoint:** -### Example configurations - -These examples are for the US1 site: +`https://mcp.{{< region-param key="dd_site" code="true" >}}/api/unstable/mcp-server/mcp` -* **Command line**: For Claude Code, run: - ```bash - claude mcp add --transport http datadog-mcp https://mcp.datadoghq.com/api/unstable/mcp-server/mcp - ``` +### Example configurations * **Configuration file**: Edit the configuration file for your AI agent: * Codex CLI: `~/.codex/config.toml` @@ -99,7 +91,7 @@ These examples are for the US1 site: "mcpServers": { "datadog": { "type": "http", - "url": "https://mcp.datadoghq.com/api/unstable/mcp-server/mcp" + "url": "{{< region-param key="https://mcp.{{< region-param key="dd_site" code="true" >}}/api/unstable/mcp-server/mcp" code="true" >}}" } } } @@ -167,7 +159,7 @@ The MCP Server uses OAuth 2.0 for [authentication][2]. If you cannot go through "mcpServers": { "datadog": { "type": "http", - "url": "https://mcp.datadoghq.com/api/unstable/mcp-server/mcp", + "url": "{{< region-param key="mcp_server_endpoint" code="true" >}}", "headers": { "DD_API_KEY": "", "DD_APPLICATION_KEY": "" From 931ad5e7a8fa4e6ba1e7fa64f05de8c3d17abe07 Mon Sep 17 00:00:00 2001 From: Sumedha Mehta Date: Thu, 19 Feb 2026 17:18:02 -0500 Subject: [PATCH 2/5] Restructure MCP setup with client-based tab switcher - Add tabs: Cursor, Claude Code, Claude Desktop, Codex, VS Code, Other - Organize instructions per client using existing doc content - Other tab: Goose, Kiro, Kiro CLI, Cline with remote + local binary options - Fix invalid region-param keys; keep shared Authentication and Test access sections Co-authored-by: Cursor --- content/en/bits_ai/mcp_server/setup.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/en/bits_ai/mcp_server/setup.md b/content/en/bits_ai/mcp_server/setup.md index 8d1606e27d8..18aa1d8e018 100644 --- a/content/en/bits_ai/mcp_server/setup.md +++ b/content/en/bits_ai/mcp_server/setup.md @@ -91,7 +91,7 @@ If your organization uses a [custom sub-domain][3], use the endpoint that corres "mcpServers": { "datadog": { "type": "http", - "url": "{{< region-param key="https://mcp.{{< region-param key="dd_site" code="true" >}}/api/unstable/mcp-server/mcp" code="true" >}}" + "url": "https://mcp.datadoghq.com/api/unstable/mcp-server/mcp" } } } @@ -159,7 +159,7 @@ The MCP Server uses OAuth 2.0 for [authentication][2]. If you cannot go through "mcpServers": { "datadog": { "type": "http", - "url": "{{< region-param key="mcp_server_endpoint" code="true" >}}", + "url": "https://mcp.datadoghq.com/api/unstable/mcp-server/mcp", "headers": { "DD_API_KEY": "", "DD_APPLICATION_KEY": "" From 7b31d53b95e4aacf6a760ec094f59fe3ff34ee7a Mon Sep 17 00:00:00 2001 From: Sumedha Mehta Date: Thu, 19 Feb 2026 18:08:39 -0500 Subject: [PATCH 3/5] Revert dynamic region URLs; use static MCP URLs for now - Remove mcp_server_endpoint from regions.config.js - Restore static endpoint table and URLs in setup.md - Restore static toolset URLs in _index.md Dynamic region URLs will be reintroduced in a separate PR. Co-authored-by: Cursor --- assets/scripts/config/regions.config.js | 9 --------- content/en/bits_ai/mcp_server/_index.md | 6 +++--- content/en/bits_ai/mcp_server/setup.md | 15 ++++++++++----- 3 files changed, 13 insertions(+), 17 deletions(-) diff --git a/assets/scripts/config/regions.config.js b/assets/scripts/config/regions.config.js index 602d9e899a1..633db1d3a09 100644 --- a/assets/scripts/config/regions.config.js +++ b/assets/scripts/config/regions.config.js @@ -652,15 +652,6 @@ export default { ap2: 'intake.synthetics.ap2.datadoghq.com', gov: 'intake.synthetics.ddog-gov.com' }, - mcp_server_endpoint: { - us: 'https://mcp.datadoghq.com/api/unstable/mcp-server/mcp', - us3: 'https://mcp.us3.datadoghq.com/api/unstable/mcp-server/mcp', - us5: 'https://mcp.us5.datadoghq.com/api/unstable/mcp-server/mcp', - eu: 'https://mcp.datadoghq.eu/api/unstable/mcp-server/mcp', - ap1: 'https://mcp.ap1.datadoghq.com/api/unstable/mcp-server/mcp', - ap2: 'https://mcp.ap2.datadoghq.com/api/unstable/mcp-server/mcp', - gov: 'N/A' - }, cursor_mcp_install_deeplink: { us: 'cursor://anysphere.cursor-deeplink/mcp/install?name=datadog-onboarding-us1&config=eyJ1cmwiOiJodHRwczovL21jcC5kYXRhZG9naHEuY29tL2FwaS91bnN0YWJsZS9tY3Atc2VydmVyL21jcD90b29sc2V0cz1vbmJvYXJkaW5nIiwidHlwZSI6Im9hdXRoIn0=', us3: 'cursor://anysphere.cursor-deeplink/mcp/install?name=datadog-onboarding-us3&config=eyJ1cmwiOiJodHRwczovL21jcC51czMuZGF0YWRvZ2hxLmNvbS9hcGkvdW5zdGFibGUvbWNwLXNlcnZlci9tY3A/dG9vbHNldHM9b25ib2FyZGluZyIsInR5cGUiOiJvYXV0aCJ9', diff --git a/content/en/bits_ai/mcp_server/_index.md b/content/en/bits_ai/mcp_server/_index.md index 549ee39d276..08e8ea36d1d 100644 --- a/content/en/bits_ai/mcp_server/_index.md +++ b/content/en/bits_ai/mcp_server/_index.md @@ -63,9 +63,9 @@ The Datadog MCP Server supports _toolsets_, which allow you to use only the tool To use a toolset, include the `toolsets` query parameter in the endpoint URL when connecting to the MCP Server ([remote authentication](/bits_ai/mcp_server/setup?tab=remote-authentication#connect-in-supported-ai-clients) only). For example: -- `https://mcp.{{< region-param key="dd_site" code="true" >}}/api/unstable/mcp-server/mcp` retrieves only the core tools (this is the default if `toolsets` is not specified). -- `https://mcp.{{< region-param key="dd_site" code="true" >}}/api/unstable/mcp-server/mcp?toolsets=synthetics` retrieves only Synthetic Testing-related tools. -- `https://mcp.{{< region-param key="dd_site" code="true" >}}/api/unstable/mcp-server/mcp?toolsets=core,synthetics,software-delivery` retrieves core, Synthetic Testing, and Software Delivery tools. +- `https://mcp.datadoghq.com/api/unstable/mcp-server/mcp` retrieves only the core tools (this is the default if `toolsets` is not specified). +- `https://mcp.datadoghq.com/api/unstable/mcp-server/mcp?toolsets=synthetics` retrieves only Synthetic Testing-related tools. +- `https://mcp.datadoghq.com/api/unstable/mcp-server/mcp?toolsets=core,synthetics,software-delivery` retrieves core, Synthetic Testing, and Software Delivery tools. ## Available tools diff --git a/content/en/bits_ai/mcp_server/setup.md b/content/en/bits_ai/mcp_server/setup.md index 18aa1d8e018..5ea83a92d19 100644 --- a/content/en/bits_ai/mcp_server/setup.md +++ b/content/en/bits_ai/mcp_server/setup.md @@ -37,7 +37,7 @@ The following AI clients are compatible with the Datadog MCP Server. For Claude Code, run (use the endpoint shown above for your site): ```bash - claude mcp add --transport http datadog-mcp {{< region-param key="https://mcp.{{< region-param key="dd_site" code="true" >}}/api/unstable/mcp-server/mcp" code="true" >}} + claude mcp add --transport http datadog-mcp https://mcp.datadoghq.com/api/unstable/mcp-server/mcp ``` @@ -71,13 +71,18 @@ The following instructions are for all [MCP-compatible clients][21]. For Cursor {{% tab "Remote authentication" %}} This method uses the MCP specification's [Streamable HTTP][1] transport mechanism to connect to the MCP Server. -Point your AI agent to the MCP Server endpoint for your regional [Datadog site][2]. The endpoint updates automatically based on the site selected in the region selector at the top of the documentation. +Point your AI agent to the MCP Server endpoint for your regional [Datadog site][2]. For example, if you're using `app.datadoghq.com` to access Datadog, use the endpoint for the US1 site. If your organization uses a [custom sub-domain][3], use the endpoint that corresponds to your regional Datadog site. -**MCP Server endpoint:** - -`https://mcp.{{< region-param key="dd_site" code="true" >}}/api/unstable/mcp-server/mcp` +| Datadog Site | MCP Server Endpoint | +|--------|------| +| **US1** (`app.datadoghq.com`) | `https://mcp.datadoghq.com/api/unstable/mcp-server/mcp` | +| **US3** (`us3.datadoghq.com`) | `https://mcp.us3.datadoghq.com/api/unstable/mcp-server/mcp` | +| **US5** (`us5.datadoghq.com`) | `https://mcp.us5.datadoghq.com/api/unstable/mcp-server/mcp` | +| **EU1** (`app.datadoghq.eu`) | `https://mcp.datadoghq.eu/api/unstable/mcp-server/mcp` | +| **AP1** (`ap1.datadoghq.com`) | `https://mcp.ap1.datadoghq.com/api/unstable/mcp-server/mcp` | +| **AP2** (`ap2.datadoghq.com`) | `https://mcp.ap2.datadoghq.com/api/unstable/mcp-server/mcp` | ### Example configurations From ead369cde86070cc98ffef101419a7f0ba210a3d Mon Sep 17 00:00:00 2001 From: Sumedha Mehta Date: Thu, 19 Feb 2026 19:29:09 -0500 Subject: [PATCH 4/5] Add client tab switcher to MCP setup; reorganize by client - Move client tab switcher to top of setup page (Cursor, Claude Code, Claude Desktop, Codex, VS Code, Other) - Reformat instructions per client using existing content - Consolidate Other tab for Goose, Kiro, Kiro CLI, Cline with remote and local binary auth - Add Supported clients reference table below tabs Co-authored-by: Cursor --- content/en/bits_ai/mcp_server/_index.md | 4 - content/en/bits_ai/mcp_server/setup.md | 278 ++++++++++++++++-------- 2 files changed, 185 insertions(+), 97 deletions(-) diff --git a/content/en/bits_ai/mcp_server/_index.md b/content/en/bits_ai/mcp_server/_index.md index 08e8ea36d1d..4749f2eda58 100644 --- a/content/en/bits_ai/mcp_server/_index.md +++ b/content/en/bits_ai/mcp_server/_index.md @@ -25,10 +25,6 @@ algolia: rank: 90 --- -{{< callout url="https://www.datadoghq.com/product-preview/datadog-mcp-server/" >}} -The Datadog MCP Server is in Preview. There is no charge for using the Datadog MCP Server during the Preview, but pricing may change when the feature becomes generally available. If you're interested in the MCP server and need access, complete this form. -{{< /callout >}} - The Datadog MCP Server acts as a bridge between your observability data in Datadog and any AI agents that support the [Model Context Protocol (MCP)][1]. Providing structured access to relevant Datadog contexts, features, and tools, the MCP Server lets you query and retrieve observability insights directly from AI-powered clients such as Cursor, OpenAI Codex, Claude Code, or your own AI agent. Ready to get started? See [Set Up the Datadog MCP Server][27] for connection instructions. diff --git a/content/en/bits_ai/mcp_server/setup.md b/content/en/bits_ai/mcp_server/setup.md index 5ea83a92d19..66c80841ec3 100644 --- a/content/en/bits_ai/mcp_server/setup.md +++ b/content/en/bits_ai/mcp_server/setup.md @@ -13,67 +13,37 @@ further_reading: text: "Datadog Extension for Cursor" --- -This page explains how to set up and configure the Datadog MCP Server, which lets you retrieve telemetry insights and manage and use platform features directly from AI-powered clients such as Cursor, OpenAI Codex, Claude Code, or your own AI agent. +This page explains how to set up and configure the Datadog MCP Server, which lets you retrieve telemetry insights and manage and use platform features directly from AI-powered clients. -## Client compatibility +Select your client to see setup instructions: -The following AI clients are compatible with the Datadog MCP Server. - -
The Datadog MCP Server is under significant development, and additional supported clients may become available.
- -| Client | Developer | Notes | -|--------|------|------| -| [Cursor][8] | Cursor | Datadog [Cursor & VS Code extension](#connect-in-cursor-and-vs-code) recommended. | -| [Claude Code][5] | Anthropic | | -| [Claude Desktop][6] | Anthropic | Limited support for remote authentication. Use [local binary authentication](?tab=localbinaryauthentication#connect-in-supported-ai-clients) as needed. | -| [Codex CLI][7] | OpenAI | | -| [VS Code][11] | Microsoft | Datadog [Cursor & VS Code extension](#connect-in-cursor-and-vs-code) recommended. | -| [Goose][9] | Block | | -| [Kiro][22] | Amazon | | -| [Kiro CLI][10] | Amazon | | -| [Cline][17] | Cline Bot | Limited support for remote authentication. Use [local binary authentication](?tab=localbinaryauthentication#connect-in-supported-ai-clients) as needed. | - -## Connect in Claude Code - - For Claude Code, run (use the endpoint shown above for your site): - ```bash - claude mcp add --transport http datadog-mcp https://mcp.datadoghq.com/api/unstable/mcp-server/mcp - ``` - - -## Connect in Cursor and VS Code +{{< tabs >}} +{{% tab "Cursor" %}} Datadog's [Cursor and VS Code extension][12] 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. -* [Cursor only] 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. +* 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: -1. If you previously installed the Datadog MCP Server manually, remove it from the IDE's configuration to avoid conflicts. To find the MCP Server configuration: - - Cursor: Go to **Cursor Settings** (`Shift` + `Cmd/Ctrl` + `J`) and select the **MCP** tab. - - VS Code: Open the command palette (`Shift` + `Cmd/Ctrl` + `P`) and run `MCP: Open User Configuration`. +1. 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. 2. Install the Datadog extension following [these instructions][14]. If you have the extension installed already, make sure it's the latest version, as new features are released regularly. 3. Sign in to your Datadog account. If you have multiple accounts, use the account included in your Product Preview. - {{< img src="bits_ai/mcp_server/ide_sign_in.png" alt="Sign in to Datadog from the IDE extension" style="width:70%;" >}} + {{< img src="bits_ai/mcp_server/ide_sign_in.png" alt="Sign in to Datadog from the IDE extension" style="width:70%;" >}} 4. **Restart the IDE.** -5. Confirm the Datadog MCP Server is available and the [tools][20] are listed in your IDE: - - Cursor: Go to **Cursor Settings** (`Shift` + `Cmd/Ctrl` + `J`), and select the **MCP** tab. - - VS Code: Open the chat panel, select agent mode, and click the **Configure Tools** button. - {{< img src="bits_ai/mcp_server/vscode_configure_tools_button.png" alt="Configure Tools button in VS Code" style="width:70%;" >}} +5. Confirm the Datadog MCP Server is available and the [tools][20] are listed: Go to **Cursor Settings** (`Shift` + `Cmd/Ctrl` + `J`), and select the **MCP** tab. -## Connect in other AI clients +{{% /tab %}} -The following instructions are for all [MCP-compatible clients][21]. For Cursor or VS Code, use the [Datadog extension](#connect-in-cursor-and-vs-code) for built-in access to the Datadog MCP Server. +{{% tab "Claude Code" %}} -{{< tabs >}} -{{% tab "Remote authentication" %}} -This method uses the MCP specification's [Streamable HTTP][1] transport mechanism to connect to the MCP Server. +You can connect Claude Code to the Datadog MCP Server using remote authentication (HTTP) or local binary authentication (stdio). -Point your AI agent to the MCP Server endpoint for your regional [Datadog site][2]. For example, if you're using `app.datadoghq.com` to access Datadog, use the endpoint for the US1 site. +**Remote authentication** -If your organization uses a [custom sub-domain][3], use the endpoint that corresponds to your regional Datadog site. +Point your AI agent to the MCP Server endpoint for your regional [Datadog site][site]. For example, if you're using `app.datadoghq.com`, use the US1 endpoint. | Datadog Site | MCP Server Endpoint | |--------|------| @@ -84,13 +54,12 @@ If your organization uses a [custom sub-domain][3], use the endpoint that corres | **AP1** (`ap1.datadoghq.com`) | `https://mcp.ap1.datadoghq.com/api/unstable/mcp-server/mcp` | | **AP2** (`ap2.datadoghq.com`) | `https://mcp.ap2.datadoghq.com/api/unstable/mcp-server/mcp` | -### Example configurations - -* **Configuration file**: Edit the configuration file for your AI agent: - * Codex CLI: `~/.codex/config.toml` - * Gemini CLI: `~/.gemini/settings.json` - * Kiro CLI: `~/.kiro/settings/mcp.json` +* **Command line**: Run (use the endpoint for your site from the table above): + ```bash + claude mcp add --transport http datadog-mcp https://mcp.datadoghq.com/api/unstable/mcp-server/mcp + ``` +* **Configuration file**: Add to `~/.claude.json`: ```json { "mcpServers": { @@ -102,62 +71,184 @@ If your organization uses a [custom sub-domain][3], use the endpoint that corres } ``` -[1]: https://modelcontextprotocol.io/specification/2025-03-26/basic/transports#streamable-http -[2]: /getting_started/site/ -[3]: /account_management/multi_organization/#custom-sub-domains +**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. + +1. Install the Datadog MCP Server binary (macOS and Linux): + ```bash + curl -sSL https://coterm.datadoghq.com/mcp-cli/install.sh | bash + ``` + This installs the binary to `~/.local/bin/datadog_mcp_cli`. + +2. Run `datadog_mcp_cli login` manually to walk through the OAuth login flow and choose a [Datadog site][site]. + +3. Configure Claude Code. Add to `~/.claude.json` (replace `` with your username): + ```json + { + "mcpServers": { + "datadog": { + "type": "stdio", + "command": "/Users//.local/bin/datadog_mcp_cli", + "args": [], + "env": {} + } + } + } + ``` + Or run: `claude mcp add datadog --scope user -- ~/.local/bin/datadog_mcp_cli` + {{% /tab %}} -{{% tab "Local binary authentication" %}} +{{% tab "Claude Desktop" %}} + +Claude Desktop has limited support for remote authentication. Use **local binary authentication** for reliable setup. + +1. Install the Datadog MCP Server binary (macOS and Linux): + ```bash + curl -sSL https://coterm.datadoghq.com/mcp-cli/install.sh | bash + ``` + This installs the binary to `~/.local/bin/datadog_mcp_cli`. + Windows: Download the [Windows version][win]. + +2. Run `datadog_mcp_cli login` manually to walk through the OAuth login flow and choose a [Datadog site][site]. + +3. 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`: + ```json + { + "mcpServers": { + "datadog": { + "type": "stdio", + "command": "/Users//.local/bin/datadog_mcp_cli", + "args": [], + "env": {} + } + } + } + ``` -This method uses the MCP specification's [stdio][1] transport mechanism to connect to the MCP Server. +{{% /tab %}} -Use this option if direct remote authentication is not available for you. After installation, you typically do not need to update the local binary to benefit from MCP Server updates, as the tools are remote. +{{% tab "Codex" %}} -1. Install the Datadog MCP Server binary: - * macOS and Linux: - ```bash - curl -sSL https://coterm.datadoghq.com/mcp-cli/install.sh | bash - ``` +Point your AI agent to the MCP Server endpoint for your regional [Datadog site][site]. For example, for US1 use `https://mcp.datadoghq.com/api/unstable/mcp-server/mcp`. See the endpoint table in the [Claude Code](#claude-code) tab for all sites. - This installs the MCP Server binary to `~/.local/bin/datadog_mcp_cli` and then you can use it like any other stdio MCP server.

+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. - * Windows: Download the [Windows version][2]. +Example JSON-style configuration (US1): -2. Run `datadog_mcp_cli login` manually to walk through the OAuth login flow. +```json +{ + "mcpServers": { + "datadog": { + "type": "http", + "url": "https://mcp.datadoghq.com/api/unstable/mcp-server/mcp" + } + } +} +``` - The MCP Server automatically starts the OAuth flow if a client needs it, but doing it manually lets you choose a [Datadog site][3] and avoid the AI client timing out. +{{% /tab %}} -3. Configure your AI client to use the Datadog MCP Server. Follow your client's configuration instructions, as MCP Server setup varies between third-party AI clients. +{{% tab "VS Code" %}} - For example, for Claude Code, add this to `~/.claude.json`, making sure to replace `` in the command path: +Datadog's [Cursor and VS Code extension][12] includes built-in access to the managed Datadog MCP Server. Benefits include: - ```json - { - "mcpServers": { - "datadog": { - "type": "stdio", - "command": "/Users//.local/bin/datadog_mcp_cli", - "args": [], - "env": {} - } - } - } - ``` +* No additional MCP Server setup after you install the extension and connect to Datadog. +* One-click transitions between multiple Datadog organizations. - Alternatively, you can also configure Claude Code by running the following: - ```bash - claude mcp add datadog --scope user -- ~/.local/bin/datadog_mcp_cli - ``` +To install the extension: + +1. 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`. +2. Install the Datadog extension following [these instructions][14]. If you have the extension installed already, make sure it's the latest version. +3. Sign in to your Datadog account. If you have multiple accounts, use the account included in your Product Preview. +4. **Restart the IDE.** +5. Confirm the Datadog MCP Server is available and the [tools][20] are listed: Open the chat panel, select agent mode, and click the **Configure Tools** button. + {{< img src="bits_ai/mcp_server/vscode_configure_tools_button.png" alt="Configure Tools button in VS Code" style="width:70%;" >}} + +{{% /tab %}} + +{{% tab "Other" %}} + +The following clients can connect to the Datadog MCP Server: [Goose][9], [Kiro][22], [Kiro CLI][10], [Cline][17], and other MCP-compatible clients. Use **remote authentication** when your client supports it. For Cline (and when remote auth is unreliable), use **local binary authentication**. + +**Remote authentication** + +Point your AI agent to the MCP Server endpoint for your regional [Datadog site][site]: + +| Datadog Site | MCP Server Endpoint | +|--------|------| +| **US1** (`app.datadoghq.com`) | `https://mcp.datadoghq.com/api/unstable/mcp-server/mcp` | +| **US3** (`us3.datadoghq.com`) | `https://mcp.us3.datadoghq.com/api/unstable/mcp-server/mcp` | +| **US5** (`us5.datadoghq.com`) | `https://mcp.us5.datadoghq.com/api/unstable/mcp-server/mcp` | +| **EU1** (`app.datadoghq.eu`) | `https://mcp.datadoghq.eu/api/unstable/mcp-server/mcp` | +| **AP1** (`ap1.datadoghq.com`) | `https://mcp.ap1.datadoghq.com/api/unstable/mcp-server/mcp` | +| **AP2** (`ap2.datadoghq.com`) | `https://mcp.ap2.datadoghq.com/api/unstable/mcp-server/mcp` | + +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 (US1): + +```json +{ + "mcpServers": { + "datadog": { + "type": "http", + "url": "https://mcp.datadoghq.com/api/unstable/mcp-server/mcp" + } + } +} +``` + +**Local binary authentication** (recommended for Cline and when remote auth is unreliable) + +1. Install the Datadog MCP Server binary (macOS and Linux): + ```bash + curl -sSL https://coterm.datadoghq.com/mcp-cli/install.sh | bash + ``` + This installs the binary to `~/.local/bin/datadog_mcp_cli`. + Windows: Download the [Windows version][win-other]. + +2. Run `datadog_mcp_cli login` manually to walk through the OAuth login flow and choose a [Datadog site][site]. + +3. Configure your AI client to use the stdio transport with `datadog_mcp_cli` as the command. Example: + ```json + { + "mcpServers": { + "datadog": { + "type": "stdio", + "command": "/Users//.local/bin/datadog_mcp_cli", + "args": [], + "env": {} + } + } + } + ``` -[1]: https://modelcontextprotocol.io/specification/2025-03-26/basic/transports#stdio -[2]: https://coterm.datadoghq.com/mcp-cli/datadog_mcp_cli.exe -[3]: /getting_started/site/ {{% /tab %}} {{< /tabs >}} +### Supported clients + +| Client | Developer | Notes | +|--------|------|------| +| [Cursor][8] | Cursor | Datadog [Cursor & VS Code extension](#cursor) recommended. | +| [Claude Code][5] | Anthropic | | +| [Claude Desktop][6] | Anthropic | Limited support for remote authentication. Use [local binary authentication](#claude-desktop) as needed. | +| [Codex CLI][7] | OpenAI | | +| [VS Code][11] | Microsoft | Datadog [Cursor & VS Code extension](#vs-code) recommended. | +| [Goose][9], [Kiro][22], [Kiro CLI][10], [Cline][17] | Various | See the **Other** tab above. Use local binary authentication for Cline if remote auth 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][2]. If you cannot go through the OAuth flow (for example, on a server), you can provide a Datadog [API key and application key][3] as `DD_API_KEY` and `DD_APPLICATION_KEY` HTTP headers. For example: +The MCP Server uses OAuth 2.0 for [authentication][auth]. If you cannot go through the OAuth flow (for example, on a server), you can provide a Datadog [API key and application key][3] as `DD_API_KEY` and `DD_APPLICATION_KEY` HTTP headers. For example: {{< code-block lang="json" >}} { @@ -179,21 +270,22 @@ For security, use a scoped API key and application key from a [service account][ ### Test access to the MCP Server 1. Install the [MCP inspector][4], a developer tool for testing and debugging MCP servers. - - ```bash - npx @modelcontextprotocol/inspector - ``` + ```bash + npx @modelcontextprotocol/inspector + ``` 2. In the inspector's web UI, for **Transport Type**, select **Streamable HTTP**. -3. For **URL**, enter the [MCP Server URL](?tab=remoteauthentication#connect-in-supported-ai-clients) for your regional Datadog site. +3. For **URL**, enter the MCP Server endpoint for your regional Datadog site (for example, for US1: `https://mcp.datadoghq.com/api/unstable/mcp-server/mcp`). See the endpoint table in the tabs above for other sites. 4. Click **Connect**, then go to **Tools** > **List Tools**. 5. Check if the [available tools][20] appear. - ## Further reading {{< partial name="whats-next/whats-next.html" >}} -[2]: https://modelcontextprotocol.io/specification/draft/basic/authorization +[site]: /getting_started/site/ +[auth]: https://modelcontextprotocol.io/specification/draft/basic/authorization +[win]: https://coterm.datadoghq.com/mcp-cli/datadog_mcp_cli.exe +[win-other]: https://coterm.datadoghq.com/mcp-cli/datadog_mcp_cli.exe [3]: /account_management/api-app-keys/ [4]: https://github.com/modelcontextprotocol/inspector [5]: https://www.anthropic.com/claude-code From 523fabf624007991a04189b6010f25ed15d1b251 Mon Sep 17 00:00:00 2001 From: Sumedha Mehta Date: Thu, 19 Feb 2026 19:41:21 -0500 Subject: [PATCH 5/5] Make MCP Server docs use dynamic region URLs - Add mcp_server_endpoint to regions.config.js for all supported sites - Replace hardcoded MCP URLs in setup.md with region-param shortcodes (all client tabs + auth + test) - Replace hardcoded MCP URLs in _index.md Toolsets section - Endpoint and examples update based on docs site selector (US1, US3, EU1, etc.) Co-authored-by: Cursor --- assets/scripts/config/regions.config.js | 9 +++++ content/en/bits_ai/mcp_server/_index.md | 8 ++--- content/en/bits_ai/mcp_server/setup.md | 46 ++++++++----------------- 3 files changed, 28 insertions(+), 35 deletions(-) diff --git a/assets/scripts/config/regions.config.js b/assets/scripts/config/regions.config.js index 633db1d3a09..602d9e899a1 100644 --- a/assets/scripts/config/regions.config.js +++ b/assets/scripts/config/regions.config.js @@ -652,6 +652,15 @@ export default { ap2: 'intake.synthetics.ap2.datadoghq.com', gov: 'intake.synthetics.ddog-gov.com' }, + mcp_server_endpoint: { + us: 'https://mcp.datadoghq.com/api/unstable/mcp-server/mcp', + us3: 'https://mcp.us3.datadoghq.com/api/unstable/mcp-server/mcp', + us5: 'https://mcp.us5.datadoghq.com/api/unstable/mcp-server/mcp', + eu: 'https://mcp.datadoghq.eu/api/unstable/mcp-server/mcp', + ap1: 'https://mcp.ap1.datadoghq.com/api/unstable/mcp-server/mcp', + ap2: 'https://mcp.ap2.datadoghq.com/api/unstable/mcp-server/mcp', + gov: 'N/A' + }, cursor_mcp_install_deeplink: { us: 'cursor://anysphere.cursor-deeplink/mcp/install?name=datadog-onboarding-us1&config=eyJ1cmwiOiJodHRwczovL21jcC5kYXRhZG9naHEuY29tL2FwaS91bnN0YWJsZS9tY3Atc2VydmVyL21jcD90b29sc2V0cz1vbmJvYXJkaW5nIiwidHlwZSI6Im9hdXRoIn0=', us3: 'cursor://anysphere.cursor-deeplink/mcp/install?name=datadog-onboarding-us3&config=eyJ1cmwiOiJodHRwczovL21jcC51czMuZGF0YWRvZ2hxLmNvbS9hcGkvdW5zdGFibGUvbWNwLXNlcnZlci9tY3A/dG9vbHNldHM9b25ib2FyZGluZyIsInR5cGUiOiJvYXV0aCJ9', diff --git a/content/en/bits_ai/mcp_server/_index.md b/content/en/bits_ai/mcp_server/_index.md index 4749f2eda58..5c057f0c799 100644 --- a/content/en/bits_ai/mcp_server/_index.md +++ b/content/en/bits_ai/mcp_server/_index.md @@ -57,11 +57,11 @@ The Datadog MCP Server supports _toolsets_, which allow you to use only the tool - `error-tracking`: Tools for interacting with Datadog [Error Tracking][25] - `dbm`: Tools for interacting with [Database Monitoring][26] -To use a toolset, include the `toolsets` query parameter in the endpoint URL when connecting to the MCP Server ([remote authentication](/bits_ai/mcp_server/setup?tab=remote-authentication#connect-in-supported-ai-clients) only). For example: +To use a toolset, include the `toolsets` query parameter in the endpoint URL when connecting to the MCP Server ([remote authentication](/bits_ai/mcp_server/setup#supported-clients) only). The endpoint updates automatically based on the site selected in the region selector at the top of the documentation. For example: -- `https://mcp.datadoghq.com/api/unstable/mcp-server/mcp` retrieves only the core tools (this is the default if `toolsets` is not specified). -- `https://mcp.datadoghq.com/api/unstable/mcp-server/mcp?toolsets=synthetics` retrieves only Synthetic Testing-related tools. -- `https://mcp.datadoghq.com/api/unstable/mcp-server/mcp?toolsets=core,synthetics,software-delivery` retrieves core, Synthetic Testing, and Software Delivery tools. +- `https://mcp.{{< region-param key="dd_site" code="true" >}}/api/unstable/mcp-server/mcp` retrieves only the core tools (this is the default if `toolsets` is not specified). +- `https://mcp.{{< region-param key="dd_site" code="true" >}}/api/unstable/mcp-server/mcp?toolsets=synthetics` retrieves only Synthetic Testing-related tools. +- `https://mcp.{{< region-param key="dd_site" code="true" >}}/api/unstable/mcp-server/mcp?toolsets=core,synthetics,software-delivery` retrieves core, Synthetic Testing, and Software Delivery tools. ## Available tools diff --git a/content/en/bits_ai/mcp_server/setup.md b/content/en/bits_ai/mcp_server/setup.md index 66c80841ec3..7677ad2caae 100644 --- a/content/en/bits_ai/mcp_server/setup.md +++ b/content/en/bits_ai/mcp_server/setup.md @@ -43,20 +43,13 @@ You can connect Claude Code to the Datadog MCP Server using remote authenticatio **Remote authentication** -Point your AI agent to the MCP Server endpoint for your regional [Datadog site][site]. For example, if you're using `app.datadoghq.com`, use the US1 endpoint. - -| Datadog Site | MCP Server Endpoint | -|--------|------| -| **US1** (`app.datadoghq.com`) | `https://mcp.datadoghq.com/api/unstable/mcp-server/mcp` | -| **US3** (`us3.datadoghq.com`) | `https://mcp.us3.datadoghq.com/api/unstable/mcp-server/mcp` | -| **US5** (`us5.datadoghq.com`) | `https://mcp.us5.datadoghq.com/api/unstable/mcp-server/mcp` | -| **EU1** (`app.datadoghq.eu`) | `https://mcp.datadoghq.eu/api/unstable/mcp-server/mcp` | -| **AP1** (`ap1.datadoghq.com`) | `https://mcp.ap1.datadoghq.com/api/unstable/mcp-server/mcp` | -| **AP2** (`ap2.datadoghq.com`) | `https://mcp.ap2.datadoghq.com/api/unstable/mcp-server/mcp` | - -* **Command line**: Run (use the endpoint for your site from the table above): +Point your AI agent to the MCP Server endpoint for your regional [Datadog site][site]. The endpoint updates automatically based on the site selected in the region selector at the top of the documentation. + +**MCP Server endpoint:** `{{< region-param key="mcp_server_endpoint" code="true" >}}` + +* **Command line**: Run (use the endpoint for your site from above): ```bash - claude mcp add --transport http datadog-mcp https://mcp.datadoghq.com/api/unstable/mcp-server/mcp + claude mcp add --transport http datadog-mcp {{< region-param key="mcp_server_endpoint" code="true" >}} ``` * **Configuration file**: Add to `~/.claude.json`: @@ -65,7 +58,7 @@ Point your AI agent to the MCP Server endpoint for your regional [Datadog site][ "mcpServers": { "datadog": { "type": "http", - "url": "https://mcp.datadoghq.com/api/unstable/mcp-server/mcp" + "url": "{{< region-param key="mcp_server_endpoint" code="true" >}}" } } } @@ -131,18 +124,18 @@ Claude Desktop has limited support for remote authentication. Use **local binary {{% tab "Codex" %}} -Point your AI agent to the MCP Server endpoint for your regional [Datadog site][site]. For example, for US1 use `https://mcp.datadoghq.com/api/unstable/mcp-server/mcp`. See the endpoint table in the [Claude Code](#claude-code) tab for all sites. +Point your AI agent to the MCP Server endpoint for your regional [Datadog site][site]. The endpoint updates automatically based on the site selected in the region selector at the top of the documentation: `{{< region-param key="mcp_server_endpoint" code="true" >}}` 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 JSON-style configuration (US1): +Example configuration: ```json { "mcpServers": { "datadog": { "type": "http", - "url": "https://mcp.datadoghq.com/api/unstable/mcp-server/mcp" + "url": "{{< region-param key="mcp_server_endpoint" code="true" >}}" } } } @@ -174,16 +167,7 @@ The following clients can connect to the Datadog MCP Server: [Goose][9], [Kiro][ **Remote authentication** -Point your AI agent to the MCP Server endpoint for your regional [Datadog site][site]: - -| Datadog Site | MCP Server Endpoint | -|--------|------| -| **US1** (`app.datadoghq.com`) | `https://mcp.datadoghq.com/api/unstable/mcp-server/mcp` | -| **US3** (`us3.datadoghq.com`) | `https://mcp.us3.datadoghq.com/api/unstable/mcp-server/mcp` | -| **US5** (`us5.datadoghq.com`) | `https://mcp.us5.datadoghq.com/api/unstable/mcp-server/mcp` | -| **EU1** (`app.datadoghq.eu`) | `https://mcp.datadoghq.eu/api/unstable/mcp-server/mcp` | -| **AP1** (`ap1.datadoghq.com`) | `https://mcp.ap1.datadoghq.com/api/unstable/mcp-server/mcp` | -| **AP2** (`ap2.datadoghq.com`) | `https://mcp.ap2.datadoghq.com/api/unstable/mcp-server/mcp` | +Point your AI agent to the MCP Server endpoint for your regional [Datadog site][site]. The endpoint updates automatically based on the site selected in the region selector at the top of the documentation: `{{< region-param key="mcp_server_endpoint" code="true" >}}` Add the Datadog MCP Server to your client's configuration using the HTTP transport and the endpoint above. Example config file locations: @@ -192,14 +176,14 @@ Add the Datadog MCP Server to your client's configuration using the HTTP transpo | Gemini CLI | `~/.gemini/settings.json` | | Kiro CLI | `~/.kiro/settings/mcp.json` | -Example JSON configuration (US1): +Example configuration: ```json { "mcpServers": { "datadog": { "type": "http", - "url": "https://mcp.datadoghq.com/api/unstable/mcp-server/mcp" + "url": "{{< region-param key="mcp_server_endpoint" code="true" >}}" } } } @@ -255,7 +239,7 @@ The MCP Server uses OAuth 2.0 for [authentication][auth]. If you cannot go throu "mcpServers": { "datadog": { "type": "http", - "url": "https://mcp.datadoghq.com/api/unstable/mcp-server/mcp", + "url": "{{< region-param key="mcp_server_endpoint" code="true" >}}", "headers": { "DD_API_KEY": "", "DD_APPLICATION_KEY": "" @@ -274,7 +258,7 @@ For security, use a scoped API key and application key from a [service account][ npx @modelcontextprotocol/inspector ``` 2. In the inspector's web UI, for **Transport Type**, select **Streamable HTTP**. -3. For **URL**, enter the MCP Server endpoint for your regional Datadog site (for example, for US1: `https://mcp.datadoghq.com/api/unstable/mcp-server/mcp`). See the endpoint table in the tabs above for other sites. +3. For **URL**, enter the MCP Server endpoint for your regional Datadog site: `{{< region-param key="mcp_server_endpoint" code="true" >}}` (updates based on the region selector at the top of the documentation). 4. Click **Connect**, then go to **Tools** > **List Tools**. 5. Check if the [available tools][20] appear.