← Explore all 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.

“New Relic Ground Truth”

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.

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 ↗
  1. Have an administrator grant organization MCP read access and enable the relevant feature controls.
  2. Choose the US, EU or JP MCP endpoint for the account, then complete the documented client OAuth flow.
  3. Use include-tags when narrowing the advertised tool groups and retain least-privilege account RBAC.
  4. 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/"
    }
  }
}

04 / FOLLOW THE EVIDENCE

The source trail.

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

  1. https://docs.newrelic.com/docs/agentic-ai/mcp/overview/

    Supports: summary, install, configExample, access, limitations, bestFor, review, compatibility, transports

  2. https://docs.newrelic.com/docs/agentic-ai/mcp/setup/

    Supports: summary, install, configExample, access, limitations, bestFor, review, compatibility, transports

Evidence & Ask