--- title: "Datadog MCP server | Agent MCP Directory" description: "Datadog: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure." canonical: https://agentmcpdirectory.com/directory/datadoghq-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Datadog MCP server | Agent MCP Directory > Datadog: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Infrastructure. Source: https://agentmcpdirectory.com/directory/datadoghq-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Datadog: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Datadog at mcp.datadoghq.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Datadog | | --- | --- | | Domain | datadoghq.com | | Category | Infrastructure (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Tranco rank | 281 on the list of 4 November 2026 | | Ora score | 69, grade C; Ora scanned the domain on 15 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for datadoghq.com, a vendor-published score) | | Company found through | the vendor's own documentation; Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.datadoghq.com/api/unstable/mcp-server/mcp | | --- | --- | | How it was found | listed in the vendor's own documentation; Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 1,102 ms over 1 attempt | | Documentation | docs.datadoghq.com | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:55:53Z https://mcp.datadoghq.com/api/unstable/mcp-server/mcp sent initialize result auth-required (HTTP 401) 1031 ms - 20:01:29Z https://mcp.datadoghq.com/api/unstable/mcp-server/mcp sent initialize result auth-required (HTTP 401) 1102 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer resource_metadata="https://mcp.datadoghq.com/.well-known/oauth-protected-resource/api/unstable/mcp-server/mcp" | | Protected resource metadata | mcp.datadoghq.com | | Authorization server metadata | mcp.datadoghq.com | | Registration endpoint | https://app.datadoghq.com/api/v2/oauth2/register | ### The sign-in route, step by step 1. Request `https://mcp.datadoghq.com/api/unstable/mcp-server/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.datadoghq.com/.well-known/oauth-protected-resource/api/unstable/mcp-server/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://app.datadoghq.com/api/v2/oauth2/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI | Package | @datadog/datadog-ci on npm (page) | | --- | --- | | Exists | yes | | Latest version | 5.27.0 | | Last publish | 4 November 2026 | | Command names | datadog-ci | | Checked | 4 November 2026 | ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Not found (the crawl got a non-200 answer). | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/datadoghq-com/index.md) ## Sources - [Datadog MCP documentation](https://docs.datadoghq.com/bits_ai/mcp_server/), read 4 November 2026 - [Ora score page for datadoghq.com](https://ora.ai/score/datadoghq.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 15 October 2026, read from GET /api/score) - [Datadog website](https://datadoghq.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026