Add the New Relic MCP server to Claude Desktop

Config last verified Jun 1, 2026

The exact config to run New Relic in Claude Desktop — paste it in, restart, and the tools load.

Prerequisites

Claude Desktop installed.
NEW_RELIC_API_KEY — New Relic User API key (starts with NRAK-) passed in the Api-Key header. Carries account context and inherits the user's role-based permissions.

Setup

1. Open `~/Library/Application Support/Claude/claude_desktop_config.json`

On Windows the file lives at %APPDATA%\Claude\claude_desktop_config.json.

2. Add this configuration

Add to ~/Library/Application Support/Claude/claude_desktop_config.json

~/Library/Application Support/Claude/claude_desktop_config.json

json

{
  "mcpServers": {
    "newrelic": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://mcp.newrelic.com/mcp/"
      ]
    }
  }
}

Heads up

Claude Desktop's config is stdio-only; this bridges the remote server with `mcp-remote`. (Pro/Team plans can use native Connectors instead.)

3. Restart Claude Desktop and confirm the New Relic tools load.

Gotchas

Claude Desktop's config is stdio-only; this bridges the remote server with `mcp-remote`. (Pro/Team plans can use native Connectors instead.)

Claude Desktop reads MCP servers from an "mcpServers" object, but the config file is stdio-only: it cannot dial a remote URL directly. To reach a remote server you bridge it locally by running "npx mcp-remote <url>" as the command. Native remote Connectors exist on paid plans, but not through this config file, so the bridge is the portable path.

← Back to the New Relic MCP server