
How to add Datadog MCP Server (Official Remote) to Cursor
Datadog's managed remote server: query logs, metrics, traces, monitors and incidents. Paste the config into ~/.cursor/mcp.json and restart Cursor.
Last updated June 15, 2026 · 250★ · http · oauth · official
Cursor config for Datadog MCP Server (Official Remote)
claude mcp add --transport http datadog https://mcp.datadoghq.com/api/unstable/mcp-server/mcp{
"mcpServers": {
"datadog-mcp-server-official-remote": {
"url": "https://mcp.datadoghq.com/api/unstable/mcp-server/mcp",
"type": "streamable-http"
}
}
}Remote server — no local install needed. Restart the client after saving the config.
Setup steps
- 1Open Cursor → Settings → MCP → Add new MCP server (or edit ~/.cursor/mcp.json directly).
- 2Paste the Datadog MCP Server (Official Remote) config below into the "mcpServers" object.
- 3Fill in placeholder secrets, then save.
- 4Cursor reloads MCP servers automatically — check Settings → MCP for a green status dot.
- 5Ask Cursor to use one of Datadog MCP Server (Official Remote)'s tools to confirm it's connected.
Before you start
- A Datadog account on a supported site (e.g. US1 or EU), with access to the MCP server Preview enabled for your org
- An MCP client that supports remote HTTP servers with OAuth (e.g. Claude Code, Cursor, OpenAI Codex CLI)
- Authorization to your Datadog org — the remote server uses an OAuth sign-in flow; Datadog API and application keys are used for the alternative/self-hosted auth path
- Appropriate Datadog roles/permissions for the data you want to query (logs, APM, incidents, etc.)
What Datadog MCP Server (Official Remote) can do in Cursor
search_datadog_logsSearch and retrieve logs by query, facets, tags, and time range
get_logs / query log analyticsAggregate and analyze logs (grouping, stats) over a time window
query_timeseries_dataQuery metric timeseries for a metric query over a start/end time range
list_metricsDiscover available metrics and their metadata/context
search_datadog_spans / list_spansSearch APM distributed spans for tracing investigations
get_traceFetch a complete distributed trace by ID
list_monitorsList monitors with their configs, thresholds, and alert states (filter by name/tag/state)
get_monitorGet details for a specific monitor
Security
This is an unstable/preview API endpoint that authenticates against your Datadog org via browser flow, so it can read sensitive logs and traces. Restrict which users can authorize it and prefer read-only scopes.
Datadog MCP Server (Official Remote) + Cursor FAQ
Where is the Cursor config file?
Cursor reads MCP servers from ~/.cursor/mcp.json. Paste the Datadog MCP Server (Official Remote) config there under the "mcpServers" key and restart the client.
Is Datadog MCP Server (Official Remote) safe to use with Cursor?
This is an unstable/preview API endpoint that authenticates against your Datadog org via browser flow, so it can read sensitive logs and traces. Restrict which users can authorize it and prefer read-only scopes.
Is this the official Datadog MCP server?
Yes — it is built and hosted by Datadog (the Bits AI MCP server), developed in collaboration with OpenAI, and is distinct from community Datadog MCP servers.
How do I authenticate?
The managed remote server uses an OAuth browser sign-in to your Datadog org; an alternative path uses Datadog API and application keys. You must have permissions for the data you query.
Which endpoint do I use?
Use the endpoint for your Datadog site — US1 is https://mcp.datadoghq.com/api/unstable/mcp-server/mcp and EU is https://mcp.datadoghq.eu/api/unstable/mcp-server/mcp, with regional variants for other sites.