Skip to main content
Glama
adm-alvin-decruz

New Relic MCP Server

by adm-alvin-decruz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to New Relic MCP Server

No user-submitted related servers found.

    Related Servers

    • newrelic-mcp

      alanhoff
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for New Relic workflows, enabling NRQL queries, NerdGraph access, entity lookup, logs, alerts, dashboards, and service levels.
      898 npm
      4
      MIT

    • New Relic MCP Server

      Ivlad003
      F
      license
      Not graded
      quality
      C
      maintenance
      A Model Context Protocol server that enables Large Language Models like Claude to query New Relic logs and metrics using NRQL queries.
      28
      -

    • NewRelic MCP Server

      ruminaider
      A
      license
      A
      quality
      D
      maintenance
      A comprehensive MCP server providing over 26 tools for querying, monitoring, and analyzing NewRelic data through NRQL queries and entity management. It enables interaction with NewRelic's NerdGraph API for managing alerts, logs, and incidents directly within Claude Code sessions.
      24
      60 npm
      2
      MIT

    • mcp-o11y

      argotdev
      F
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that demonstrates comprehensive observability with Sentry, OpenTelemetry, and Braintrust, providing tools for file, data, and HTTP operations along with real-time status and configuration resources.
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.2/5.0

    Scored across 45 tools

    Disambiguation3/5

    Most tools target distinct resource-action pairs, but get_incidents and get_alert_violations clearly overlap (the latter explicitly includes incidents), and get_dashboards vs search_all_dashboards have murky boundaries since both retrieve the same 200-dashboard limit and both support searching. The descriptions do not effectively differentiate these pairs.

    Naming Consistency4/5

    The vast majority follow a clean verb_noun convention: get_*, list_*, create_*, update_*, delete_*. Minor deviations exist such as entity_search vs search_all_dashboards (noun-first vs verb-first) and decode_entity_guid, but the overall pattern is predictable and readable.

    Tool Count2/5

    45 tools is well into the overcrowded range, especially for a single platform. The surface includes roughly 13 alerting tools, 9 dashboard tools, and 6 entity-tag tools, indicating sub-domains that could be consolidated without losing capability.

    Completeness3/5

    Dashboards, alert policies, NRQL conditions, and entity tags have solid CRUD coverage, and query_nrql acts as a powerful escape hatch. However, notification destinations/channels, workflows, and muting rules all lack update operations, and synthetics and SLOs are read-only, leaving agents with delete-and-recreate workarounds and asymmetric capabilities.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources