---
title: "New Relic Ground Truth MCP: review, setup & limitations · Undominated.ai"
canonical: https://undominated.ai/mcp-servers/new-relic/
description: "Connect supported agents to New Relic telemetry and operational tools with account RBAC and OAuth."
---

# New Relic Ground Truth MCP: review, setup & limitations · Undominated.ai

> Connect supported agents to New Relic telemetry and operational tools with account RBAC and OAuth.

[← Explore all mcp servers](/mcp-servers/)

OBSERVABILITY INVESTIGATION / New Relic

# New Relic Ground Truth MCP

Connect supported agents to New Relic telemetry and operational tools with account RBAC and OAuth.

 [See setup guidance ↓](#setup)[Original source ↗](https://docs.newrelic.com/docs/agentic-ai/mcp/overview/)

SOURCE REVIEW

 Reviewed 2026-10-14
 Evidence 2 linked sources
 Publisher New Relic
 Licence Not established
 [Read what was—and wasn’t—checked ↓](#review)

“New Relic Ground Truth”

 [New Relic · upstream description ↗](https://docs.newrelic.com/docs/agentic-ai/mcp/overview/) Our analysis follows below.

01 / THE REASONING

## Why this made the selection.

 - Documents organization-level access controls independently of client setup.
- Regional endpoints and tool-tag filtering make the intended telemetry connection explicit.
- New Relic’s overview calls Ground Truth the MCP layer for operational intelligence, and it says some tools exist only for OAuth and are not available with an API key.
- The setup page says supported clients should use OAuth unless the documentation expressly says otherwise, while Antigravity CLI is the documented API-key exception.

### A good fit for

 - Investigate an alert and bounded NRQL evidence for a deployment.
- Compare affected services and errors before proposing a remediation.
- Using New Relic MCP tools from a supported client that can complete OAuth
- Antigravity CLI only with the API-key method the setup page says is currently supported there

### Weigh up before choosing

 - Core and advanced tool availability depends on account compute entitlements and administrator feature toggles.
- include-tags selects tools; it does not reduce the user account permissions.
- API-key support is client-specific and omits some AI/preview tools; the normal setup uses OAuth.
- Some tools are not available when using an API key.
- An API-key setup is not described as working for supported clients unless the documentation indicates otherwise.
- No licence was stated on these pages, and none was inferred.
- This review did not execute the resource.
- The server was not called.
- A valid API key cannot substitute for OAuth-only tools, and enabling local clients does not enable every integration or preview capability.

02 / THE REVIEW RECORD

## What we actually inspected.

Source review has boundaries. A clear record is more useful than a “safe” badge.

### Material inspected

 - https://docs.newrelic.com/docs/agentic-ai/mcp/overview/
- https://docs.newrelic.com/docs/agentic-ai/mcp/setup/
- Round 2 reread of acquired publisher setup and permission evidence; see immutable wave review.

### Our findings

 - The overview separates organization permissions, feature toggles and account entitlements.
- Setup explicitly warns that tools can act on the account and recommends OAuth except documented exceptions.
- The overview says New Relic Ground Truth gives agents governed access to New Relic operational intelligence through MCP.
- Some tools are only accessible via OAuth and are not available with an API key.
- The setup page says supported clients should be set up with OAuth, and that an API-key setup will not work as described unless expressly indicated. Antigravity CLI is the stated exception: only the API key method is currently supported, and OAuth is not yet available there.
- Organization feature controls separately gate MCP, API-key access and preview tools; some analysis and preview tools require OAuth and are unavailable with API keys.

### Not established by this review

 - Server startup, authentication, live tool execution and security isolation were not tested.
- Published package/container parity with a source revision and hosted implementation internals were not tested.
- The resource was not executed and its tools were not called.
- The server was not called. A source review is not a runtime or security certification.

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

## Connect a server deliberately.

[Upstream setup instructions ↗](https://docs.newrelic.com/docs/agentic-ai/mcp/overview/)
 - Have an administrator grant organization MCP read access and enable the relevant feature controls.
- Choose the US, EU or JP MCP endpoint for the account, then complete the documented client OAuth flow.
- Use include-tags when narrowing the advertised tool groups and retain least-privilege account RBAC.
- Have an administrator check group-level MCP read permission and the applicable feature-control toggles, then use the account's regional OAuth endpoint.

### Before you start

 - A New Relic account with MCP access and a supported OAuth MCP client.
- Node.js only for clients requiring the mcp-remote bridge.

### Documented configuration example

Use the client and authentication context described in the setup guidance. Configuration formats vary between hosts.

 {
 "mcpServers": {
 "newrelic": {
 "type": "http",
 "url": "https://mcp.newrelic.com/mcp/"
 }
 }
} Copy configuration ↗

### Compatibility

A New Relic account with MCP access and a supported OAuth MCP client. · Node.js only for clients requiring the mcp-remote bridge.

### Transports

Streamable HTTP

### Observability investigation

 - Tools act on the user account and can perform operational changes when permitted.
- OAuth documentation lists observability:read, offline and offline_access; account roles remain relevant.

### Cost model

New Relic account and compute entitlements apply; advanced tools require the documented entitlement.

04 / FOLLOW THE EVIDENCE

## The source trail.

Our notes are separate from the original resource. Check upstream before adopting a new version.

 - [Publisher setup, capabilities and operating boundaries ↗](https://docs.newrelic.com/docs/agentic-ai/mcp/overview/) Checked 2026-10-14 https://docs.newrelic.com/docs/agentic-ai/mcp/overview/ Supports: summary, install, configExample, access, limitations, bestFor, review, compatibility, transports
- [Publisher setup, capabilities and operating boundaries ↗](https://docs.newrelic.com/docs/agentic-ai/mcp/setup/) Checked 2026-10-14 https://docs.newrelic.com/docs/agentic-ai/mcp/setup/ Supports: summary, install, configExample, access, limitations, bestFor, review, compatibility, transports

KEEP COMPARING

## Other approaches to consider.

Related by category or shared topics. These are alternatives to inspect, not a measured quality order.

 [### Dynatrace remote MCP ↗ Generate and execute DQL and investigate telemetry through the MCP gateway in a Dynatrace environment.](/mcp-servers/dynatrace-hosted/)

 [AI Tools ↗](/tools/)[Skills ↗](/skills/)[Agents ↗](/agents/)[MCP Servers ↗](/mcp-servers/)[Workflows ↗](/workflows/)

## Continue your investigation

 - [Inspect resource evidence](/tools/)
- [Choose a host](/agents/)
- [Inspect reusable workflows](/skills/)
- [Use Undominated data](/api/)
