Newrelic Change Tracking MCP Server

🚀 New Relic Change Tracking MCP Server

This tool serves as a server that enables easy recording and integration of New Relic Change Tracking events via a chat-based interface. It utilizes the Model Context Protocol (MCP) to support direct requests from LLMs, streamlining the recording of application deployments and other changes.

⚠️ Important Note

This repository is an experimental implementation of an MCP server and is not recommended for use in production environments.

✨ Features

newrelic_change_tracking_create_deployment

• Records deployment information for a specified entity.

Input Parameters

📦 Installation

Docker Build

# Build the image
docker build -t newrelic-change-tracking-mcp-server .

💻 Usage Examples

Required Environment Variables

• NEW_RELIC_API_KEY - Specify your New Relic API key (User Key).

For Claude Desktop MCP users, you can configure it as follows in claude_desktop_config.json:

Docker

{
  "mcpServers": {
    "newrelic-change-tracking": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "NEW_RELIC_API_KEY",
        "newrelic-change-tracking-mcp-server"
      ],
      "env": {
        "NEW_RELIC_API_KEY": "Set your New Relic user key"
      }
    }
  }
}

Usage

Enter a prompt to record an entity change tracking request:

Required Parameters

Record a deployment for <entity name> with <version>

Example:

Record a deployment for my-application with version 1.0.0

Optional Parameters

Record a deployment for <entity name> with <version>
user: <username>
description: <description>
changelog: <changelog>
repository: <repository URL>
commit: <commit hash>
domainType: <domain type>

Example:

Record a deployment for application my-application with version 1.0.0
user: yuzujoe
description: Spring version update
changelog: - Fixed login issues\n- Added new dashboard feature
repository: Repository URL
commit: Commit hash
domainType: APM-APPLICATION