# Unable to Configure DataDog MCP with an Automation

**URL:** <https://forum.cursor.com/t/unable-to-configure-datadog-mcp-with-an-automation/163816>\
**Category:** Bug Reports\
**Tags:** plugins, mcp, automations\
**Created:** [June 22, 2026, 12:35pm UTC](https://forum.cursor.com/t/unable-to-configure-datadog-mcp-with-an-automation/163816 "2026-06-22T12:35:11Z")\
**Posts on this page:** 16\
**Page:** 1

<div class="post-metadata">

**Author:** ![Greg\_Farrow](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/greg_farrow/32/80070_2.png) [@Greg\_Farrow](https://forum.cursor.com/u/Greg_Farrow)\
**Post date:** [June 22, 2026, 12:35pm UTC](https://forum.cursor.com/t/unable-to-configure-datadog-mcp-with-an-automation/163816/1 "2026-06-22T12:35:11Z")

</div>

### Where does the bug appear (feature/product)?

Somewhere else…

### Describe the Bug

Until recently I had been using the Automation “Investigate top Datadog errors”. However, recently the DataDog MCP broke and the automation stopped working.

I can no longer setup the DataDog MCP on the automation agents.

The Datadog MCP is unusable in automations, which is a big issue for my use case.

### Steps to Reproduce

- Go to [https://cursor.com/automations](https://cursor.com/automations) and choose the “Incidents & Triage” tab, then select “Investigate top Datadog errors”
- The automation opens and at the bottom under “Tools” I can see “Datadog” with the options “Set up MCP”, edit and delete.
- When I click “Set up MCP” a dialog opens asking to install the Datadog Plugin (Note: the plugin is already installed, both locally and in the cloud, so this shouldn’t show)
- I click “Add Plugin”
- The dialog closes, but the Datadog MCP is not authenticated.

I don’t see any console logs or network activity when I click “add plugin”. There’s no indiation that anythig has happened.

### Expected Behavior

The Datadog MCP authentication completes successfully and the Datadog MCP is available to this automation (and any others I setup).

### Screenshots / Screen Recordings

 ![2.png](https://us1.discourse-cdn.com/cursor1/original/3X/0/5/05b5ec9aaaea1d86f066b6f0ffb3113b2ba3f4b7.png)

### Operating System

MacOS

### Version Information

Version: 3.8.11 (Universal)  
VS Code Extension API: 1.105.1  
Commit: e56ad3440df06d22ca7501e65fd518e905486ef0  
Date: 2026-06-18T01:40:18.333Z  
Layout: glass  
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.256  
OS: Darwin arm64 25.5.0

### Does this stop you from using Cursor

No - Cursor works, but with this issue

---

<div class="post-metadata">

**Author:** ![Colin](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/colin/32/90452_2.png) [@Colin](https://forum.cursor.com/u/Colin)\
**Post date:** [June 22, 2026, 1:23pm UTC](https://forum.cursor.com/t/unable-to-configure-datadog-mcp-with-an-automation/163816/6 "2026-06-22T13:23:29Z")

</div>

Hey @Greg_Farrow

Thanks for the report. We’ve had a couple of reports come in about this, and I can also reproduce similar behavior on my personal account!

It looks like something changed in the Datadog plugin that the Plugin install for Cloud Agents/Automations isn’t expecting. Something will have to change on our end or in the plugin! Will keep you posted.

---

<div class="post-metadata">

**Author:** ![Greg\_Farrow](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/greg_farrow/32/80070_2.png) [@Greg\_Farrow](https://forum.cursor.com/u/Greg_Farrow)\
**Post date:** [June 27, 2026, 6:41am UTC](https://forum.cursor.com/t/unable-to-configure-datadog-mcp-with-an-automation/163816/8 "2026-06-27T06:41:22Z")

</div>

Hi @Colin - has the team made any progress on this bug yet? I am still able to replicate it today. Any ideas on an estimated time to fix as this is a major issue for me, I had been relying heavily on this functionality.

Thanks

Greg

---

<div class="post-metadata">

**Author:** ![Jason\_Luo1](https://avatars.discourse-cdn.com/v4/letter/j/bc79bd/32.png) [@Jason\_Luo1](https://forum.cursor.com/u/Jason_Luo1)\
**Post date:** [June 27, 2026, 7:20am UTC](https://forum.cursor.com/t/unable-to-configure-datadog-mcp-with-an-automation/163816/9 "2026-06-27T07:20:08Z")

</div>

This is the kind of automation breakage where a visible auth state would help a lot.

If the plugin is installed but the automation agent cannot actually use the MCP connection, the UI should probably distinguish “plugin present” from “tool authenticated and available in this automation run.” Otherwise it looks configured until the job silently loses its core tool.

---

<div class="post-metadata">

**Author:** ![Colin](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/colin/32/90452_2.png) [@Colin](https://forum.cursor.com/u/Colin)\
**Post date:** [June 29, 2026, 4:50pm UTC](https://forum.cursor.com/t/unable-to-configure-datadog-mcp-with-an-automation/163816/10 "2026-06-29T16:50:05Z")

</div>

I’ll ping on this @Greg_Farrow!

---

<div class="post-metadata">

**Author:** ![Colin](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/colin/32/90452_2.png) [@Colin](https://forum.cursor.com/u/Colin)\
**Post date:** [June 29, 2026, 6:06pm UTC](https://forum.cursor.com/t/unable-to-configure-datadog-mcp-with-an-automation/163816/12 "2026-06-29T18:06:40Z")

</div>

@Greg_Farrow We just merged a fix, so next deploy this should be fixed. Check back a little later!

---

<div class="post-metadata">

**Author:** ![Greg\_Farrow](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/greg_farrow/32/80070_2.png) [@Greg\_Farrow](https://forum.cursor.com/u/Greg_Farrow)\
**Post date:** [June 30, 2026, 7:38am UTC](https://forum.cursor.com/t/unable-to-configure-datadog-mcp-with-an-automation/163816/13 "2026-06-30T07:38:23Z")

</div>

TL;DR there is more visibility but the bug remains.

@Colin I’ve tried to connect in the latest version:

Version: 3.9.16 (Universal)  
VS Code Extension API: 1.105.1  
Commit: 042b3c1a4c53f2c3808067f519fbfc67b72cad80  
Date: 2026-06-27T06:41:01.941Z  
Layout: editor  
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.256  
OS: Darwin arm64 25.5.0

First I have removed the DataDog Plugin, to attempt to set it up from scratch.

When I attempt to reconnect I see:

 ![CleanShot 2026-06-30 at 08.31.00@2x](https://us1.discourse-cdn.com/cursor1/original/3X/7/c/7c6a3b61f025075441e5b40471fa449f917cb210.png)

and in the output logs I see:

_ **2026-06-30** _ _ **08:31:38.202** _ [info] [MCPService] [MCPService] createClient: identifier=“plugin-datadog-datadog”, serverName=“datadog”

_ **2026-06-30** _ _ **08:31:38.217** _ [error] [MCPService] [MCPService] createClient completed for server: plugin-datadog-datadog, connected=false, statusType=error, error=net::ERR\_NAME\_NOT\_RESOLVED

The plugin is installed but broken.

In the Agents Window the MCP is broken for Cloud and is failing to authenticate for Local:

 ![CleanShot 2026-06-30 at 08.35.17@2x](https://us1.discourse-cdn.com/cursor1/original/3X/9/f/9fd7a80f2d5fa3aad9780cce3ef86e7676f2c3f8.png)

In older versions, the plugin would prompt for the DataDog URL to use (i.e. the region). But, in this version it does not prompt, so I suspect it is not setting the URL correctly and that is causing the error?

---

<div class="post-metadata">

**Author:** ![Greg\_Farrow](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/greg_farrow/32/80070_2.png) [@Greg\_Farrow](https://forum.cursor.com/u/Greg_Farrow)\
**Post date:** [July 3, 2026, 6:11am UTC](https://forum.cursor.com/t/unable-to-configure-datadog-mcp-with-an-automation/163816/14 "2026-07-03T06:11:27Z")

</div>

@Colin the DataDog MCP is still broken in cloud. It works locally n, but for Cloud and Automations it is still in Error state.

I have tried reinstalling the plugin and rerunning /ddsetup. But, these actions haven’t helped.

Is there an investigation still underway as this ia ba big issue for me still.

---

<div class="post-metadata">

**Author:** ![Greg\_Farrow](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/greg_farrow/32/80070_2.png) [@Greg\_Farrow](https://forum.cursor.com/u/Greg_Farrow)\
**Post date:** [July 6, 2026, 12:47am UTC](https://forum.cursor.com/t/unable-to-configure-datadog-mcp-with-an-automation/163816/15 "2026-07-06T00:47:42Z")

</div>

@Colin following the latest release the error configuring the DataDog MCP tool is still present. I was able to retrieve the following output logs - I hope these help you diagnose and fix the problem:

```  
_ **2026-07-06** _ _ **01:41:57.130** _ [info] [Shared MCP process] connecting streamableHttp for “datadog” (plugin-datadog-datadog)

_ **2026-07-06** _ _ **01:41:57.130** _ [info] [Shared MCP process] [V2 FSM] connection:connect\_start: conn=idle,auth=unknown → conn=connecting,auth=unknown

_ **2026-07-06** _ _ **01:41:57.527** _ [warning] [Shared MCP process] MCP HTTP exchange failed

_ **2026-07-06** _ _ **01:41:57.527** _ [warning] [Shared MCP process] Transient error connecting to streamableHttp server: fetch failed

_ **2026-07-06** _ _ **01:42:05.574** _ [warning] [Shared MCP process] MCP HTTP exchange completed

_ **2026-07-06** _ _ **01:42:05.685** _ [info] [Shared MCP process] MCP OAuth refresh lock acquired

_ **2026-07-06** _ _ **01:42:05.686** _ [info] [Shared MCP process] MCP OAuth refresh prepared

_ **2026-07-06** _ _ **01:42:06.353** _ [info] [Shared MCP process] MCP OAuth tokens persisted

_ **2026-07-06** _ _ **01:42:06.353** _ [info] [Shared MCP process] MCP OAuth refresh result

_ **2026-07-06** _ _ **01:42:06.354** _ [info] [Shared MCP process] MCP OAuth refresh lock released

_ **2026-07-06** _ _ **01:42:06.526** _ [info] [Shared MCP process] Successfully connected to streamableHttp server

_ **2026-07-06** _ _ **01:42:06.526** _ [info] [Shared MCP process] [V2 FSM] connection:connect\_success: conn=connecting,auth=unknown → conn=connected,auth=unknown

_ **2026-07-06** _ _ **01:42:06.596** _ [warning] [Shared MCP process] MCP HTTP exchange completed

_ **2026-07-06** _ _ **01:42:48.615** _ [info] [MCPService] [MCPService] createClient: identifier=“plugin-datadog-datadog”, serverName=“datadog”

_ **2026-07-06** _ _ **01:42:48.616** _ [info] [MCPService] [MCPService] createClient completed for server: plugin-datadog-datadog, connected=true, statusType=connected

_ **2026-07-06** _ _ **01:42:49.319** _ [info] [MCPService] [MCPService] createClient: identifier=“plugin-datadog-datadog”, serverName=“datadog”

_ **2026-07-06** _ _ **01:42:49.326** _ [info] [MCPService] [MCPService] createClient completed for server: plugin-datadog-datadog, connected=true, statusType=connected

_ **2026-07-06** _ _ **01:42:50.273** _ [info] [MCPService] [MCPService] createClient: identifier=“plugin-datadog-datadog”, serverName=“datadog”

_ **2026-07-06** _ _ **01:42:52.477** _ [info] [MCPService] [MCPService] createClient: identifier=“plugin-datadog-datadog”, serverName=“datadog”

_ **2026-07-06** _ _ **01:42:52.481** _ [info] [MCPService] [MCPService] createClient completed for server: plugin-datadog-datadog, connected=true, statusType=connected

_ **2026-07-06** _ _ **01:43:50.640** _ [error] [MCPService] [MCPService] Error creating client: Timeout waiting for EverythingProvider with command ‘mcp.createClient’

_ **2026-07-06** _ _ **01:43:50.646** _ [info] [MCPService] [MCPService] createClient: identifier=“plugin-datadog-datadog”, serverName=“datadog”

_ **2026-07-06** _ _ **01:44:51.633** _ [error] [MCPService] [MCPService] Error creating client: Timeout waiting for EverythingProvider with command ‘mcp.createClient’  
```

---

<div class="post-metadata">

**Author:** ![Greg\_Farrow](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/greg_farrow/32/80070_2.png) [@Greg\_Farrow](https://forum.cursor.com/u/Greg_Farrow)\
**Post date:** [July 7, 2026, 4:00pm UTC](https://forum.cursor.com/t/unable-to-configure-datadog-mcp-with-an-automation/163816/16 "2026-07-07T16:00:45Z")

</div>

Hey @Colin its been over 2 weeks and this is still broken for me and is causing me serious issues with my production workload. It would be really helpful to know if this is still being worked on as this thread has gone cold. Thanks

---

<div class="post-metadata">

**Author:** ![Colin](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/colin/32/90452_2.png) [@Colin](https://forum.cursor.com/u/Colin)\
**Post date:** [July 7, 2026, 4:32pm UTC](https://forum.cursor.com/t/unable-to-configure-datadog-mcp-with-an-automation/163816/17 "2026-07-07T16:32:34Z")

</div>

Sorry for the delay, @Greg_Farrow. I’ll reflag this for the team.

---

<div class="post-metadata">

**Author:** ![Colin](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/colin/32/90452_2.png) [@Colin](https://forum.cursor.com/u/Colin)\
**Post date:** [July 8, 2026, 7:18pm UTC](https://forum.cursor.com/t/unable-to-configure-datadog-mcp-with-an-automation/163816/18 "2026-07-08T19:18:36Z")

</div>

Hi again @Greg_Farrow!

> [@Greg\_Farrow](#):
>
> In older versions, the plugin would prompt for the DataDog URL to use (i.e. the region). But, in this version it does not prompt, so I suspect it is not setting the URL correctly and that is causing the error?

After installing the plugin, do you see a **Configure** option? This should let you configure the URL correctly.

IDE:

 ![Screenshot 2026-07-08 at 20.59.36](https://us1.discourse-cdn.com/cursor1/original/3X/4/d/4da34429007c9dcfc3f112974d5b61f89efc366e.png)

Web:

 ![Screenshot 2026-07-08 at 21.00.56](https://us1.discourse-cdn.com/cursor1/original/3X/5/1/51da1c20146589ca1cb55d2ab3d7aa8cadb886d5.png)

 ![Screenshot 2026-07-08 at 21.01.34](https://us1.discourse-cdn.com/cursor1/original/3X/d/f/df2e8cb4a4dd994085f2c52896b5e65511af0dd3.png)

This was unfortunately not too obvious to me, and probably something we should improve the visibility of! Let me know if you’re still facing issues after the URL is configured.

---

<div class="post-metadata">

**Author:** ![Javier\_Valencia](https://avatars.discourse-cdn.com/v4/letter/j/df788c/32.png) [@Javier\_Valencia](https://forum.cursor.com/u/Javier_Valencia)\
**Post date:** [July 8, 2026, 10:27pm UTC](https://forum.cursor.com/t/unable-to-configure-datadog-mcp-with-an-automation/163816/19 "2026-07-08T22:27:14Z")

</div>

Hey @Colin ! I am also having an issue with the Automations + Datadog.  
Even when I set the Datadog plugin URL it shows as this on the MCP and wont let me connect:  
https://${dd\_mcp\_domain:-not-setup}/v1/mcp?referrer\_ide=cursor-plugin&plugin\_version=0.7.14&toolsets=${dd\_mcp\_toolsets:-core,visualizations}

 ![image](https://us1.discourse-cdn.com/cursor1/original/3X/d/9/d95a5a3015b9ac1ee7db8d24767c264107443540.png)

 ![image](https://us1.discourse-cdn.com/cursor1/original/3X/0/d/0d545894f9978270b9e076e7d576d55f6669d837.png)

---

<div class="post-metadata">

**Author:** ![naveen.narayanan](https://avatars.discourse-cdn.com/v4/letter/n/7ea924/32.png) [@naveen.narayanan](https://forum.cursor.com/u/naveen.narayanan)\
**Post date:** [July 9, 2026, 3:55am UTC](https://forum.cursor.com/t/unable-to-configure-datadog-mcp-with-an-automation/163816/20 "2026-07-09T03:55:14Z")

</div>

Same issue for me as well, getting this error each time with all the same setup as others when running it on cursor automation + cloud.

`Datadog MCP is set up, but it is not working right now`  
`Please run ` **`/ddconfig`** ` to repair the Datadog MCP server`

---

<div class="post-metadata">

**Author:** ![Greg\_Farrow](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/greg_farrow/32/80070_2.png) [@Greg\_Farrow](https://forum.cursor.com/u/Greg_Farrow)\
**Post date:** [July 9, 2026, 7:54am UTC](https://forum.cursor.com/t/unable-to-configure-datadog-mcp-with-an-automation/163816/21 "2026-07-09T07:54:43Z")

</div>

Hi @Colin thanks so much for the reply and the info - following those instructions I was able to successfully re-configure ❤

You are right, the user experience around this functionality is really poor. I particularly struggle with differences between browser-based behaviour being similar but subtly different to the Agent Window behaviour - for example the configure button **is not visible** in the browser…

 ![CleanShot 2026-07-09 at 08.50.13@2x](https://us1.discourse-cdn.com/cursor1/original/3X/4/b/4b1d3197657fd3f35d7c8f69cfb07d290d1bcd5c.png)

Its also very difficult to understand from the UI where configuration is applied only to local, only to cloud, or both. I hope you are able to feed this back t the team so they can improve this.

**TL;DR** - Using the Agent Window, I was able to navigate tot he Plugin page fo Datadog and click on the **greyed out** configure button (it looks like it is disabled) and click on it to select the region.

 ![CleanShot 2026-07-09 at 08.53.21@2x](https://us1.discourse-cdn.com/cursor1/original/3X/7/7/77ae16597b5b623a0b4f1b8eaa8675451914d5db.png)

---

<div class="post-metadata">

**Author:** ![system](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/system/32/99069_2.png) [@system](https://forum.cursor.com/u/system)\
**Post date:** [July 11, 2026, 7:55am UTC](https://forum.cursor.com/t/unable-to-configure-datadog-mcp-with-an-automation/163816/22 "2026-07-11T07:55:30Z")

</div>

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.