New Relic MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NEW_RELIC_API_KEY | Yes | Your New Relic User API Key (required for NerdGraph API access) | |
| NEW_RELIC_ACCOUNT_ID | Yes | Your New Relic Account ID |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| query-logsA | Execute a custom NRQL query against New Relic logs. Use this for complex queries with specific filtering and aggregations. Example: "SELECT * FROM Log WHERE message LIKE '%error%' SINCE 1 HOUR AGO LIMIT 100" |
| search-logsA | Search New Relic logs with keyword filtering and optional attributes. This is a simpler alternative to query-logs for basic searches. |
| get-recent-logsB | Get the most recent log entries from New Relic. Useful for quickly checking the latest logs without specific filters. |
| query-apmA | Execute a custom NRQL query against New Relic APM data. Use this for complex queries against Transaction, Metric, or other APM event types. Example: "SELECT average(duration) FROM Transaction WHERE appName = 'MyApp' SINCE 1 HOUR AGO" |
| get-apm-metricsB | Get APM performance metrics for applications including response time, throughput, error rate, and Apdex. This provides a comprehensive overview of application performance. |
| get-transaction-tracesA | Get transaction traces from APM, optionally filtering for slow transactions. Useful for identifying performance bottlenecks and slow database queries. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool targets a distinct data source or operation: APM metrics, logs, transaction traces, and custom queries differentiate by data type (APM vs logs) and complexity (query vs search).
All tool names use snake_case with consistent verb-noun pattern: get- for retrievals, query- for custom queries, search- for simple search.
6 tools is well-scoped for a New Relic integration, covering the most common monitoring data types without unnecessary overlap.
Core read operations for APM, logs, and traces are present. Missing listing of apps/entities or alerting tools, but these are not essential for the main use case.