Start free →

New Relic

Connecting New Relic lets an agent check latency, alerts, and incidents after a change ships.

Before you start

You need a New Relic User API key, which looks like NRAK-…. Create one in New Relic from the user menu, under API keys. New Relic's own guide is Set up New Relic MCP.

An agent can only reach the accounts and data your own New Relic user can, so the key inherits your role-based access.

Connect it

  1. In SetForth, open your project, then Integrations.
  2. Choose New Relic.
  3. Leave the server URL as https://mcp.newrelic.com/mcp/. For other regions, use https://mcp.eu.newrelic.com/mcp/ or https://mcp.jp.newrelic.com/mcp/.
  4. Add a header named api-key with your User API key as the value.
  5. Choose Connect. SetForth tests the connection and reports the result.

What agents can check

Connecting an observability tool adds two follow-ups:

  • Hold latency budget blocks a merge when latency for the endpoints you name exceeds the budget you set. You choose the percentile and the budget in milliseconds.
  • No new alerts fails a task when its release fires a monitor that was quiet before. You choose which monitors count and the minimum severity.

You set the observation window when you add the follow-up during planning.