Skip to content

Streamline setup instructions for MCP Server clients [DOCS-13657]#35412

Open
joepeeples wants to merge 8 commits intomasterfrom
joepeeples/13657-mcp-setup-streamline
Open

Streamline setup instructions for MCP Server clients [DOCS-13657]#35412
joepeeples wants to merge 8 commits intomasterfrom
joepeeples/13657-mcp-setup-streamline

Conversation

@joepeeples
Copy link
Contributor

@joepeeples joepeeples commented Mar 19, 2026

What does this PR do? What is the motivation?

Contributes to DOCS-13657 by streamlining setup instructions to involve less reading and clearer, simpler actions.

  • Remove unnecessary heading and extraneous text throughout
  • Refactor tabs so each is relatively self-contained: a user can follow just the tab's instructions and get MCP working, doesn't require reading the whole page, other sections, etc.
    • Add toolsets mentions & URLs, link to larger toolsets section

Note

Admittedly, the tabs contain some duplicated content with additional maintenance concerns. I'm working on a longer-term solution for that, but for near-term we need to get this content updated to meet an aggressive timeline.

Merge instructions

Merge readiness:

  • Ready for merge

For Datadog employees:

Your branch name MUST follow the <name>/<description> convention and include the forward slash (/). Without this format, your pull request will not pass CI, the GitLab pipeline will not run, and you won't get a branch preview. Getting a branch preview makes it easier for us to check any issues with your PR, such as broken links.

If your branch doesn't follow this format, rename it or create a new branch and PR.

[6/5/2025] Merge queue has been disabled on the documentation repo. If you have write access to the repo, the PR has been reviewed by a Documentation team member, and all of the required checks have passed, you can use the Squash and Merge button to merge the PR. If you don't have write access, or you need help, reach out in the #documentation channel in Slack.

AI assistance

Additional notes

@joepeeples joepeeples added the WORK IN PROGRESS No review needed, it's a wip ;) label Mar 19, 2026
@joepeeples joepeeples changed the title Streamline setup instructions Streamline setup instructions [DOCS-13657] Mar 19, 2026
@joepeeples joepeeples changed the title Streamline setup instructions [DOCS-13657] Streamline setup instructions for MCP Server clients [DOCS-13657] Mar 19, 2026
@github-actions
Copy link
Contributor

Preview links (active after the build_preview check completes)

Modified Files

@joepeeples joepeeples marked this pull request as ready for review March 20, 2026 17:32
@joepeeples joepeeples requested a review from a team as a code owner March 20, 2026 17:32
@joepeeples joepeeples removed the WORK IN PROGRESS No review needed, it's a wip ;) label Mar 20, 2026
Copy link
Contributor

@urseberry urseberry left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice job making functional and readable page about a complex topic!

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][2]. 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.
1. Install the extension (omit `--profile` and name to install to the default Cursor profile):
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
1. Install the extension (omit `--profile` and name to install to the default Cursor profile):
1. Install the extension (omit `--profile` and profile name to install to the default Cursor profile):

```shell
cursor --install-extension datadog.datadog-vscode --profile <PROFILE_NAME>
```
Alternatively, install the Datadog extension following [these instructions][2]. If you have the extension installed already, make sure it's the latest version.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Alternatively, install the Datadog extension following [these instructions][2]. If you have the extension installed already, make sure it's the latest version.
Alternatively, install the [Datadog extension][2]. If you have the extension installed already, make sure it's the latest version.

5. Confirm the Datadog MCP Server is available and the [tools][3] are listed: Go to **Cursor Settings** (`Shift` + `Cmd/Ctrl` + `J`), and select the **MCP** tab.
1. **Restart the IDE.**
1. Confirm the Datadog MCP Server is available and the [tools][3] are listed: Go to **Cursor Settings** (`Shift` + `Cmd/Ctrl` + `J`), select the **Tools & MCP** tab, and expand the extension's tools list.
1. If you previously installed the Datadog MCP Server manually, remove it from the IDE's configuration to avoid conflicts.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this a prerequisite? If so, it should be step 1.

{{% tab "Claude Code" %}}

