MCP Server for New Relic Change Tracking

Name: MCP Server for New Relic Change Tracking
Author: yuzujoe

@yuzujoe

Repository

About MCP Server for New Relic Change Tracking

No overview available yet

Basic information

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "newrelic-change-tracking-mcp-server": {
      "command": "docker",
      "args": [
        "build",
        "-t",
        "newrelic-change-tracking-mcp-server",
        "."
      ]
    }
  }
}

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is MCP Server for New Relic Change Tracking?

It is a Model Context Protocol (MCP) server that records New Relic Change Tracking events through chat interfaces. Designed for developers and operators who want to log deployment events from conversational AI tools, it uses the newrelic_change_tracking_create_deployment tool to create deployment records in New Relic.

How to use MCP Server for New Relic Change Tracking?

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 with ” to log a deployment. Optional fields include user, description, changelog, repository, commit, and domainType.

Key features of MCP Server for New Relic Change Tracking

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.

Use cases of MCP Server for New Relic Change Tracking

Log application deployments from a conversational assistant.
Record release events without leaving the chat environment.
Track changes with version, entity name, and optional metadata.
Automate deployment notifications in New Relic from CI/CD pipelines via MCP.

FAQ from MCP Server for New Relic Change Tracking

What does this server do?

It creates deployment change tracking events in New Relic based on user prompts through an MCP‑compatible chat interface.

How do I set it up?

You need Docker and a New Relic API (User) key. Build the Docker image, then configure your MCP client (e.g., Claude Desktop) with the NEW_RELIC_API_KEY environment variable.

Is this production‑ready?

No. The repository is explicitly described as a practice implementation and is not recommended for production use.

What fields are required to record a deployment?

version (string) and name (entity name) are required. All other inputs (domainType, entityGuid, description, user, commit, changelog, timestamp) are optional.

What authentication does it use?

It requires a New Relic User Key passed via the NEW_RELIC_API_KEY environment variable. No other authentication or transport is documented.

Comments

More Developer Tools MCP servers

Unity MCP (Server + Plugin)

IvanMurzak

AI Skills, MCP Tools, and CLI for Unity Engine. Full AI develop and test loop. Use cli for quick setup. Efficient token usage, advanced tools. Any C# method may be turned into a tool by a single line. Works with Claude Code, Gemini, Copilot, Cursor and any other absolutely for fr

3.5K