Commit graph

3 commits

Author SHA1 Message Date
Pierre Gimalac
cab8c78682
Remove dd- prefix from MCP server names (#58065)
<!-- dd-meta {"pullId":"3e3f1369-6616-44bb-bc3f-f400847b8529","source":"chat","resourceId":"3c3d69a2-748e-4124-bc93-130bfccfeb14","workflowId":"13d096cc-0f95-4ce5-a865-dd72e7e90f57","codeChangeId":"13d096cc-0f95-4ce5-a865-dd72e7e90f57","sourceType":"code_channel"} -->
<!--Please give us some feedback on your experience writing this PR ! https://app.datadoghq.com/forms/43db4c02-6837-400c-8083-692e141b1b88 !-->

### What does this PR do?

- Use unprefixed MCP server names throughout the dotagents declarations and all committed client configs, including the manually maintained Slack and Zed entries.
- Keep the documentation consistent with the new names while preserving endpoints and client-specific authentication settings.

### Motivation

The dd- prefix creates duplicate entries alongside developers' local MCP servers. Unprefixed names align this repository with dd-source and dd-go so developers can use consistent server names across repositories.

### Describe how you validated your changes

Parsed agents.toml and all six client configs as TOML or JSON/JSONC. Compared each config against the original to verify that only server identifiers changed, including preservation of Slack OAuth settings and unrelated Zed configuration. Confirmed all declared server names and URLs match the source and no prefixed MCP identifiers remain in the configs or documentation.

Dotagents regeneration was not run because mise and dotagents are unavailable in this sandbox.

### Additional Notes

Updates the configuration introduced in PR #53874, "Configure MCP servers". The naming change was agreed with Ofek Lev.

---

PR by Bits - [View session in Datadog](https://app.datadoghq.com/code/3c3d69a2-748e-4124-bc93-130bfccfeb14)

Comment @datadog to request changes

Co-authored-by: datadog-bits <263423550+datadog-bits@users.noreply.github.com>
Co-authored-by: pierre.gimalac <pierre.gimalac@datadoghq.com>
2026-10-16 12:51:45 +00:00
Régis Desgroppes
f497b1760d
Switch Datadog MCP endpoint and Claude marketplace to their new homes (#57783)
### What does this PR do?
Point the `dd-api` MCP server at the supported Datadog endpoint in `agents.toml`, the configs it generates and `.zed/settings.json`.

Point `AGENTS.md` to the new home of the Datadog Claude Marketplace.

### Motivation
The Datadog MCP server reports `/api/unstable/mcp-server/mcp` as deprecated in favor of `/v1/mcp`, the US1 endpoint in its setup docs.

`DataDog/claude-marketplace` gets deleted on 2026-10-08 in favor of `ddoghq/claude-marketplace`.

### Describe how you validated your changes
`/v1/mcp` and `/v1/mcp?toolsets=all` answer 401 to an unauthenticated MCP `initialize` request, whereas an unknown path answers 404.

Co-authored-by: regis.desgroppes <regis.desgroppes@datadoghq.com>
2026-10-08 16:37:57 +00:00
Ofek Lev
20a1182ecc
Configure MCP servers (#53874)
### What does this PR do?

This moves over the MCP config we currently define in our dev env [here](https://github.com/DataDog/datadog-agent-buildimages/blob/main/dev-envs/linux/claude.sh) and [here](https://github.com/DataDog/datadog-agent-buildimages/blob/main/dev-envs/linux/codex.sh).

### Motivation

We want to remove all dependence on tools and config defined externally. For this change in particular, it's also far easier to configure and more compatible with the AI agent ecosystem.

### Additional Notes

I chose to use [dotagents](https://github.com/getsentry/dotagents) rather than writing our own tooling, for now, as it supports most of what we want and running JavaScript apps is pretty easy since mise is already [available](https://github.com/DataDog/datadog-agent-buildimages/blob/main/tools/dotslash/config/mise.json) in our dev envs.

I opened a [PR](https://github.com/getsentry/dotagents/pull/141) that adds support for Windows.

Co-authored-by: ofek.lev <ofek.lev@datadoghq.com>
2026-07-21 22:20:55 +00:00