Skip to main content
Glama
deenesjakoruzh
Ivlad003

New Relic MCP Server

by Ivlad003
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

New Relic MCP 서버

NRQL 쿼리를 사용하여 New Relic 로그를 쿼리하는 간단한 모델 컨텍스트 프로토콜(MCP) 서버입니다. 이 서버를 통해 Claude와 같은 대용량 언어 모델(LLM)이 New Relic 데이터와 상호 작용할 수 있습니다.

특징

  • NRQL을 사용하여 New Relic 로그 및 메트릭 쿼리

  • 자세한 오류 로깅

  • Claude Desktop과의 간편한 통합

  • 사람이 읽을 수 있는 출력 형식

  • 구성 가능한 New Relic 계정 ID

Related MCP server: Datadog MCP Server

설치 지침

필수 조건

  • Python 3.10 이상

  • New Relic 계정 및 API 키

  • 클로드 데스크톱 애플리케이션

설치 단계

  1. uv 패키지 관리자를 설치하세요:

지엑스피1

  1. 프로젝트 생성 및 설정:

# Create directory
mkdir newrelic-mcp
cd newrelic-mcp

# Create virtual environment
uv venv

# Activate virtual environment
source .venv/bin/activate  # On Unix/macOS
.venv\Scripts\activate     # On Windows

# Install dependencies
uv pip install "mcp[cli]" httpx

  1. 제공된 코드로 서버 파일 newrelic_logs_server.py 를 만듭니다.

  2. 환경 변수를 구성하세요.

# On Unix/macOS
export NEW_RELIC_API_KEY="your-api-key-here"
export NEW_RELIC_ACCOUNT_ID="your-account-id-here"

# On Windows (CMD)
set NEW_RELIC_API_KEY=your-api-key-here
set NEW_RELIC_ACCOUNT_ID=your-account-id-here

# On Windows (PowerShell)
$env:NEW_RELIC_API_KEY = "your-api-key-here"
$env:NEW_RELIC_ACCOUNT_ID = "your-account-id-here"

Claude 데스크톱 통합

구성 파일을 편집하여 Claude Desktop을 구성하세요.

  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

  • Windows: %APPDATA%\Claude\claude_desktop_config.json

다음 구성을 추가합니다.

{
    "mcpServers": {
        "newrelic": {
            "command": "uv",
            "args": [
                "--directory",
                "/absolute/path/to/newrelic-mcp",
                "run",
                "newrelic_logs_server.py"
            ],
            "env": {
                "NEW_RELIC_API_KEY": "your-api-key-here",
                "NEW_RELIC_ACCOUNT_ID": "your-account-id-here"
            }
        }
    }
}

용법

NRQL 쿼리 예시

  1. 기본 거래 쿼리:

SELECT * FROM Transaction SINCE 1 hour ago

  1. 오류 분석:

SELECT * FROM Transaction WHERE error IS TRUE SINCE 1 hour ago LIMIT 10

  1. 성과 분석:

SELECT average(duration) FROM Transaction FACET name ORDER BY average(duration) DESC LIMIT 5

클로드 프롬프트 예시

클로드에게 다음과 같은 질문을 할 수 있습니다.

  • "지난 1시간 동안의 모든 거래를 보여주세요"

  • "우리의 애플리케이션에 오류가 있나요?"

  • "가장 느린 종료 지점은 어디인가요?"

디버깅

로그 보기

# On macOS/Linux
tail -f ~/Library/Logs/Claude/mcp-server-newrelic.log

# On Windows
type %APPDATA%\Claude\logs\mcp-server-newrelic.log

MCP Inspector로 테스트

다음을 사용하여 서버 기능을 테스트하세요.

npx @modelcontextprotocol/inspector uv run newrelic_logs_server.py

일반적인 문제

  1. 인증 오류:

  • NEW_RELIC_API_KEY가 올바르게 설정되었는지 확인하세요

  • API 키에 올바른 권한이 있는지 확인하세요

  • API 키가 유효한지 확인하세요

  1. 쿼리 오류:

  • NRQL 구문 확인

  • 코드에서 계정 ID가 귀하의 계정과 일치하는지 확인하세요.

  • 쿼리된 데이터가 시간 범위 내에 있는지 확인하세요.

  1. 연결 문제:

  • 네트워크 연결 확인

  • GraphQL 엔드포인트에 액세스할 수 있는지 확인하세요

  • 방화벽이 연결을 차단하지 않는지 확인하세요.

보안 참고 사항

  • API 키를 버전 제어에 커밋하지 마십시오.

  • 민감한 데이터에 환경 변수를 사용하세요

  • 종속성을 최신 상태로 유지하세요

  • 쿼리 패턴 및 액세스 로그 모니터링

