Skip to content
New Relic MCP Server

New Relic MCP Server

new-relicobservabilitynrqlapmalertingincident-responsetelemetry

Summary

New Relic's official hosted MCP server — query telemetry with NRQL or natural language, investigate alerts and incidents, and assess deployment impact from your agent.

Features

  • Run NRQL queries and natural-language questions against your telemetry
  • Entity lookup and account management
  • Alert policies, incident management and recent-issues retrieval
  • Change tracking with deployment impact assessment
  • Golden metrics, logs and thread analysis for performance work
  • Hosted endpoints in US, EU and Japan regions

Installation

Set up this MCP server in your favorite AI agent — copy a ready-made configuration below.

Any MCP-compatible agent

Most agents (Claude, Cursor, Windsurf, VS Code, and more) read a standard mcpServers configuration.

  1. Open your agent's MCP configuration file.
  2. Merge the snippet below into it.
  3. Restart the agent — the "New Relic MCP Server" tools will be available.
{
  "mcpServers": {
    "newrelic-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.newrelic.com/mcp/",
        "--transport",
        "http",
        "--header",
        "api-key: NRAK-xxxx"
      ]
    }
  }
}

Description

New Relic's official MCP server is a hosted endpoint that puts an observability account behind the Model Context Protocol, so an agent can ask questions of live telemetry instead of you translating them into NRQL by hand.

Tools are grouped into six areas: entity and account management (entity lookup, account operations), alerting and monitoring (alert policies, incident management, recent issues), incident response (change tracking, error and alert analysis), performance analytics (golden metrics, logs, thread analysis), data access (NRQL queries plus natural-language querying), and advanced analysis (deployment impact assessment, entity log analysis).

Because it is hosted rather than a local process, setup is a URL and a credential. Two auth paths are supported: a User API key (the NRAK- prefixed keys from the API keys page) passed as an Api-Key header, or OAuth 2.0 against https://login.newrelic.com/login with regional token endpoints. Endpoints are region-specific — https://mcp.newrelic.com/mcp/ for the US, https://mcp.eu.newrelic.com/mcp/ for the EU and https://mcp.jp.newrelic.com/mcp/ for Japan — and you must use the one matching your data region.

Supported clients per New Relic's documentation: Claude Code, Claude Desktop, VS Code, Windsurf, Gemini CLI and Kiro CLI. Claude Code and VS Code speak HTTP transport natively; Claude Desktop goes through mcp-remote.

Two caveats worth reading before deploying: the server is in preview, and New Relic states it is prohibited for workloads under FedRAMP compliance mandates.

Best for SREs and on-call engineers who want an agent that can pull the incident timeline, correlate a regression to a deployment and write the NRQL, rather than a dashboard you have to drive yourself.

Related MCP Servers

New

Postman's official MCP server — reach your workspaces, collections, specs and environments from Claude Code, Cursor, VS Code or Copilot, in four tool tiers.

Developer Tools
New

Drive live Jupyter notebooks from an agent — read and edit cells, execute code, see rich outputs, and run against local JupyterLab or a cloud sandbox.

Developer Tools

MCP: deja-vu

by Vladislav Shulcz

New

Indexes the coding-agent sessions already sitting on your disk — months of history from before you installed it — and serves them back over MCP. 3.5 GB searched in ~1.5 ms, no LLM, no embeddings.

Developer ToolsDatabases & Data
1 views
New

Microsoft's official MCP server for Azure DevOps - work items, repos, pipelines, wikis, test plans and iterations, reachable from any MCP client in plain language.

Developer Tools
1 views
Browse all MCP servers →