New Relic MCP Server

What New Relic MCP Server MCP server does

New Relic MCP Server MCP server exposes selected New Relic observability and administration functions to MCP-compatible AI clients. It covers NRQL queries, logs, metrics, traces, errors, entities, alerts, incidents, dashboards, synthetics, workloads, and service levels. The server sends requests through New Relic's NerdGraph API rather than exposing arbitrary GraphQL operations.

Access is read-only by default. Mutating operations are unavailable unless their feature gates are enabled, and enabled writes must pass through a dry run, a confirmation phrase, and a post-write readback. New Relic credentials are kept in the server configuration and are not accepted as tool arguments.

How it works

The project supports two transports. Local clients can launch the process over stdio, while deployments can expose a sessionless Streamable HTTP endpoint at /mcp. The HTTP mode also provides /healthz and /readyz probes. Diagnostics and logs use stderr in stdio mode so stdout remains available for MCP frames.

A fixed, documented operation set limits which NerdGraph requests the server can make. Toolsets for major capability areas can be enabled independently. The doctor command checks configuration, credentials, region, accessible accounts, and a bounded schema query for each enabled toolset without performing mutations. The tools command reports enabled toolsets and safety gates.

Prometheus metrics are available from a /metrics endpoint. They include per-tool call counts, duration, and outcomes, along with upstream request, queue, retry, rate-limit, and cache measurements.

Setup and configuration

New Relic MCP Server MCP server requires Node.js 22.7.5 or later; Node.js 24 LTS is recommended for production. A New Relic user key with permissions matching the enabled toolsets is also required. Supported New Relic deployments use the US or EU endpoint, with a verified JP compatibility endpoint deployment also documented.

For a local installation, install the npm package globally or have an MCP client invoke a pinned package version with npx. Set NEW_RELIC_API_KEY and NEW_RELIC_REGION, then run the doctor command before starting the stdio server. HTTP deployments can read the New Relic key and MCP bearer token from files. Non-loopback HTTP requires bearer or OIDC authentication, a Host allowlist, TLS at the reverse proxy, and an Origin allowlist for browser clients.

Claude Code, Claude Desktop, Cursor, and Codex configuration examples are provided. Docker Compose and Helm are supported deployment options, and the project includes a client-installable MCPB bundle workflow.

Limitations and notes

New Relic limits each user to 25 concurrent NerdGraph requests across that user's keys. The server defaults to 20 total requests and five complex NRQL queries, so deployments should review the documented scaling guidance before adding replicas. Ordinary HTTP calls are sessionless; cancellation across multiple replicas additionally requires deterministic load-balancer affinity.

The server does not provide arbitrary GraphQL access and does not pass New Relic keys through tool calls. Writes should be tested against a non-production New Relic account before enabling them. The repository is Apache-2.0 licensed, but the README states that published registry, npm, container, and MCPB artifacts depend on maintainer credentials.