Skip to main content
Glama
MohamedSawahZC

newrelic-mcp

Related Servers

Alternatives to newrelic-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      B
      maintenance
      Enables natural language access to New Relic for monitoring, querying, and managing dashboards, entities, alerts, and deployments via the Model Context Protocol.
      52
      8
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Enables 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.
      26
      456 PyPI
      6
      MIT
    • F
      license
      A
      quality
      D
      maintenance
      Enables 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.
      6
      1
      -
    • F
      license
      Not graded
      quality
      D
      maintenance
      Provides New Relic observability tools for AI assistants, enabling discovery, data access, alerting, incident response, and performance analytics via natural language queries.
      -
    • A
      license
      Not graded
      quality
      A
      maintenance
      Connects 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.
      16 npm
      Apache 2.0
    • 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
      -

    TDQS

    A3.5/5.0

    Scored across 10 tools

    Disambiguation4/5

    Tools are mostly distinct: nrql_query and nrql_batch_query overlap in purpose but are clearly differentiated by efficiency, and search_entities vs get_entity serve different stages of entity interaction. Other tools each target a unique domain (alerts, incidents, deployments, golden signals, error traces, throughput), leaving little ambiguity.

    Naming Consistency5/5

    All tool names follow a consistent snake_case verb_noun pattern (e.g., get_entity, search_entities, nrql_query). The two nrql tools deviate slightly from get_ but still maintain the same structural style, making the naming predictable and coherent.

    Tool Count5/5

    With 10 tools, the server covers a broad but focused set of New Relic operations—querying, entity discovery, alerting, performance metrics, and deployment info. This is well-scoped for a monitoring MCP server, neither too sparse nor overloaded.

    Completeness4/5

    The surface covers core read-only workflows: flexible NRQL querying, entity lookup, alert/incident awareness, and APM performance details. Minor gaps exist (e.g., no log-specific query but nrql_query handles it, no entity mutation), but for a read-only monitoring server, it covers the essential needs without dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues