Datadog plugin config lets you save a key combination that can't work, with no error or recovery

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

When I set up the Datadog plugin for cloud agents, the setup form let me save an Application Key with no API Key. Datadog needs both keys together, or neither if you use OAuth sign-in. The form accepted it anyway, and Datadog then silently didn’t work. Nothing told me the setup was invalid or how to fix it. I only got it working after clearing the variables and using OAuth.

Suggestions:

  1. Validate the form. Block saving an Application Key without an API Key, or show an inline warning like “An Application Key requires an API Key. Leave both empty to sign in with OAuth.”
  2. Make OAuth the obvious default. Mark the key fields as advanced, so people don’t fill them in thinking they’re required.
  3. Self-healing or a clear error. When a configured MCP fails to connect or authenticate, say why (missing key, bad domain, auth failed) and offer a fix, like “Clear keys and sign in with OAuth”, instead of the tools just not showing up.
  4. Fix cloud agent support for the plugin. Support’s forum answer says the plugin version doesn’t apply in cloud agents yet and needs a manual URL. That should work out of the box, or the plugin page should say so.

Environment: Windows 11, Cursor desktop plus cloud agents at cursor.com/agents, Datadog US1 (mcp.datadoghq.com).

Steps to Reproduce

  • Go to cursor.com/agents and open the Datadog plugin (Verified by Cursor) to configure it for cloud agents.

  • In the setup form, leave DD API Key empty.

  • Leave Datadog Domain as mcp.datadoghq.com.

  • Enter a value in DD Application Key.

  • Click Save.

  • Start a cloud agent and ask it to use Datadog, for example “list my Datadog monitors”.

Expected Behavior

The form blocks saving, or warns that an Application Key needs an API Key and that you can leave both empty to sign in with OAuth. If the connection fails, the agent or the settings page explains why and how to fix it.

Operating System

Windows 10/11

Version Information

Version: 3.30.14 (user setup)
VS Code Extension API: 1.128.0
Commit: 5f54c8173e5552412beb40702adac16275677fa0
Date: 2026-11-13T06:36:47.504Z
Layout: Agent Window
Build Type: Stable
Release Track: Default
Electron: 43.8.9
Chromium: 150.0.7871.250
Node.js: 24.22.1
V8: 15.0.245.31-electron.0
xterm.js: 6.1.0-beta.291
OS: Windows_NT x64 10.0.26100

For AI issues: which model did you use?

Grok 4.7

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hey @Igor_Zhavrid, you’ve got it right. With only the Application Key saved, Cursor treats the plugin as set up for key sign-in, so it stops offering the Datadog sign-in, Datadog refuses the half pair, and the cloud agent starts without the Datadog tools and doesn’t tell you why.

The setup you ended on is the right one: leave both key fields empty, keep Datadog Domain, and sign in. If you ever want keys instead, fill in both.

I’ve passed this to the team, including the form check for the key pair and a clearer message when the connection is refused.

On your last point: that older forum answer is out of date. The plugin works in cloud agents now without a manual URL, as it does for you since you signed in.