New Relic MCP server: 27 tools, in preview

A hosted observability connector still in preview, its three regional endpoints, and the compliance line its own documentation draws.

Last verified 1 September 2026 · from New Relic's own MCP documentation and tool reference

This page is one of 90 in a directory of monitoring and developer tools. Each page checks what an AI coding agent can get out of the tool through its MCP server, the connector that lets the agent query the tool directly.

What is the New Relic MCP server?

It is New Relic's server for the Model Context Protocol. New Relic is an observability platform, so a connected agent reaches telemetry, alerts and the entities that produce them.

Two tools carry the querying. execute_nrql_query runs NRQL directly, and natural_language_to_nrql_query turns a question into NRQL. The pairing is rare. The agent can write the query itself, or it can ask New Relic to write it.

The rest is analysis rather than retrieval. analyze_deployment_impact, analyze_golden_metrics, analyze_threads and generate_user_impact_report return New Relic's own assessment rather than raw rows.

It is strongest in production observability, touches release through change events, and reaches nothing in code review or cost.

For an agent, New Relic answers what production is doing and what changed just before it started. Deployment impact analysis is the tool that links the two. It has no view of the code, so a fix still needs a repository connector.

What can an AI agent do with New Relic?

list_available_new_relic_accounts belongs first. Most tools take an account, and an answer from the wrong one looks exactly like an answer from the right one.

What connecting costs before the first question

A context window is the amount of text a model can hold at once. Twenty-seven tools cost 1,897 to 2,193 tokens on Claude. A group is a heading on this page, not a filter New Relic offers, so the group sizes do not divide the token cost.

The endpoints are a preview program running in three regions, so the surface that registers can change and is not one to budget against.

Encodings: GPT-5.6, GPT-5.5 o200k_base; GPT-4, GPT-3.5 cl100k_base; Claude Haiku 4.5 to Opus 5 count_tokens. Counted from the 27 tool entries in the vendor's own documentation. That is the only public inventory.

The server could not be run for a live tools/list. So no input schemas are available. These figures cover each tool's name and description only. They are a floor, not the figure.

The Claude columns are measured through the API's count_tokens endpoint, with an empty schema per tool. So they cover the same content as the GPT columns. The range there is two tokenizer generations. Haiku 4.5 and Opus 4.6 sit at the low end. Opus 5 and Sonnet 5 sit at the high end. The gap between them is about a fifth.

New Relic MCP server limits: where answers come back incomplete

New Relic's preview product, regional deployments and generated queries set the constraints below.

How to configure New Relic MCP for agents

1. 1

   Check the compliance restriction first

   New Relic states the server must not be used where accounts or data fall under FedRAMP mandates.

2. 2

   Request preview access

   The feature is provided under a preview program, enabled from the Previews and Trials page.

3. 3

   Pick the region

   Token URLs differ: mcp.newrelic.com for the US, mcp.eu.newrelic.com for the EU and mcp.jp.newrelic.com for Japan.

4. 4

   Decide between a user key and OAuth

   A user key is in the NRAK- format; OAuth uses New Relic's pre-configured client and endpoints.

Paste this into your agent’s instructions

Several tools generate an assessment rather than returning data, and one writes the query the answer rests on. Both need naming.

When you answer using New Relic MCP tools, state:
- The account and entity the answer covers.
- The NRQL that ran. If natural_language_to_nrql_query wrote
  it, show the query it produced.
- Whether a claim came from an analyze_ or generate_ tool,
  which return New Relic's assessment rather than raw telemetry.
Never state that data does not exist. State that the query
above returned no results.
Write your answer in ASD-STE100 Simplified Technical
English. Use short sentences with one idea in each.

Do you need the MCP server at all?

Often not. NerdGraph and the NRQL API answer the same questions and are generally available rather than preview.

The connector earns its place on the analysis tools. Deployment impact and golden-metric analysis are New Relic's own assessments, which a raw query does not reproduce.

For an observability connector that is not in preview, Grafana and Datadog both publish generally available servers.

Connect it for investigation while the preview lasts. Use NerdGraph where you need a supported interface.

New Relic MCP server setup

