MCP.so
登录

MCP Server for New Relic Change Tracking

@yuzujoe

关于 MCP Server for New Relic Change Tracking

暂无概览

基本信息

分类

开发工具

许可证

MIT

运行时

node

传输方式

stdio

发布者

yuzujoe

配置

使用下面的配置,将此服务器添加到你的 MCP 客户端。

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

工具

未检测到工具

工具是从 README 中自动提取的。维护者可以在 ## Tools 标题下列出工具,即可填充这部分内容。

概览

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.

评论

开发工具 分类下的更多 MCP 服务器