Twenty toolsets is far more than any one conversation needs, and loading them all would cost tokens on every turn. Putting the selection in the connection string means an incident-response client and a dashboards client can point at the same server and see different surfaces. Two things to check before planning: your Datadog site determines the endpoint, and the roles are separate from ordinary Datadog permissions — someone has to grant mcp_read and mcp_write.
Datadog's own server. There is no single address: you take the endpoint for your Datadog site — US1, US3, US5, EU, AP or UK — from their setup page. Government sites are not supported.
- More than 20 toolsets: logs, metrics, traces, dashboards, monitors, incidents, APM, synthetics, security, workflows and others
- Toolsets are enabled per connection with a query parameter — ?toolsets=apm,llmobs — rather than all at once
OAuth, configured automatically by the client during setup, or a bearer token, or the API and application key headers. The account needs the mcp_read and mcp_write roles.
Paste a URL, then authorize — add the endpoint to your client, then approve the OAuth consent screen