nr-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NEW_RELIC_REGION | Yes | New Relic region (US or EU). Default is US. | US |
| NEW_RELIC_API_KEY | Yes | Your New Relic API key. | |
| 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 | {
"listChanged": true
} |
| logging | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| run-nrql-queryC | Execute a NRQL query and return the results as data points |
| query-logsB | Query New Relic logs by field and value with customizable parameters |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| debug-trace | Debug a specific trace using its trace ID |
| analyze-service | Analyze the performance and health of a specific service |
| explore-errors | Explore and analyze errors in a specific service |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| All New Relic Services | All services from both production and staging environments |
| Production New Relic Services | Services from the production environment |
| Staging New Relic Services | Services from the staging environment |
| New Relic Schema List | All known New Relic table schemas |
TDQS
Scored across 2 tools
The two tools target different data types: 'run-nrql-query' returns generic data points from NRQL queries, while 'query-logs' specifically targets log data with field/value filtering. There's a small risk of confusion since NRQL can also query logs, but the descriptions clearly differentiate the intended use cases.
Both tool names follow a verb_noun pattern with hyphens ('run-nrql-query', 'query-logs'), which is consistent. The only minor inconsistency is that one uses 'run-' prefix while the other uses 'query-' prefix, but both are action verbs and the pattern is maintained.
Two tools feels thin for a server called 'nr-mcp' given New Relic's broad API surface (alerts, dashboards, entities, etc.). While the two tools may serve a focused need, the count is borderline—adequate for a minimal implementation but missing many common operations.
The tool surface is severely incomplete for New Relic's capabilities. There are no tools for managing alerts, dashboards, entities, deployments, or even fetching raw NRQL query results beyond data points. An agent relying on this server will hit dead ends quickly when needing anything beyond logs or basic NRQL queries.