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.