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 API key used for authentication. | |
| NEW_RELIC_ACCOUNT_ID | Yes | Your New Relic account ID used for querying data. |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| query_logsB | Query New Relic logs using NRQL. Args: query: NRQL query string (e.g., "SELECT * FROM Transaction") account_id: New Relic account ID (default from env var) |
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 1 tool
With only one tool, there is no possibility of overlap or misselection; its purpose (querying logs via NRQL) is unambiguous.
The single name query_logs follows a clean verb_noun snake_case convention that would scale predictably if more tools were added.
One tool is far too few for a platform like New Relic, which spans logs, metrics, APM, alerts, and dashboards; the surface feels like a stub rather than a server.
Only log querying is exposed, with no metric queries, APM data, alert/incident retrieval, or account/resource listing, leaving major observability workflows unreachable.