NewRelic MCP Server
Related Servers
Alternatives to NewRelic MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceMCP server for New Relic workflows, enabling NRQL queries, NerdGraph access, entity lookup, logs, alerts, dashboards, and service levels.712 npm4MIT
- FlicenseCqualityDmaintenanceMCP server allowing AI agents to query New Relic for debugging incidents.2-
- FlicenseNot gradedqualityCmaintenanceProvides comprehensive access to the New Relic observability platform through 55 MCP tools, enabling APM, infrastructure, logs, traces, alerts, dashboards, synthetics, workflows, notifications, service levels, tags, entities, and workloads via a single GraphQL endpoint.-
- AlicenseBqualityCmaintenanceA comprehensive Model Context Protocol (MCP) server for New Relic monitoring, observability, and management operations.45MIT
- AlicenseNot gradedqualityBmaintenanceA read-only MCP server that exposes tools to query Datadog monitors and logs, and AWS CloudWatch Logs, and to group recurring errors by fingerprint. Designed for use with Claude Code to diagnose issues and propose fixes.MIT
- AlicenseBqualityBmaintenanceRun NRQL, NerdGraph, and REST v2 operations to query data, manage incidents, create synthetics, and annotate deployments — all from your MCP client.18712 npm15MIT
TDQS
Scored across 24 tools
Most tools have distinct purposes, such as analyze_deployment_impact for deployment analysis and get_entity for entity retrieval. However, some overlap exists between analyze_entity_logs and query_logs, which both handle logs but with different scopes, potentially causing minor confusion. Overall, descriptions help clarify boundaries, but a few tools like list_recent_logs and query_logs might be ambiguous without careful reading.
Tool names follow a highly consistent verb_noun pattern throughout, such as analyze_deployment_impact, list_alert_conditions, and get_dashboard. All tools use snake_case without deviation, making them predictable and easy to parse. This consistency aids in agent selection and understanding of the toolset's structure.
With 24 tools, the count is slightly high but reasonable for a comprehensive NewRelic monitoring and analytics server. It covers various aspects like alerts, dashboards, entities, logs, and queries, which justifies the breadth. However, it borders on feeling heavy, as some tools might be consolidated or specialized, but it remains well-scoped for the domain.
The toolset provides complete coverage for NewRelic's domain, including CRUD-like operations for entities, dashboards, alerts, and logs, along with advanced analytics and query capabilities. Tools like execute_nrql_query and natural_language_to_nrql_query support custom exploration, while list_related_entities and analyze_golden_metrics offer lifecycle insights. No obvious gaps are present, enabling agents to handle typical workflows without dead ends.