개발

로컬 테스트

  1. 환경 변수 설정:

export NEW_RELIC_API_KEY="your-api-key-here"
export NEW_RELIC_ACCOUNT_ID="your-account-id-here"

  1. 서버를 실행합니다:

uv run newrelic_logs_server.py

코드 구조

서버는 다음을 구현합니다.

  • 단일 NRQL 쿼리 도구

  • 구성 가능한 New Relic 계정 ID

  • 포괄적인 오류 처리

  • 자세한 로깅

  • 응답 형식

변경 사항 테스트

  1. 필요에 따라 코드를 수정하세요

  2. MCP Inspector로 테스트

  3. 변경 사항을 적용하려면 Claude Desktop을 다시 시작하세요.

문제 해결 가이드

  1. 서버가 시작되지 않음:

  • Python 버전 확인

  • 모든 종속성이 설치되었는지 확인하세요

  • 가상 환경이 활성화되었는지 확인하세요

  1. 쿼리가 작동하지 않습니다:

  • 자세한 오류 메시지는 로그에서 확인하세요.

  • NRQL 구문 확인

  • 쿼리된 시간 범위 내에 데이터가 있는지 확인하세요.

  1. 클로드가 연결되지 않음:

  • 구성 파일 구문 확인

  • 경로가 절대적인지 확인하세요

  • Claude Desktop을 다시 시작하세요

기여하다

  1. 저장소를 포크하세요

  2. 기능 브랜치 생성

  3. 풀 리퀘스트 제출

특허

이 프로젝트는 MIT 라이선스에 따라 라이선스가 부여되었습니다.

지원하다

문제가 발생하는 경우:

  1. 로그를 확인하세요

  2. 일반적인 문제 섹션을 검토하세요

  3. MCP Inspector로 테스트

  4. GitHub에 문제를 제출하세요

Available Tools

1 tool
query_logsB

Query New Relic logs using NRQL.

Args: query: NRQL query string (e.g., "SELECT * FROM Transaction") account_id: New Relic account ID (default from env var)

ParametersJSON Schema
NameRequiredDescriptionDefault
queryYes
account_idNo1234567

TDQS

B3.1/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full behavioral burden and largely drops it. It never states that this is a read-only operation, whether results are limited or paginated, what time range NRQL defaults to, or what auth/scope is required for the account.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Short and front-loaded with the core action in the first sentence, followed by a compact arg list. The docstring-style 'Args:' block is a bit ceremonial but each line carries parameter information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter query tool with no output schema and no annotations, the description covers the parameters adequately but omits result shape, row/result limits, and pagination behavior. It is minimally viable rather than complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must compensate, and it does: 'query' is explained as an NRQL string with a concrete example, and 'account_id' is described as taking a default from an environment variable. This is meaningful context the bare schema lacks, though the example query targets 'Transaction' rather than a log table, which is slightly off for a log tool.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ('Query New Relic logs using NRQL'), which is unambiguous about what the tool does. There are no sibling tools to differentiate from, so 5 is not reachable, but the purpose itself is crisp.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It says the tool uses NRQL but gives no guidance on when to use it versus other retrieval tools, no prerequisites, and no exclusions. An agent gets the mechanism but not the selection criteria.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool updatev0.1.0
    • First observedquery_logs
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 1 tool

Disambiguation5/5

With only one tool, there is no possibility of overlap or misselection; its purpose (querying logs via NRQL) is unambiguous.

Naming Consistency5/5

The single name query_logs follows a clean verb_noun snake_case convention that would scale predictably if more tools were added.

Tool Count2/5

One tool is far too few for a platform like New Relic, which spans logs, metrics, APM, alerts, and dashboards; the surface feels like a stub rather than a server.

Completeness2/5

Only log querying is exposed, with no metric queries, APM data, alert/incident retrieval, or account/resource listing, leaving major observability workflows unreachable.

Maintenance

ActivityStale
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

  • DevRev MCP Server

    kpsunil97
    F
    license
    C
    quality
    D
    maintenance
    A Model Context Protocol server that enables searching and retrieving information from DevRev using its APIs with Claude.
    2
    3
    -

  • Datadog MCP Server

    brukhabtu
    A
    license
    B
    quality
    Not graded
    maintenance
    A Model Context Protocol server that enables AI assistants to interact with Datadog's observability platform through natural language.
    72
    MIT

  • New Relic MCP Server

    thrashy
    A
    license
    B
    quality
    C
    maintenance
    Enables natural language access to New Relic for monitoring, querying, and managing dashboards, entities, alerts, and deployments via the Model Context Protocol.
    52
    9
    MIT

Appeared in Searches