A Model Context Protocol (MCP) server that provides seamless integration with New Relic's observability platform. Query metrics, manage alerts, monitor applications, and interact with your entire observability stack through a simple, unified interface.

Disclaimer: This is an unofficial community project and is not affiliated with, endorsed by, or supported by New Relic, Inc. All trademarks are the property of their respective owners.

• 📊 NRQL Queries - Execute powerful queries to analyze your data
• 🚀 APM Integration - Monitor application performance and health
• 🔔 Alert Management - View and acknowledge alerts and incidents
• 🔍 Entity Search - Discover and inspect entities across your infrastructure
• 📈 Synthetics Monitoring - Manage synthetic monitors and checks
• 🔧 NerdGraph API - Direct access to New Relic's GraphQL API
• 🌐 REST v2 Tools (2.0+) - High‑value REST endpoints for deployments, APM apps, metrics, and alerts

To install or deploy via Smithery, see the official docs: Deployments, Project Configuration, and smithery.yaml Reference.

To install New Relic MCP for Claude Desktop automatically via Smithery:

npx @smithery/cli install newrelic-mcp --client claude

We recommend the Smithery CLI for local development, inspection, and deployment flows. Benefits:

• Unified dev/build/deploy workflow, client‑agnostic
• Dev server with hot‑reload and playground (optional tunnel)
• Build bundles for stdio or shttp transports
• Inspect a server interactively; run with supplied config
• Simple install per client

Examples:

# Hot‑reload dev server
npx @smithery/cli dev src/server.ts --port 8181 --no-open

# Build production bundle (shttp transport)
npx @smithery/cli build src/server.ts --out .smithery/index.cjs --transport shttp

# Inspect a published server
npx @smithery/cli inspect @cloudbring/newrelic-mcp

# Run with config (env via JSON)
npx @smithery/cli run @cloudbring/newrelic-mcp --config '{"NEW_RELIC_API_KEY":"...","NEW_RELIC_ACCOUNT_ID":"..."}'

# Install into a specific client
npx @smithery/cli install newrelic-mcp --client claude

# Open playground
npx @smithery/cli playground --port 3001

Notes:

• This repo includes a minimal smithery.yaml with runtime: "typescript" to align with TypeScript‑first deployments.
• See the CLI reference for all commands and flags: smithery-ai/cli.

{
  "mcpServers": {
    "newrelic": {
      "command": "npx",
      "args": [
        "-y",
        "newrelic-mcp"
      ],
      "env": {
        "NEW_RELIC_API_KEY": "your-api-key-here",
        "NEW_RELIC_ACCOUNT_ID": "your-account-id"
      }
    }
  }
}

{
  "cline.mcpServers": [
    {
      "name": "newrelic",
      "command": "npx",
      "args": ["-y", "newrelic-mcp"],
      "env": {
        "NEW_RELIC_API_KEY": "your-api-key-here",
        "NEW_RELIC_ACCOUNT_ID": "your-account-id"
      }
    }
  ]
}

{
  "language_models": {
    "mcp": {
      "servers": {
        "newrelic": {
          "command": "npx",
          "args": ["-y", "newrelic-mcp"],
          "env": {
            "NEW_RELIC_API_KEY": "your-api-key-here",
            "NEW_RELIC_ACCOUNT_ID": "your-account-id"
          }
        }
      }
    }
  }
}

{
  "mcpServers": {
    "newrelic": {
      "command": "npx",
      "args": ["-y", "newrelic-mcp"],
      "env": {
        "NEW_RELIC_API_KEY": "your-api-key-here",
        "NEW_RELIC_ACCOUNT_ID": "your-account-id"
      }
    }
  }
}

git clone https://github.com/cloudbring/newrelic-mcp.git
cd newrelic-mcp

npm install
npm run build

{
  "mcpServers": {
    "newrelic": {
      "command": "node",
      "args": ["/path/to/newrelic-mcp/dist/server.js"],
      "env": {
        "NEW_RELIC_API_KEY": "your-api-key-here",
        "NEW_RELIC_ACCOUNT_ID": "your-account-id"
      }
    }
  }
}

• NEW_RELIC_API_KEY - Your New Relic User API Key (required)
• NEW_RELIC_ACCOUNT_ID - Your New Relic Account ID (optional, can be provided per tool call)

1. API Key:

   • Log in to New Relic
   • Navigate to API Keys in the left sidebar
   • Create a new User API Key with appropriate permissions

2. Account ID:

   • Find your Account ID in the URL when logged into New Relic
   • Or navigate to Administration → Access management → Accounts

