MCP Server for New Relic Change Tracking
Description
# 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…
About
# 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…
Details
- Author
- yuzujoe
- Downloads
- 146
- Categories
- Developer Tools
Jump to
- Records deployment events to New Relic Change Tracking.
- Supports optional fields: description, user, commit, changelog, timestamp.
- Works via chat-based MCP interfaces.
- Simple Docker build and deployment.
- Uses a single tool: newrelic_change_tracking_create_deployment.
Setting up with Highlight
This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:
- Download and install Highlight from highlightai.com/download
- Navigate to the plugins tab and select "Add Custom Plugin"
-
Configure the plugin with the settings below
Plugin Name
MCP Server for New Relic Change TrackingCommand (node, npx, python, etc.)Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.
- Enable "Start Automatically" if you want the plugin to start when Highlight launches
From the repository
Configure the server via Docker with the required NEW_RELIC_API_KEY environment variable. For Claude Desktop, set it in claude_desktop_config.json as a Docker MCP server. Then send prompts such as “Record a deployment for <entity name> with <version>” to log a deployment. Optional fields include user, description, changelog, repository, commit, and domainType.
Claude Desktop / Cursor
Paste into your MCP client config file to install this server.
{
"mcpServers": {
"mcp server for new relic change tracking": {
"newrelic-change-tracking-mcp-server": {
"command": "docker",
"args": [
"build",
"-t",
"newrelic-change-tracking-mcp-server",
"."
]
}
}
}
}McpServers
{
"newrelic-change-tracking-mcp-server": {
"command": "docker",
"args": [
"build",
"-t",
"newrelic-change-tracking-mcp-server",
"."
]
}
}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
| Field | Type | Required | Description |
|-------|------|----------|--------------------------------------------------------------------------------|
| version | string | Yes | Version of the deployment |
| name | string | Yes | Entity Name of the deployment |
| domainType | string | No | Domain Type (eg, APM-APPLICATION BROWSER-APPLICATION MOBILE-APPLICATION) |
| entityGuid | string | No | Entity GUID - defaults to mapped value or environment variable if not provided |
| description | string | No | Description of the deployment |
| user | string | No | User who initiated the deployment |
| commit | string | No | Commit hash or identifier |
| changelog | string | No | Changelog details |
| timestamp | number \| string | No | Timestamp - defaults to current time |
Setup
Docker Build
```shell
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.
