Unable to add New Relic MCP to Automations

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.

image

  • 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
  • Expected behavior is it connects
1 Like

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)?

  • Cursor IDE
  • Cursor CLI
  • Background Agent (GitHub, Slack, Web, Linear)
  • BugBot
  • Somewhere 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!


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!

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.

{ "mcpServers": { "logfire": { "type": "http", "url": " Pydantic Logfire " } } }

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.

I’ll post here when there are updates.

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