← Explore all mcp servers

OBSERVABILITY / New Relic

New Relic MCP

Hosted New Relic server at mcp.newrelic.com exposing entity lookup, alerting, incident response, NRQL and deployment-impact tools over Streamable HTTP. OAuth is the documented default; organisation admins gate access through feature-control toggles and an include-tags header filters which tool families a client receives.

“MCP is a standard way for AI models or agents to receive relevant information (context) about a specific system or environment.”

01 / THE REASONING

Why this made the selection.

  • New Relic documents organisation-level gating for the hosted server: feature-control-manager toggles, an organisation role with permission to read the MCP server, and per-request tool filtering with the include-tags header.
  • The overview documents a natural_language_to_nrql_query tool that turns plain-English questions into NRQL, alongside alert-insight, user-impact and deployment-impact report tools (all OAuth-only).

02 / THE REVIEW RECORD

What we actually inspected.

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

Material inspected

  • New Relic MCP overview docs, read 2026-10-13: supported clients, prerequisites, organisation role and feature-control-manager toggles (MCP Server and Local Clients on by default, others off), OAuth endpoints and scopes, API-key alternative and the OAuth-only tool list.
  • New Relic MCP setup guide, read 2026-10-13: endpoint https://mcp.newrelic.com/mcp/, per-client configuration for Claude Code, Codex, Antigravity CLI, Kiro CLI, Claude Desktop and VS Code, and the include-tags header for filtering tool families.
  • newrelic/mcp-server repository README at pinned revision 73e3cd4505e1320187feaf666b50f3e438f6a060 (still the default-branch head on 2026-10-13): a documentation pointer describing the hosted server and tool categories, with setup delegated to the docs.

Our findings

  • The repository contains no server code or licence file; the served artefact is the hosted endpoint, so the record follows the hosted-successor precedent with repository null.
  • Tool categories include entity and account management, alerting and monitoring, incident response, performance analytics, NRQL data access and deployment-impact analysis.
  • The transport is recorded as Streamable HTTP from the setup guide's claude mcp add --transport http command and its type http blocks; the docs do not name the transport.
  • Corrected 2026-10-13: this record said an administrator must enable the MCP Server and Local Clients toggles before anyone can connect; the overview now says both are enabled by default.
  • configExample is the setup guide's Claude Code ~/.claude.json block. Corrected 2026-10-13: the earlier example merged it with the include-tags header, which the guide shows as a separate fragment.

Not established by this review

  • No OAuth flow or API-key connection was completed and no NRQL query was executed.

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. Check that the New Relic MCP Server and Local Clients toggles are still on in feature control manager (on by default); ask an administrator to enable API Keys or Preview Tools if needed.
  2. Add https://mcp.newrelic.com/mcp/ as an HTTP MCP server in the client and complete the browser OAuth flow.
  3. Optionally set the include-tags header to expose only the tool families the workflow needs.

Before you start

  • A New Relic account with an organisation role that permits MCP read access.
  • Node.js where the client needs the mcp-remote proxy (Claude Desktop).

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, upstreamDescription, access, compatibility, whySelected, limitations, review

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

    Supports: install, configExample, transports, compatibility, limitations

  3. https://github.com/newrelic/mcp-server/blob/73e3cd4505e1320187feaf666b50f3e438f6a060/README.md

    Supports: bestFor, limitations

Evidence & Ask