New Relic MCP Server
About
Run NRQL, NerdGraph, and REST v2 operations to query data, manage incidents, create synthetics, and annotate deployments — all from your MCP client.
Details
- Author
- cloudbring
- Downloads
- 288
- Categories
- Developer Tools, Infrastructure
Jump to
- Execute NRQL queries for aggregate analytics and timeseries.
- Run arbitrary NerdGraph GraphQL queries.
- Search and retrieve detailed entity information.
- List, create, and manage Synthetics browser monitors.
- Triage and acknowledge open incidents by priority.
- Record and list APM deployments with full details.
- Enumerate and filter alert policies.
- Region‑aware REST v2 tools with auto‑pagination.
- Safe delete operations require explicit confirm: true.
Setting up with Highlight
This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:
- Download and install Highlight from highlightai.com/download
- Navigate to the plugins tab and select "Add Custom Plugin"
-
Configure the plugin with the settings below
Plugin Name
New Relic MCP ServerCommand (node, npx, python, etc.)Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.
- Enable "Start Automatically" if you want the plugin to start when Highlight launches
From the repository
Install the server with npx -y newrelic-mcp. Configure it in your MCP client’s JSON by setting NEW_RELIC_API_KEY (required) and optionally NEW_RELIC_ACCOUNT_ID. The default account ID can be overridden per tool call using the target_account_id parameter. The recommended system prompt guides the assistant on which tool to use for each task (e.g., run_nrql_query for aggregate analytics, REST tools for deployments).
Claude Desktop / Cursor
Paste into your MCP client config file to install this server.
{
"mcpServers": {
"new relic mcp server": {
"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"
}
}
}Install
- One‑liner: npx -y newrelic-mcp
Server config (drop-in for most MCP clients)
{
"mcpServers": {
"newrelic": {
"command": "npx",
"args": ["-y", "newrelic-mcp"],
"env": {
"NEW_RELIC_API_KEY": "YOUR_API_KEY",
"NEW_RELIC_ACCOUNT_ID": "YOUR_ACCOUNT_ID"
}
}
}
}
Environment variables
- NEW_RELIC_API_KEY: New Relic User API Key (required) - NEW_RELIC_ACCOUNT_ID: Default account ID (optional; can be provided per tool call)Tools (copy for MCP.so "Tools" section)
- run_nrql_query: Execute NRQL against an account.
- run_nerdgraph_query: Run arbitrary NerdGraph GraphQL.
- search_entities: Search across entities (type, tags, account).
- get_entity_details: Deep detail for any entity GUID (relationships, golden metrics, alert context).
- list_apm_applications: List APM apps via GraphQL.
- list_synthetics_monitors: List Synthetics monitors (filter by type).
- create_browser_monitor: Create a Synthetics Browser monitor.
- list_alert_policies: Enumerate alert policies.
- list_open_incidents: Fetch open incidents (filter by priority).
- acknowledge_incident: Acknowledge a specific incident.
REST v2 (region-aware, auto‑pagination)
- create_deployment - list_deployments_rest - delete_deployment (requires confirm: true) - list_apm_applications_rest - list_metric_names_for_host - get_metric_data_for_host - list_application_hosts - get_account_details: Convenience account infoRecommended System Prompt:
You are an SRE copilot using New Relic via MCP tools. Follow these rules:
1) Choose the right interface:
- Use run_nrql_query for aggregate analytics and timeseries.
- Use run_nerdgraph_query for graph-shaped data and entities/alerts APIs.
- Prefer REST v2 tools for deployments and legacy APM metrics; set region as needed.
2) Always include target_account_id unless a default is configured.
3) For large result sets, enable auto_paginate and surface page info.
4) Be safe: require explicit user confirmation for delete_deployment (confirm=true).
5) For incidents:
- Use list_open_incidents to triage by priority.
- Use acknowledge_incident only after user approval.
6) For synthetics:
- Use create_browser_monitor with name, url, frequency, locations.
7) Return concise summaries with a short “What I did” and “What next” suggestion.
Example Prompts
- “Run NRQL to get requests and error rate for app ‘web’ over the last 30 minutes; include a short analysis.”
- “List open incidents with priority CRITICAL and HIGH; summarize by policy.”
- “Acknowledge incident 1234 with comment ‘false positive after deploy rollback’.”
- “Create a Synthetics Browser monitor named ‘Homepage SLA’ for https://example.com every 5 mins from US_EAST_1 and EU_WEST_1.”
- “Record deployment for application_id 987654 with revision 9f3c2ab; include changelog and user.”
- “List APM applications via REST; filter language=nodejs; auto-paginate across regions US then EU.”
- “For app 987654 host 321, list metric names, then fetch CPU and memory timeslices in the last 30 minutes.”
Testing
- Tested to 90%+ Code Coverage - Behavior defined in Gherkin; evaluated with AI evals testing. - Tool discovery and input schema validation covered. Pagination, error handling, and performance scenarios included.Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.
