Support pre-registered OAuth clients with explicit redirect URIs for remote/non-local MCP clients

[dredkin94]

datadog mcp server seems like it only allows localhost URLs based on the client list and other clients failing. can we allow a full client pre registration where we can add custom redirect URLs to support more remote clients?

[cookesan]

This repo does not appear to contain the OAuth client registration or redirect allowlist. It is mainly the public setup/examples surface for Datadog's hosted MCP endpoint:

https://mcp.datadoghq.com/api/unstable/mcp-server/mcp

The README points non-US1 users to the equivalent regional hosted endpoint and sends client/auth details to the Datadog setup docs.

So a custom redirect URL is not something you can enable from this repository or from a local config here. If the hosted MCP server currently only allows localhost-style callback URLs for the supported clients, adding remote client redirect URIs would need a Datadog-side product/server change: registered client metadata plus a redirect URI allowlist.

The useful feature request framing is probably: "support pre-registered OAuth clients with explicit redirect URIs for remote/non-local MCP clients."

[dredkin94]

Is this repo not maintained by datadog?

We need to be able to allow those other redirect URLs in the datadog MCP configuration console but I can't seem to find it.

[cookesan]

Yes, it is a Datadog-maintained repo. The important distinction is that this repo does not appear to expose the hosted MCP OAuth/client-registration control plane.

The repo documents Datadog's hosted MCP endpoint and client setup. I do not see repo code or config for OAuth client registration, redirect URI allowlisting, or the Datadog configuration console. So if the console has no field for those redirect URLs, that looks like a Datadog product/control-plane gap rather than a repo-local setting.

I would file/support-request it as: "MCP hosted endpoint should support pre-registered OAuth clients with explicit redirect URI allowlists for remote clients." That keeps the request aimed at the Datadog-side configuration surface.

[cookesan]

Yes, this repo appears to be Datadog-maintained: it is under datadog-labs, and the README describes it as the official Datadog MCP Server. But the repo is mostly setup docs/examples for Datadog's managed MCP endpoint, not the implementation or the Datadog-side OAuth configuration UI. README: https://github.com/datadog-labs/mcp-server

From the current setup docs, the documented auth paths are:

• remote OAuth 2.0 for supported MCP clients
• DD_API_KEY/DD_APPLICATION_KEY HTTP headers when OAuth cannot be used
• local datadog_mcp_cli stdio authentication when remote auth is unreliable or unavailable

Docs: https://docs.datadoghq.com/bits_ai/mcp_server/setup/#authentication

I do not see a documented console setting for adding arbitrary OAuth redirect URIs to the managed Datadog MCP app. For a non-local client today, I would use one of the documented auth paths above; if you need Datadog to allow-list a new hosted redirect URI, that looks like a Datadog support/feedback request rather than a repo setting.