When trying to set up a New Relic MCP connection for automations, I simply get this error that says “connection failed”. I’m able to use the same exact connection settings (URL and api-key header) in Cursor IDE and it works fine.
Bug happens only in Automations
When attempting to connect to New Relic MCP with details like the below, it gives a Connection Failed error
"url": "https://mcp.newrelic.com/mcp/",
"headers": {
"api-key": "NRAK-YOUR-API-KEY-HERE"
}
Steps to reproduce - create a new MCP connection to New Relic for Automations, add a valid api-key header, and attempt to add it to a new automation
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!
I’m also experiencing the same issue for the LogFire MCP. Even through the oauth version, it is not working. It is saying that there is a missing refresh token.
Hey, this is a known issue. MCP connections via Automations are unstable right now. We’re seeing similar reports with other providers like Sentry, Datadog, and LogFire.
The team is aware. There’s no ETA yet, but your reports help us prioritize.
@c2keesey same situation with LogFire, we’re tracking it.
Hey @Kyle_Holgate,
Just checking in — are you still seeing the “fetch failed” error when adding MCP servers to Automations? This was recently addressed, and updating to the latest version should resolve it. Let me know if you’re still running into it!
I’m unable to add the Datadog plugin to Automations for the same reason, and now it just refuses to add the plugin to the Automation. It worked for a couple of days, now the automations refuse to acknwledge adding it. Has there been any fixes or updates on this?
Hey, the original issue in that thread fetch failed / connection failed when adding MCP was fixed back in April. What you’re describing, the plugin worked for a while and now Automation won’t confirm the add, sounds like a different symptom, so let’s treat it as a new case.
To avoid mixing it up with the already closed bug, please start a new thread and include:
Where exactly you’re adding Datadog, in the IDE or in the web dashboard at cursor.com/automations
A screenshot showing the exact text/state, stuck on Installing, an error, or it just doesn’t get added with no message
Your Cursor version
How you’re adding Datadog, via a marketplace plugin or a custom MCP, JSON with url and headers
Roughly when it stopped working
With those details we can link your case to the right issue. A similar symptom, plugin installs but doesn’t show up in the tools list, is already on our radar, but I want to confirm it’s the same thing and not something else.