MCP setup: recommend Datadog plugin/connector as default for Claude clients by sumedham · Pull Request #36654 · DataDog/documentation

sumedham · 2026-05-13T17:22:58Z

What's changing

On the MCP Server setup page, lead with the new GA install paths for Claude clients:

Claude Code tab → recommend installing the Datadog plugin from the Claude Code Plugin Marketplace (/plugin marketplace add DataDog/claude-marketplace → /ddsetup). Existing claude mcp add / ~/.claude.json instructions are kept as a "Manual MCP Server configuration" fallback in a collapsed section.
Claude tab → recommend installing the Datadog Connector from the Claude Connectors Directory (Add Connector → OAuth). Existing custom-connector URL setup is kept as a "Manual setup with a custom connector" fallback in a collapsed section.
Supported clients table → annotate both rows with the new recommended path.

Why

The Datadog plugin for Claude Code (Anthropic Plugin Marketplace) and the Datadog Connector for Claude (Claude Connectors Directory) are now GA. Both remove the manual MCP-Server JSON configuration that previously gated adoption — the plugin auto-updates, ships /ddsetup for site/org selection, and bundles future skills; the connector includes MCP Apps for in-product visualizations. Claude Code is used by >70% of orgs using coding agents on Datadog, so the friction reduction matters.

Available in all regions except GovCloud — preserved by the existing {{< site-region region="gov,gov2" >}} block.

Items to verify before merge

Claude Connectors Directory URL — used https://claude.ai/directory as the link target for "Datadog Connector". If the directory lives at a different path (e.g. claude.ai/integrations or a direct Datadog-connector URL), please correct.
Plugin install command syntax — used /plugin install datadog@datadog (Anthropic's <plugin-name>@<marketplace-name> convention). The exact suffix depends on the name field in DataDog/claude-marketplace's marketplace.json — happy to update if it should be a different marketplace name.

Out of scope

Other client tabs (Cursor, Codex, Gemini, VS Code, JetBrains, etc.) — no changes; they already have appropriate one-click/plugin paths or remain unchanged.
Translations (fr/ja/ko/es) intentionally not modified per CONTRIBUTING.md.

🤖 Generated with Claude Code

The Datadog plugin for Claude Code and the Datadog Connector for Claude are now GA. Make these the recommended install paths on the MCP Server setup page, since they remove the manual MCP-configuration friction that gates adoption. - Claude Code tab: lead with /plugin marketplace add DataDog/claude-marketplace + /ddsetup; collapse the existing claude mcp add / ~/.claude.json flow into a "manual MCP Server configuration" fallback - Claude tab: lead with the directory connector + Add Connector flow; collapse the existing custom-connector URL flow into a "manual setup with a custom connector" fallback - Supported clients table: note the plugin/connector as recommended for the two clients Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

github-actions · 2026-05-13T17:27:31Z

Preview links (active after the `build_preview` check completes)

Modified Files

https://docs-staging.datadoghq.com/sumedham/claude-plugin-connector-recommended/bits_ai/mcp_server/setup

Reference-style markdown links do not resolve inside tab blocks in this docs build. Hardcode the URLs inline in the Claude and Claude Code tabs, and remove the now-orphaned reference definitions. Also replace the em dashes in the lead-in sentences with periods. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Use the GA marketing pages instead of the GitHub repo and directory root: - Datadog plugin: https://claude.com/plugins/datadog - Datadog Connector: https://claude.ai/directory/connectors/datadog Updates the inline links in both tabs and the supported-clients table footer references. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

m-paternostro · 2026-05-13T20:01:03Z


 {{< site-region region="us,us3,us5,eu,ap1,ap2" >}}
-Selected endpoint ({{< region-param key="dd_site_name" >}}): <code>{{< region-param key="mcp_server_endpoint" >}}</code>.
+1. Add the Datadog marketplace to Claude Code:


Because we are now on the Claude Code official marketplace, there is no need to install our separate one. For details see this documentation.

The command to install the plugin is /plugin install datadog@claude-plugins-official

m-paternostro · 2026-05-13T20:08:28Z

 {{% tab "Claude Code" %}}

-Point your AI agent to the MCP Server endpoint for your regional [Datadog site][1]. For the correct instructions, use the {{< ui >}}Datadog Site{{< /ui >}} selector on the right side of this documentation page to select your site.
+Install the [Datadog plugin](https://claude.com/plugins/datadog) from the [Claude Code Plugin Marketplace](https://docs.claude.com/en/docs/claude-code/plugin-marketplaces). The plugin packages the Datadog MCP Server with the `/ddsetup` slash command for first-time configuration, and auto-updates as new toolsets and skills ship. If you previously installed the Datadog MCP Server manually, remove it from your Claude Code configuration to avoid conflicts.


and auto-updates as new toolsets and skills ship

Short suggestion: remove "new toolsets and".

Long suggestion: a better and shorter version of the following ;-)

I am pretty sure that the plugins installed from the marketplace are, by default, marked for auto update. Therefore the plugin is updated automatically when we release a new version. Moreover, the a new plugin version may have new skills.

The issue is with toolsets, though... Toolsets are not related to the plugin update at all: toolsets can be enabled and disabled with the /ddtoolsets command and any change to the tools in a toolset is a backend action that does not change the plugin.

m-paternostro · 2026-05-13T20:17:24Z

+1. Install the Datadog plugin when prompted, or run:
+    <pre><code>/plugin install datadog@datadog</code></pre>
+
+1. Run `/ddsetup` to choose your [Datadog site](/getting_started/site/) and organization.


Datadog site and organization

The organization is chosen on the browser during the OAuth flow, not via the command. Moreover, the command actually allows the user to enter the MCP Domain - most users will choose a domain associated with a site so indeed there is a 1-1 match. That said, we really need the domain (an internal user could type in mcp.datad0g.com as the domain to use staging, for instance).

Run /ddsetup

I am not sure how complete we want our documentation to be so I will mumble here and let you decide ;-)