Point your AI agent to the MCP Server endpoint for your regional [Datadog site][1].
Point your AI agent to the MCP Server endpoint for your regional [Datadog site][1]. Use the **Datadog Site** selector on the right side of this page to select your site.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Point your AI agent to the MCP Server endpoint for your regional [Datadog site][1]. Use the **Datadog Site** selector on the right side of this page to select your site.
Point your AI agent to the MCP Server endpoint for your regional [Datadog site][1].
To get the correct instructions for your site, use the **Datadog Site** selector on the right side of this documentation page to select your site.

2. When prompted for a URL, enter the Datadog MCP Server endpoint for your [Datadog site][2] ({{< region-param key="dd_site_name" >}}):
1. Follow the Claude help center guide on [custom connectors][1] to add a new custom connector.

1. When prompted for a URL, enter the Datadog MCP Server endpoint for your [Datadog site][2] ({{< region-param key="dd_site_name" >}}). Use the **Datadog Site** selector on the right side of this page to select your site.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
1. When prompted for a URL, enter the Datadog MCP Server endpoint for your [Datadog site][2] ({{< region-param key="dd_site_name" >}}). Use the **Datadog Site** selector on the right side of this page to select your site.
1. When prompted for a URL, enter the Datadog MCP Server endpoint for your [Datadog site][2] ({{< region-param key="dd_site_name" >}}). Use the **Datadog Site** selector on the right side of this documentation page to select your site.

3. Sign in to your Datadog account.
4. **Restart the IDE.**
5. Confirm the Datadog MCP Server is available and the [tools][3] are listed: Open the chat panel, select agent mode, and click the **Configure Tools** button.
1. Install the extension (omit `--profile` and name to install to the default VS Code profile):
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
1. Install the extension (omit `--profile` and name to install to the default VS Code profile):
1. Install the extension (omit `--profile` and profile name to install to the default VS Code profile):

```shell
code --install-extension datadog.datadog-vscode --profile <PROFILE_NAME>
```
Alternatively, install the Datadog extension following [these instructions][2]. If you have the extension installed already, make sure it's the latest version.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Alternatively, install the Datadog extension following [these instructions][2]. If you have the extension installed already, make sure it's the latest version.
Alternatively, install the [Datadog extension][2]. If you have the extension installed already, make sure it's the latest version.

1. **Restart the IDE.**
1. Confirm the Datadog MCP Server is available and the [tools][3] 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%;" >}}
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`.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If this needs to be done at the beginning, it should be step 1.

JetBrains offers the [Junie][1] and [AI Assistant][2] plugins for their range of IDEs. Alternately, many developers use an agent CLI, such as Claude Code or Codex, alongside their IDE. The sections below describe how to configure the Datadog MCP Server for use by these AI tools.
JetBrains offers the [Junie][1] and [AI Assistant][2] plugins for their range of IDEs. Alternatively, many developers use an agent CLI, such as Claude Code or Codex, alongside their IDE.

Point your plugin to the MCP Server endpoint for your regional [Datadog site][3]. Use the **Datadog Site** selector on the right side of this page to select your site.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Point your plugin to the MCP Server endpoint for your regional [Datadog site][3]. Use the **Datadog Site** selector on the right side of this page to select your site.
Point your plugin to the MCP Server endpoint for your regional [Datadog site][3]. Use the **Datadog Site** selector on the right side of this documentation page to select your site.

The following clients can connect to the Datadog MCP Server: [Goose][1], [Kiro][2], [Kiro CLI][3], [Cline][4], and other MCP-compatible clients. Use these instructions for remote authentication when your client supports it. For Cline or when remote authentication is unreliable or not available, use [local binary authentication](#local-binary-authentication).
For most other [supported clients](#supported-clients), use these instructions for remote authentication. For Cline or when remote authentication is unreliable or not available, use [local binary authentication](#local-binary-authentication).

Point your AI agent to the MCP Server endpoint for your regional [Datadog site][1]. Use the **Datadog Site** selector on the right side of this page to select your site.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Point your AI agent to the MCP Server endpoint for your regional [Datadog site][1]. Use the **Datadog Site** selector on the right side of this page to select your site.
Point your AI agent to the MCP Server endpoint for your regional [Datadog site][1]. Use the **Datadog Site** selector on the right side of this documentation page to select your site.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants