DataDog MCP does not exist in Cloud Agents

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

  • Editor, Tab & Chat (autocomplete, Composer, in-editor agent)
  • Terminal & commands
  • Models, pricing & API keys (availability, Auto/Max, BYOK/Bedrock)
  • MCP & tools
  • Cloud Agents & Automations (cursor.com/agents, scheduled/event)
  • BugBot & Code Review
  • Cursor CLI
  • Cursor Mobile
  • Remote (SSH / Dev Containers / WSL)
  • Account, billing & login
  • Something else…

Describe the Bug
I am trying to run the ‘Investigate top Datadog errors’ automation using a cloud agent, however runs keeping failing with ‘Datadog MCP tool fails live tool discovery’ and it reports serverStatus: "error"'.I have setup the DataDog MCP. It appears to be connected in the tool list for the automation (see below). DataDog MCP works fine for me locally.

Screenshot 2026-08-05 at 10.42.32
Screenshot 2026-08-05 at 10.42.321762×122 7.25 KB

Steps to Reproduce
How can you reproduce this bug? We have a much better chance at fixing issues if we can reproduce them!

  1. In Cursor Web, navigate to Automations > Investigate top Datadog Errors and click on it.
  2. Under Tools, Datadog shows ‘Disconnect’ button and edit button, suggesting it is connected.
  3. Click on ‘Test run’ button in right hand corner of the page.
  4. The run will show in its output thet MCP tool fails live tool discovery.

Expected Behavior
The automation should be able to access Datadog and investigate Datadog errors.

Screenshots / Screen Recordings
If applicable, attach images or videos (.jpg, .png, .gif, .mp4, .mov)

Operating System

  • Windows 10/11
  • MacOS
  • Linux

Version Information

  • For Cursor IDE: Menu → About Cursor → Copy
  • For Cursor CLI: Run agent about in your terminal
IDE:
Version: 3.14.7 (Universal)
VS Code Extension API: 1.128.0
Commit: a758f2241ca99fecf380180b6cbdbbce0f1f42c0
Date: 2026-07-30T06:41:34.009Z
Layout: Agent Window
Build Type: Stable
Release Track: Default
Electron: 40.10.3
Chromium: 144.0.7559.236
Node.js: 24.15.0
V8: 14.4.258.32-electron.0
xterm.js: 6.1.0-beta.291
OS: Darwin arm64 25.5.0

CLI:
N/A

For AI issues: which model did you use?
Model name: Opus 5

For AI issues: add Request ID with privacy disabled
Request ID: bc-bae0d9a0-1f69-4c1d-b7a2-460e2e213960
For Background Agent issues, also post the ID: bc-…

Additional Information
One thing I have noticed is if I click on the edit icon to the right, the modal opens and never displays the Datadog domain I previously selected. If I choose the correct domain and hit ‘Save’ there is no clear success or failure message. It appears to save and the modal closes. I don’t know if this is related but it’s the only unusual thing that points me to a potential issue.

Screenshot 2026-08-05 at 10.43.32
Screenshot 2026-08-05 at 10.43.32864×704 38.2 KB

Does this stop you from using Cursor?

  • Yes - Cursor is unusable
  • Sometimes - I can sometimes use Cursor
  • No - Cursor works, but with this issue
    I can use other cursor functionality. just this automation doesn’t work.
2

Hi there!

We detected that this may be a bug report, so we’ve moved your post to the Bug Reports category.

To help us investigate and fix this faster, could you edit your original post to include the details from the template below?

Bug Report Template - Click to expand

Where does the bug appear (feature/product)?

  • Editor, Tab & Chat (autocomplete, Composer, in-editor agent)
  • Terminal & commands
  • Models, pricing & API keys (availability, Auto/Max, BYOK/Bedrock)
  • MCP & tools
  • Cloud Agents & Automations (cursor.com/agents, scheduled/event)
  • BugBot & Code Review
  • Cursor CLI
  • Cursor Mobile
  • Remote (SSH / Dev Containers / WSL)
  • Account, billing & login
  • Something else…

Describe the Bug
A clear and concise description of what the bug is.

Steps to Reproduce
How can you reproduce this bug? We have a much better chance at fixing issues if we can reproduce them!

  1. …
  2. …
  3. …

Expected Behavior
What is meant to happen here that isn’t working correctly?

Screenshots / Screen Recordings
If applicable, attach images or videos (.jpg, .png, .gif, .mp4, .mov)

Operating System

  • Windows 10/11
  • MacOS
  • Linux

Version Information

  • For Cursor IDE: Menu → About Cursor → Copy
  • For Cursor CLI: Run agent about in your terminal
IDE:
Version: 2.xx.x
VSCode Version: 1.105.1
Commit: ......

CLI:
CLI Version 2026.01.17-d239e66

For AI issues: which model did you use?
Model name (e.g., Sonnet 4, Tab…)

For AI issues: add Request ID with privacy disabled
Request ID: f9a7046a-279b-47e5-ab48-6e8dc12daba1
For Background Agent issues, also post the ID: bc-…

Additional Information
Add any other context about the problem here.

Does this stop you from using Cursor?

  • Yes - Cursor is unusable
  • Sometimes - I can sometimes use Cursor
  • No - Cursor works, but with this issue

The more details you provide, the easier it is for us to reproduce and fix the issue. Thanks!

7

Hey @ebyoto
This is on our side, not your setup - the plugin-managed Datadog entry (the domain-dropdown one) isn’t applying to cloud runs right now, so the URL comes out invalid and the tools get dropped during discovery.

Workaround that works today: in your Cloud Agent / Automation MCP settings (cursor.com/agents, not your local mcp.json), add Datadog as a manual HTTP MCP server with the full URL hard-coded:

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

Swap the domain for your Datadog site if you’re not on US1 (EU → mcp.datadoghq.eu, US3 → mcp.us3.datadoghq.com, US5 → mcp.us5.datadoghq.com). Datadog’s setup page: https://docs.datadoghq.com/mcp_server/setup/?tab=cursor

This is an issue we’re tracking - I’ll follow up here when there’s an update.

9

Thank you @mohitjain for the quick response, that workaround fixed the issue :+1: Would be great to keep an eye on a permanent solution.