The server is hosted, so nothing is installed. Preview access is requested from the Previews and Trials page in your account.

Authentication is a user key or OAuth. Keys are in the NRAK- format and are created under API keys in the account menu.

claude mcp add --transport http newrelic \
  https://mcp.newrelic.com/mcp \
  --header "Api-Key: NRAK-XXXXXXXXXXXXXXXXXXXXX"

{"mcpServers":{"newrelic":{
  "url":"https://mcp.newrelic.com/mcp",
  "headers":{"Api-Key":"NRAK-XXXXXXXXXXXXXXXXXXXXX"}}}}

[mcp_servers.newrelic]
url = "https://mcp.newrelic.com/mcp"
headers = { "Api-Key" = "NRAK-XXXXXXXXXXXXXXXXXXXXX" }

Every other client

Each block below is the configuration for one client, with the file path and the key that client expects.

{"mcpServers":{"newrelic":{"url":"https://mcp.newrelic.com/mcp",
  "headers":{"Api-Key":"NRAK-XXXXXXXXXXXXXXXXXXXXX"}}}}

{"mcpServers":{"newrelic":{"url":"https://mcp.newrelic.com/mcp",
  "headers":{"Api-Key":"NRAK-XXXXXXXXXXXXXXXXXXXXX"}}}}

{"servers":{"newrelic":{"url":"https://mcp.newrelic.com/mcp",
  "headers":{"Api-Key":"NRAK-XXXXXXXXXXXXXXXXXXXXX"}}}}

{"mcpServers":{"newrelic":{"url":"https://mcp.newrelic.com/mcp",
  "headers":{"Api-Key":"NRAK-XXXXXXXXXXXXXXXXXXXXX"}}}}

# EU
https://mcp.eu.newrelic.com/mcp
# Japan
https://mcp.jp.newrelic.com/mcp

# Authorization URL: https://login.newrelic.com/login
# Token URL (US):    https://mcp.newrelic.com/oauth2/token
# Scopes:            ["openid"]

Read-only access, permissions and security

• FedRAMP accounts are excluded

  New Relic states that use of this preview with FedRAMP-regulated accounts is strictly prohibited.

• It is preview software

  The documentation places it under a preview program governed by New Relic's pre-release policies.

• Telemetry can carry sensitive content

  Log and transaction tools return production data, which reaches the model like any other tool result.

• Every documented tool reads

  Nothing in the 27 creates or deletes a New Relic resource.

Troubleshooting

The endpoint refuses the connection

Preview access has to be enabled. Request it from the Previews and Trials page before configuring a client.

Data appears to be missing

Check the region and the account. There are separate US, EU and Japan deployments, and list_available_new_relic_accounts shows what the key can reach.

A natural-language answer looks wrong

natural_language_to_nrql_query writes the query, and execute_nrql_query runs it. Have the agent print the generated NRQL and read it.

Compliance review blocks the rollout

If any account or data falls under FedRAMP mandates, New Relic's own documentation prohibits using this server.

New Relic MCP server: Reference

What engineers report

New Relic documents 27 tools and runs three regional endpoints, and the figures below come from those docs. Public discussion is small: newrelic/mcp-server has 7 stars, and the two issues below are what engineers have filed against it.

“The MCP tool is great but Agents will run the same query across all accounts for every investigation unless specifically prompted not to do so.”

“Even when I am already logged in, when clicking on the MCP oauth link, I am redirected out to my corporate SSO. After login, the mcp oath flow was lost, and nothing ever goes back to the MCP.”

Tool inventory, regions, authentication and the compliance restriction read from New Relic's own MCP documentation and tool reference on 24 August 2026. Repository facts from the GitHub API on the same date.

Should you connect an agent to New Relic?

Yes. Best for a read-scoped user key in the right region, with generated NRQL printed in every answer.

Strongest fit

New Relic customers outside FedRAMP scope who want an agent to investigate production from the editor.

Main advantage

Both routes to a query: the agent can write NRQL, or ask the platform to write it.

Main weakness

It is a preview, so it sits outside the support and stability guarantees of the rest of the platform.

Operational risk

Low from the tools, which all read. The real risk is the compliance restriction on FedRAMP accounts.

Frequently asked questions