New Relic MCP Server
Related Servers
Alternatives to New Relic MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables AI agents to query New Relic observability data, including NRQL queries, entity searches, incident tracking, deployment history, and golden signals, via the Model Context Protocol.10MIT
- FlicenseNot gradedqualityDmaintenanceProvides New Relic observability tools for AI assistants, enabling discovery, data access, alerting, incident response, and performance analytics via natural language queries.-
- FlicenseNot gradedqualityDmaintenanceEnables users to query and manage New Relic account data and features through natural language or specific commands, including NRQL queries, entity search, APM, Synthetics, and alerts management.3-
- FlicenseAqualityDmaintenanceEnables AI agents to access New Relic logs and APM data through the NerdGraph API. It allows users to execute NRQL queries, retrieve application performance metrics, and analyze transaction traces using natural language.61-
- AlicenseBqualityBmaintenanceEnables AI assistants to interact with New Relic monitoring and observability data through programmatic access to New Relic APIs. Supports APM management, NRQL queries, alert policies, synthetic monitoring, dashboards, infrastructure monitoring, and deployment tracking.26281 PyPI6MIT
- AlicenseNot gradedqualityAmaintenanceConnects AI assistants to New Relic with read-only access to NRQL, logs, metrics, traces, alerts, and more. Offers optional, gated write operations with a dry-run and confirmation workflow.34 npmApache 2.0
TDQS
Scored across 52 tools
Most tools target distinct resources with clear CRUD boundaries, but several pairs overlap: get_incidents vs get_alert_violations (the latter also returns incidents), delete_tags_from_entity vs delete_tag_values (delete key vs delete key-value pair), and list_notification_destinations vs list_notification_channels. The detailed descriptions help, but an agent could still misselect between these closely related concepts.
Most tools follow a verb_noun pattern (create_/update_/delete_/list_), but the read-verb choice is inconsistent: list_alert_conditions, list_workflows, and list_muting_rules use 'list' while get_incidents, get_dashboards, and get_synthetic_results use 'get' for equivalent enumeration operations. Deviations like entity_search, decode_entity_guid, and add_widget_to_dashboard further break the convention.
At 52 tools, the set exceeds the 50+ threshold for an extreme mismatch. The tool descriptions are very long (especially add_widget_to_dashboard's rawConfiguration reference), creating heavy context overhead and making reliable tool selection difficult given the many similar list_/get_/create_ tools. Even accounting for New Relic's broad platform, this is too many tools for one server.
The set covers full CRUD for alert policies, NRQL conditions, workflows, muting rules, dashboards, widgets, entities/tags, and service levels, plus NRQL querying and read-only monitoring. Notable gaps: no update tools for notification destinations or channels, no create/update/delete for synthetic monitors, and only NRQL-type alert conditions can be created.