> For the complete documentation index, see [llms.txt](https://docs.ilert.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ilert.com/ai-and-agents/mcp/external/new-relic.md).

# New Relic

Connect an agent to New Relic's MCP server for entities, NRQL queries, alerts and logs, using a User API key.

New Relic hosts its own MCP server, which gives an agent access to your New Relic entities, NRQL queries, alerts and logs. It authenticates with a New Relic API key sent in the `Api-Key` header — ilert pre-fills that header for you.

#### Prerequisites

* A New Relic account and a User API key, created as described in New Relic's [Setup guide](https://docs.newrelic.com/docs/agentic-ai/mcp/setup/)
* The data-centre region your account lives in (US or EU)

The endpoint is fixed per region and derived from your selection, so there is no URL field:

<table><thead><tr><th width="243.15625">Region</th><th>MCP endpoint</th></tr></thead><tbody><tr><td>US (mcp.newrelic.com)</td><td><code>https://mcp.newrelic.com/mcp/</code></td></tr><tr><td>EU (mcp.eu.newrelic.com)</td><td><code>https://mcp.eu.newrelic.com/mcp/</code></td></tr></tbody></table>

#### Create the connector

{% stepper %}
{% step %}
Navigate to **Connectors** in the ilert navigation menu
{% endstep %}

{% step %}
Scroll to the **MCP Servers** section and click **Connect** on the **New Relic MCP Server** card
{% endstep %}

{% step %}
Fill in the dialog:

* **Name:** a name for the connector (defaults to "New Relic MCP")
* **New Relic region:** your account's region (defaults to US)
* **API key:** the New Relic User API key

<figure><img src="https://3394882078-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M76ygPnS4HUcFSX8ulm%2Fuploads%2Fgit-blob-2285bfe21dc3eb8931896c652b09f4da86fb7a14%2Fnew-relic-mcp-create-dialog.png?alt=media" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
Click **Test connection** to confirm the key works and the tools can be listed
{% endstep %}

{% step %}
Click **Save**
{% endstep %}
{% endstepper %}

{% hint style="info" %}
The region must match the account the API key belongs to. An EU account key used against the US endpoint fails authentication.
{% endhint %}

#### Connect MCP server with agent

To connect New Relic with your AI SRE agent:

{% stepper %}
{% step %}
Navigate to **Agents** in the ilert navigation menu
{% endstep %}

{% step %}
Open the agent detail view for the agent you want to configure
{% endstep %}

{% step %}
Go to the **Tools** tab
{% endstep %}

{% step %}
Under the **External MCP Servers** section, locate the **New Relic MCP Server** row
{% endstep %}

{% step %}
Click **Connect**
{% endstep %}

{% step %}
In the dialog, choose the New Relic connector you created under **Select connector** (or create one here — the same region and API key fields appear)
{% endstep %}

{% step %}
Click **Add**
{% endstep %}

{% step %}
Expand the server card to load its tools and enable the ones the agent may use, then save the agent
{% endstep %}
{% endstepper %}

The New Relic integration is now connected and ready to use for root cause analysis.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.ilert.com/ai-and-agents/mcp/external/new-relic.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.