Running /ddsetup manually is definitely an option but is not 100% needed. Users can do it for a more controlled experience but we actually worded the description of that skill so that it kicks in whenever the user enters a prompt that may involve "something Datadog". Moreover, the way we designed the MCP server declaration allows for advanced users to set environment variables to eliminate the requirement for /ddsetup - btw, the environment variables also allow authentication via API and APP keys.

m-paternostro · 2026-05-13T20:20:17Z

 {{% tab "Claude Code" %}}

-Point your AI agent to the MCP Server endpoint for your regional [Datadog site][1]. For the correct instructions, use the {{< ui >}}Datadog Site{{< /ui >}} selector on the right side of this documentation page to select your site.
+Install the [Datadog plugin](https://claude.com/plugins/datadog) from the [Claude Code Plugin Marketplace](https://docs.claude.com/en/docs/claude-code/plugin-marketplaces). The plugin packages the Datadog MCP Server with the `/ddsetup` slash command for first-time configuration, and auto-updates as new toolsets and skills ship. If you previously installed the Datadog MCP Server manually, remove it from your Claude Code configuration to avoid conflicts.


Should we add a section here to describe the skills we ship with the plugin?

Right now we have 3: ddsetup, ddconfig, ddtoolsets. Let me know if you want a short description for each.

sumedham and others added 2 commits May 13, 2026 15:23

sumedham marked this pull request as ready for review May 13, 2026 19:36

sumedham requested review from a team as code owners May 13, 2026 19:36

joepeeples added the editorial review Waiting on a more in-depth review label May 13, 2026

m-paternostro reviewed May 13, 2026

View reviewed changes

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

MCP setup: recommend Datadog plugin/connector as default for Claude clients#36654

MCP setup: recommend Datadog plugin/connector as default for Claude clients#36654
sumedham wants to merge 3 commits into
masterfrom
sumedham/claude-plugin-connector-recommended

sumedham commented May 13, 2026

Uh oh!

github-actions Bot commented May 13, 2026

Uh oh!

m-paternostro May 13, 2026

Uh oh!

m-paternostro May 13, 2026

Uh oh!

m-paternostro May 13, 2026

Uh oh!

m-paternostro May 13, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Conversation

sumedham commented May 13, 2026

What's changing

Why

Items to verify before merge

Out of scope

Uh oh!

github-actions Bot commented May 13, 2026

Preview links (active after the build_preview check completes)

Modified Files

Uh oh!

m-paternostro May 13, 2026

Choose a reason for hiding this comment

Uh oh!

m-paternostro May 13, 2026

Choose a reason for hiding this comment

Uh oh!

m-paternostro May 13, 2026

Choose a reason for hiding this comment

Uh oh!

m-paternostro May 13, 2026

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Preview links (active after the `build_preview` check completes)