For detailed setup instructions, see docs/new-relic-setup.md.

Once configured, you can interact with New Relic through your MCP client:

"Show me the average response time for my web application over the last hour"
"What are the top 10 slowest database queries today?"
"Display error rate trends for the production environment"

"List all my APM applications and their current status"
"Show me the health of my Node.js services"
"Which applications have active alerts?"

"Show me all open incidents"
"What critical alerts fired in the last 24 hours?"
"Acknowledge incident #12345"

"Find all Redis databases in production"
"Show me entities with high CPU usage"
"List all synthetic monitors and their success rates"

Below is a concise catalog of all MCP tools exposed by this server. See the docs folder for detailed stories/specs.

References:

• Detailed specs and schemas: docs/REST_ENDPOINT_TOOL.md and docs/rest-tools-stories/*

src/
├── server.ts           # Main MCP server implementation
├── client/
│   └── newrelic-client.ts  # New Relic API client
└── tools/
    ├── nrql.ts         # NRQL query tool
    ├── apm.ts          # APM applications tool
    ├── entity.ts       # Entity management tools
    ├── alert.ts        # Alert and incident tools
    ├── synthetics.ts   # Synthetics monitoring tools
    └── nerdgraph.ts    # NerdGraph query tool

1. Clone the repository:

git clone https://github.com/cloudbring/newrelic-mcp.git
cd newrelic-mcp

2. Install dependencies:

npm install

3. Create a .env file:

NEW_RELIC_API_KEY=your-api-key-here
NEW_RELIC_ACCOUNT_ID=your-account-id

4. Build the project:

npm run build

# Start development server with hot reload
npm run dev

# Build for production
npm run build

# Run tests
npm test

# Run tests with coverage
npm run test:coverage

# Run linting
npm run lint

# Format code
npm run format

# Test server startup
npm run test:server

The project uses Test-Driven Development (TDD) with:

• Vitest for unit testing
• Gherkin for BDD testing
• Evalite for LLM response validation

# Run all tests
npm test

# Run with coverage
npm run test:coverage

# Run BDD tests only
npm run test:bdd

# Run integration tests with real API
USE_REAL_ENV=true npm test

Use the MCP Inspector to test and debug the server:

# Run with MCP Inspector
npm run inspect

# Run with development server
npm run inspect:dev

# Run with environment variables
npm run inspect:env

See docs/mcp-inspector-setup.md for detailed instructions.

The server follows a modular architecture with:

• Client Layer: Handles New Relic API communication
• Tools Layer: Implements MCP tool specifications
• Server Layer: Manages MCP protocol and tool routing

Each tool:

• Has a single, focused purpose
• Validates inputs using Zod schemas
• Returns structured, typed responses
• Includes comprehensive error handling

We welcome contributions! Please see our Contributing Guidelines for details.

1. Fork the repository
2. Create a feature branch (git checkout -b feature/amazing-feature)
3. Write tests first (TDD approach)
4. Implement your feature
5. Ensure all tests pass (npm test)
6. Maintain >90% code coverage
7. Run linting (npm run lint)
8. Commit your changes (commits will be auto-formatted)
9. Push to your branch
10. Open a Pull Request

This project uses:

• Biome for linting and formatting
• TypeScript with strict mode
• 2 spaces for indentation
• Single quotes for strings
• Semicolons always

• New Relic Setup Guide - Detailed credential setup
• MCP Inspector Setup - Testing and debugging
• Logging & Telemetry - Test monitoring
• Implementation Details - Architecture deep dive
• REST tools overview - High‑level design for REST v2 tools
• REST tool stories - Per‑tool specs, schemas, and test plans

We researched other public New Relic MCP servers and did not find any actively maintained, feature‑complete alternatives at the time of writing. If you know of one, please open an issue to add it here.

Planned enhancements (based on REST v2 catalog and user demand):

• Alerts: violations and conditions management via REST where available
• Metrics: broader app‑level metrics endpoints (names/data) beyond per‑host
• Additional REST coverage: labels, key transactions, mobile apps (prioritized by feedback)

• 🐛 Report bugs
• 💡 Request features
• 💬 Join discussions
• 📖 Read the docs

This project is licensed under the MIT License - see the LICENSE file for details.

This project is not affiliated with, endorsed by, or supported by New Relic, Inc. It is an independent open-source project that uses New Relic's public APIs.

• Built on the Model Context Protocol specification
• Integrates with New Relic's observability platform APIs
• Inspired by the broader MCP ecosystem

Made with ❤️ by @cloudbring using Cursor and Claude Code