--- sourceDocument: Australia Enable AI sourceDocumentLink: https://www.servicenow.com/docs/r/australia/intelligent-experiences Release : - australia ft:locale : - en-US ft:publication_title : - Australia Enable AI ft:clusterId : - platai bundleId : - platai workflow : - Platform --- # New Relic MCP server AI agent # New Relic MCP server AI agent {#ariaid-title1} Release version: Australia Updated September 10, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of New Relic MCP server AI agent The New Relic MCP server AI agent integrates with New Relic observability tools to analyze and interpret monitoring data. It enables ServiceNow customers to investigate alerts or respond to queries by leveraging the full suite of New Relic MCP server capabilities. This AI agent is designed to provide actionable insights such as entity health, service dependencies, log analysis, alert history, performance metrics, and change events, enhancing incident investigation and operational awareness. Show full answer Show less ## Key Features * **Alert and Query Analysis:** The agent can investigate alerts or answer direct questions by querying New Relic data using relevant MCP tools. * **Insight Generation:** It can generate detailed reports such as alert insights and user impact reports to support decision-making. * **Configuration Controls:** Administrator-configurable options include allowing third-party AI agents or AI specialists to access this agent, and enabling long-term memory to provide context across multiple interactions. * **Extensive Toolset:** Supports tools for analyzing logs, metrics (golden, Kafka, garbage collection), transactions, entities, and alerts, as well as executing NRQL queries and managing dashboards. * **Role-Based Access:** Access is controlled by specific user roles (e.g., evtmgmtoperator), ensuring secure and appropriate use of the AI agent and data. * **Integration with ServiceNow Workflows:** Can be configured for use in Virtual Agent or ServiceNow Otto panels and supports agentic workflows like analyzing alert impact. ## Practical Benefits for ServiceNow Customers By integrating this AI agent, customers can automate and accelerate incident investigation using New Relic data without manual query building. The agent's ability to contextualize alerts with performance and dependency data supports faster root cause analysis and improved operational efficiency. Role-based access and configurable settings ensure controlled, secure deployment tailored to organizational needs. Additionally, the agent's compatibility with ServiceNow's Virtual Agent and Otto workflows enables seamless AI-driven assistance within existing ITOM AIOps processes. This AI agent queries and interprets observability data from New Relic using the full suite of New Relic MCP server tools. ## Workflow {#itom-obs-new-relic-mcp-server-agent-ai-agent__zsmdlwierhjt} The agent investigates a New Relic alert or answers a direct question using New Relic observability data. 1. Identify what to investigate.The agent uses a provided alert or assesses a conversational question. 2. Generate an alert insights report or query the relevant data in New Relic using the appropriate MCP tools. 3. Return the relevant information, such as entity health, service dependencies, log analysis, alert details and history, performance metrics, and change events. {#itom-obs-new-relic-mcp-server-agent-ai-agent__ol_hcp_qwx_njc} For more information about configuring this AI agent, see [Configure observability agents for ServiceNow Otto](https://www.servicenow.com/docs/access?context=configure-integration-agents-for-now-assist&version=australia&pubname=australia-it-operations-management&ft:locale=en-US). {#itom-obs-new-relic-mcp-server-agent-ai-agent__zsmdlwierhjt__entry__2} | Field | Description | |-|-| | Allow third party to access this AI agent | When enabled, third-party AI agents can use this agent. This value is off (false) by default. This setting is defined in the AI Agent configs \[sn_aia_agent_config\] table on the External discoverable field. | | Allow AI specialists to access this AI agent | When enabled, AI specialists can use this agent. This value is off (false) by default. When set to true, more configuration options for tools become available so that an AI specialist can map inputs and response templates to tool outputs. This setting is defined in the AI Agent configs \[sn_aia_agent_config\] table on the Specialist enabled field. | | Manage long-term memory | When enabled, all previous user interactions are used as context for the LLM. This value is off (false) by default. This setting is defined by the sn_aia.ltm.enable_long_term_memory system property. For more information, see [ServiceNow Otto AI agents reference](https://www.servicenow.com/docs/MUqSU8rHp3ao~q3QEWgHkA "Find more information about user roles, tables, and the different properties that are installed in ServiceNow Otto AI agents."). | | Tools | Model Context Protocol tools : Analyze Deployment Impact : Analyze Entity Logs : Analyze Golden Metrics : Analyze Kafka Metrics : Analyze Threads : Analyze Transactions : Convert Time Period to Epoch : Execute NRQL Query : Generate Alert Insights Report : Generate User Impact Report : Get Dashboard : Get Entity : List Alert Conditions : List Alert Policies : List Available Accounts : List Change Events : List Dashboards : List Entity Error Groups : List Entity Types : List Garbage Collection Metrics : List Recent Issues : List Recent Logs : List Related Entities : List Synthetic Monitors : Natural Language to NRQL : Search Entity by Tag : Search Incidents | | Allowed user roles The specific user roles that can access this AI agent. | evt_mgmt_operator | | Data access roles The specific user identity roles that determine which data the AI agent can access and what actions it can take. | evt_mgmt_operator | | Triggers | Optional. None defined by default. An admin can specify triggers if desired. For more information, see [Add a trigger to an AI agent](https://www.servicenow.com/docs/NXqRJBQV_Vw00FEzklcAJw "In the guided setup for an AI agent, add triggers to run the AI agent automatically when certain conditions are met."). | | Channels | Configure an assistant for Virtual Agent or ServiceNow Otto panel using [Assistant Designer](https://www.servicenow.com/docs/access?context=configure-now-assist-va&version=australia&pubname=australia-conversational-interfaces&ft:locale=en-US). | | Used in agentic workflows | [Analyze alert impact agentic workflow](https://www.servicenow.com/docs/access?context=now-assist-itom-agentic-aia&version=australia&pubname=australia-it-operations-management&ft:locale=en-US) | [Table 1. Configuration] For more information, see [ITOM AIOps](https://www.servicenow.com/docs/access?context=itom-health-landing-page&version=australia&pubname=australia-it-operations-management&ft:locale=en-US).