Provides comprehensive integration with New Relic's observability platform, enabling NRQL queries, APM application monitoring, alert and incident management, entity search across infrastructure, synthetics monitoring, deployment tracking, and access to both NerdGraph GraphQL and REST v2 APIs for complete observability stack management.
New Relic MCP Server
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.
Features
📊 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
Installation
Quick Install with Smithery
To install or deploy via Smithery, see the official docs: Deployments, Project Configuration, and smithery.yaml
.
To install New Relic MCP for Claude Desktop automatically via Smithery:
Smithery CLI (recommended)
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
orshttp
transportsInspect a server interactively; run with supplied config
Simple install per client
Examples:
Notes:
This repo includes a minimal
smithery.yaml
withruntime: "typescript"
to align with TypeScript‑first deployments.See the CLI reference for all commands and flags: smithery-ai/cli.
Manual Installation
Add to your Claude Desktop configuration file:
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json
Add to your Cline settings in VS Code:
Add to your Zed configuration file at ~/.config/zed/settings.json
:
Add to your Windsurf Cascade configuration:
Clone the repository:
Install dependencies and build:
Add to your MCP client configuration:
Configuration
Required Environment Variables
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)
Getting Your New Relic Credentials
API Key:
Log in to New Relic
Navigate to API Keys in the left sidebar
Create a new User API Key with appropriate permissions
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.
Usage Examples
Once configured, you can interact with New Relic through your MCP client:
Query Your Data
Monitor Applications
Manage Alerts
Search Infrastructure
Tool Reference
Below is a concise catalog of all MCP tools exposed by this server. See the docs folder for detailed stories/specs.
NerdGraph/GraphQL tools
Tool | Summary |
| Execute NRQL queries (requires
) |
| Execute raw NerdGraph GraphQL queries |
| List APM applications via NerdGraph |
| Search entities (name, type, tags) |
| Fetch details for a GUID |
| List alert policies via NerdGraph |
| List open incidents via NerdGraph |
| Acknowledge an incident (NerdGraph only) |
| List Synthetics monitors |
| Create a browser monitor |
| Fetch account metadata |
REST v2 tools (added in v2.0)
Tool | Summary | Notes |
| Create deployment marker for an APM application | Inputs:
,
; optional
,
,
; supports
|
| List deployments for an app | Supports
,
,
|
| Delete deployment marker | Requires
; User API key must have admin role permissions |
| List APM apps via REST | Filters:
,
,
,
; auto‑paginate |
| List metric names/values for host | Inputs:
,
, optional
; auto‑paginate |
| Get timeslice metric data for host | Inputs:
,
,
; optional
,
,
,
,
; auto‑paginate |
| List hosts for an APM app | Filters:
,
; auto‑paginate |
| List alert policies via REST | Optional
; supports pagination |
| List incidents via REST | Server has no
/
filters; these are applied client‑side; auto‑paginate |
References:
Detailed specs and schemas:
docs/REST_ENDPOINT_TOOL.md
anddocs/rest-tools-stories/*
Troubleshooting
If you're having trouble connecting:
Verify your API key is valid:
curl -X POST https://api.newrelic.com/graphql \ -H 'Content-Type: application/json' \ -H 'API-Key: YOUR_API_KEY' \ -d '{"query":"{ actor { user { email } } }"}'Check that your Account ID is correct
Ensure your API key has the necessary permissions
Check the MCP client logs for detailed error messages
If you receive permission errors:
Verify your API key has the required permissions:
For NRQL queries:
NRQL query
permissionFor APM data:
APM
read permissionsFor alerts:
Alerts
read/write permissions
Create a new API key with broader permissions if needed
Development
Project Structure
Setup Development Environment
Clone the repository:
Install dependencies:
Create a
.env
file:
Build the project:
Development Commands
Testing
The project uses Test-Driven Development (TDD) with:
Vitest for unit testing
Gherkin for BDD testing
Evalite for LLM response validation
Debugging
Use the MCP Inspector to test and debug the server:
See docs/mcp-inspector-setup.md for detailed instructions.
Architecture
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
Contributing
We welcome contributions! Please see our Contributing Guidelines for details.
Development Workflow
Fork the repository
Create a feature branch (
git checkout -b feature/amazing-feature
)Write tests first (TDD approach)
Implement your feature
Ensure all tests pass (
npm test
)Maintain >90% code coverage
Run linting (
npm run lint
)Commit your changes (commits will be auto-formatted)
Push to your branch
Open a Pull Request
Code Style
This project uses:
Biome for linting and formatting
TypeScript with strict mode
2 spaces for indentation
Single quotes for strings
Semicolons always
Documentation
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
Comparisons
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.
Project | Status | Transport(s) | Deployments | APM Apps | Metrics | Alerts | Synthetics | Notes |
This project (newrelic-mcp) | Active | NerdGraph + REST v2 | Create/List/Delete | List (NerdGraph + REST) | Host names + timeslices (REST) | Policies + Incidents (NG + REST) | List/Create (browser) | Comprehensive tests and docs |
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)
Support
License
This project is licensed under the MIT License - see the LICENSE file for details.
Disclaimer
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.
Acknowledgments
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
remote-capable server
The server can be hosted and run remotely because it primarily relies on remote services or has no dependency on the local environment.
Tools
Run NRQL, NerdGraph, and REST v2 operations to query data, manage incidents, create synthetics, and annotate deployments — all from your MCP client.
- Features
- Installation
- Configuration
- Usage Examples
- Tool Reference
- Troubleshooting
- Development
- Contributing
- Documentation
- Comparisons
- Support
- License
- Disclaimer
- Acknowledgments
Related Resources
Related MCP Servers
- AsecurityAlicenseAqualityMCP for working with GraphQL servers.Last updated -2502296MIT License
- -securityFlicense-qualityAn MCP server that enables graph database interactions with Neo4j, allowing users to access and manipulate graph data through natural language commands.Last updated -
- -securityAlicense-qualityA MCP server that exposes GraphQL schema information to LLMs like Claude. This server allows an LLM to explore and understand large GraphQL schemas through a set of specialized tools, without needing to load the whole schema into the contextLast updated -1742MIT License
Nx MCP Serverofficial
-securityAlicense-qualityThe Nx MCP server provides LLMs with comprehensive insights into your monorepo: project dependencies, file relationships, executable tasks, ownership metadata, technology stacks, custom generators, and Nx documentation. This deep context enables LLMs to produce code perfectly aligned with your archiLast updated -39,0841,380MIT License