Datadog Cursor Plugin

Query your Datadog data directly from Cursor using natural language. Ask about logs, metrics, traces, dashboards, monitors, and more.

What you need

• A Datadog account
• Cursor IDE (v2.6.0+)

Getting started

If you already have the Datadog MCP server registered separately, disable or remove it first to avoid conflicts.

1. Open Cursor Settings by clicking on the gear icon in the left sidebar or by running the "Cursor Settings" command in the Command Palette.
2. Go to the Plugins section
3. Install the datadog plugin
4. When prompted, pick your Datadog domain from the Datadog Domain dropdown (e.g. mcp.datadoghq.com for US1, mcp.datadoghq.eu for EU). The plugin uses this to connect to the right Datadog site.
5. Restart Cursor, then authenticate the Datadog MCP server when prompted.

If you skipped the domain prompt, or want to change the domain later, run the /ddsetup command in an agent chat window. The agent will guide you through it.

Using the plugin

Once connected, just ask the agent anything about your Datadog data:

Show me error logs from the last hour

What monitors are currently alerting?

Find traces for service "api-gateway" with latency > 500ms

List my dashboards

Can't connect?

Never connected before? Run the /ddsetup command in an agent chat window. It will help you provide the correct Datadog MCP domain and set up the MCP server.

Was working before but stopped? Run the /ddconfig command in an agent chat window. It will check your site, authentication status, and network access to help diagnose the issue.

Changing settings

The plugin provides a few commands you can run in the agent to manage configuration:

• /ddconfig — change your Datadog site or switch organizations
• /ddtoolsets — enable or disable groups of tools

Advanced usage

Key authentication

Instead of OAuth, you can authenticate using a Datadog API key and application key. Set all three environment variables before starting Cursor:

DD_MCP_DOMAIN=your-mcp-domain \
DD_API_KEY=your-api-key \
DD_APPLICATION_KEY=your-application-key

The DD_MCP_DOMAIN value must be the MCP domain (e.g. mcp.datadoghq.com, mcp.us3.datadoghq.com, mcp.datadoghq.eu), not a URL — do not include https://. When using key authentication, /ddsetup is not required — the plugin connects directly.

Environment variable overrides

The plugin uses environment variables with default values in its registration file. You can override these defaults by setting the environment variables directly:

• DD_MCP_DOMAIN — the Datadog MCP domain. This is the same value you pick from the Datadog Domain dropdown when installing the plugin; Cursor sets it for you. You can also set it manually in your shell for non-standard environments or key authentication.
• DD_MCP_TOOLSETS — overrides the enabled toolsets (comma-separated). If set, the plugin uses this value regardless of what /ddtoolsets configured.

When environment variables are set, /ddsetup, /ddconfig, and /ddtoolsets still edit the default values in the registration file, but those defaults won't take effect until the environment variables are removed. In particular, to make /ddsetup or /ddconfig drive the domain, clear the Datadog Domain value in the plugin's settings first.

Good to know

• By default, authentication is handled via OAuth in your browser. Key authentication is also supported.
• No Datadog credentials are sent to the AI model provider.

Support

• Datadog MCP Server Documentation

Legal

See the LICENSE and NOTICE files included with this plugin.

For details on how Datadog handles your data, see the Datadog Privacy Policy.