mcpField
M
MCP Server for New Relic Change Tracking

MCP Server for New Relic Change Tracking

Local
github.com/yuzujoeDeveloper Tools0Updated 81w ago

About MCP Server for New Relic Change Tracking

An MCP server for recording New Relic Change Tracking events from chat interfaces. It lets teams submit deployment details, though the repository describes it as a practice implementation not recommended for production.

Key features

  1. 01Record deployment events
  2. 02Specify version and entity
  3. 03Add commit and changelog details
  4. 04Set deployment time and user

Use cases

  1. 01Log an application release
  2. 02Attach a commit to a deployment

MCP support

Exposes a tool to MCP clients for creating New Relic deployment change-tracking events. It uses the Model Context Protocol to accept requests from LLMs.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"newrelic-change-tracking": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"build"
]
}
}
}
Run commanddocker run -i --rm build

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
ocibuild

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project README

MCP Server for New Relic Change Tracking

An MCP server that integrates with New Relic Change Tracking via chat interfaces.

Overview

This tool is a server that makes it easy to record and integrate New Relic Change Tracking events through chat-based interfaces. It uses the Model Context Protocol (MCP) to support direct requests from LLMs, making it simple to record application deployment events and other changes.

Note: This repository was created as a practice implementation of an MCP server and is not recommended for production use.

Tools

newrelic_change_tracking_create_deployment
  • Records deployments for the specified entity
inputs
FieldTypeRequiredDescription
versionstringYesVersion of the deployment
namestringYesEntity Name of the deployment
domainTypestringNoDomain Type (eg, APM-APPLICATION BROWSER-APPLICATION MOBILE-APPLICATION)
entityGuidstringNoEntity GUID - defaults to mapped value or environment variable if not provided
descriptionstringNoDescription of the deployment
userstringNoUser who initiated the deployment
commitstringNoCommit hash or identifier
changelogstringNoChangelog details
timestampnumber | stringNoTimestamp - defaults to current time

Setup

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

Usage

Required Environment Variables
  • NEW_RELIC_API_KEY - Specify your New Relic API key (USER KEY).

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

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 New Relic User Key"
      }
    }
  }
}
How to Use

Enter a prompt to record 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 release update
changelog: - Fixed login bug\n- Added new dashboard feature
repository: repository URL
commit: commit hash
domainType: APM-APPLICATION

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.