New Relic MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NEW_RELIC_REGION | No | New Relic data center region: US (default) or EU (optional) | US |
| NEW_RELIC_API_KEY | Yes | Your New Relic User API Key (required) | |
| NEW_RELIC_ACCOUNT_ID | No | Your New Relic Account ID (optional, can be provided per tool call) |
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 |
|---|---|
| run_nrql_queryA | Execute NRQL queries against New Relic data to analyze metrics and events |
| list_apm_applicationsC | List all APM applications in your New Relic account |
| search_entitiesB | Search for entities in New Relic by name, type, or tags |
| get_entity_detailsB | Get detailed information about a specific entity |
| list_alert_policiesB | List all alert policies in your New Relic account |
| list_open_incidentsB | List all open incidents in your New Relic account |
| acknowledge_incidentB | Acknowledge an open incident |
| list_synthetics_monitorsB | List all Synthetics monitors in your New Relic account |
| create_browser_monitorB | Create a new browser-based Synthetics monitor |
| run_nerdgraph_queryB | Execute a custom NerdGraph GraphQL query |
| create_deploymentC | Create a deployment marker for an APM application (REST v2). |
| list_deployments_restC | List deployments for an APM application (REST v2). |
| delete_deploymentA | Delete a deployment record (REST v2). Requires admin role permissions. |
| list_apm_applications_restC | List APM applications via REST v2. |
| list_metric_names_for_hostC | List metric names and values for a specific application host (REST v2). |
| get_metric_data_for_hostC | Get metric timeslices for metrics on a host (REST v2). |
| list_application_hostsC | List hosts for an APM application (REST v2). |
| get_account_detailsC | Get New Relic account details |
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 18 tools
Most tools have distinct purposes, but the presence of both list_apm_applications and list_apm_applications_rest creates ambiguity as they both list APM applications via different APIs. Similarly, get_metric_data_for_host and list_metric_names_for_host are closely related but distinct. Overall, the set is mostly clear with a few overlapping pairs.
Tool names generally follow a verb_noun pattern, using verbs like acknowledge, create, delete, get, list, run, search. However, inconsistency arises with the 'rest' suffix on some tools (list_apm_applications_rest, list_deployments_rest) while others lack it, and mixing 'get' and 'list' for similar operations. The pattern is mostly consistent with minor deviations.
With 18 tools, the server covers a broad but focused set of New Relic functionalities including incidents, alerts, APM, synthetics, deployments, entities, and queries. The count is well-scoped for a general-purpose MCP server, providing a comprehensive yet manageable tool surface without being overwhelming.
The tool set covers many essential operations but lacks CRUD completeness for several domains. Missing operations include updating alert policies, updating or deleting synthetics monitors, and managing other entity types beyond APM. The powerful query tools (nerdgraph and nrql) can compensate for some gaps, but notable missing CRUD actions will cause agents to reach dead ends.