New Relic MCP Server

Overview

New Relic MCP Server is a powerful Model Context Protocol (MCP) server that enables AI assistants and language models to interact directly with New Relic services. Built with Python, this MCP server provides a standardized interface for AI-powered monitoring operations, making it easy to integrate New Relic capabilities into your AI workflow.

The Model Context Protocol (MCP) is an open standard that allows AI models to securely connect to external data sources and tools. New Relic MCP Server implements this protocol to provide seamless monitoring integration, enabling AI assistants like Claude, GPT, and other LLMs to perform complex operations through natural language commands.

Whether you're building AI-powered applications, automating monitoring workflows, or creating intelligent chatbots, New Relic MCP Server provides the bridge between your AI assistant and New Relic services. With its comprehensive API coverage and robust error handling, this server is designed for both development and production environments.

As the AI ecosystem continues to evolve, MCP servers like New Relic MCP Server are becoming essential tools for developers who want to leverage the full power of large language models. By providing structured access to New Relic APIs, this server eliminates the need for custom integration code and reduces development time significantly. For more MCP options, explore our complete MCP Servers directory.

Installation

Getting started with New Relic MCP Server is straightforward. Follow these steps to install and configure the server for your MCP-compatible client.

Prerequisites

• Node.js 18+ or Python 3.10+ (depending on the implementation)
• An MCP-compatible client (Claude Desktop, Cursor, VS Code with MCP extension, etc.)
• New Relic account and API credentials
• npm or pip package manager

Quick Install

Install New Relic MCP Server using npm (for TypeScript/JavaScript implementations):

npx -y new-relic-monitoring-mcp init

Or using pip (for Python implementations):

pip install new-relic-monitoring-mcp

Claude Desktop Configuration

Add the following to your Claude Desktop configuration file (claude_desktop_config.json):

{
  "mcpServers": {
    "new-relic-monitoring-mcp": {
      "command": "npx",
      "args": ["-y", "new-relic-monitoring-mcp"],
      "env": {
        "API_KEY": "your-api-key-here"
      }
    }
  }
}

Cursor IDE Configuration

For Cursor IDE, add the MCP server configuration in Settings → MCP Servers:

{
  "name": "New Relic MCP Server",
  "command": "npx",
  "args": ["-y", "new-relic-monitoring-mcp"],
  "env": {
    "API_KEY": "your-api-key-here"
  }
}

VS Code Configuration

If you're using VS Code with an MCP extension, add the server to your .vscode/settings.json:

{
  "mcp.servers": {
    "new-relic-monitoring-mcp": {
      "command": "npx",
      "args": ["-y", "new-relic-monitoring-mcp"],
      "env": {
        "API_KEY": "your-api-key-here"
      }
    }
  }
}

Configuration

Proper configuration is essential for getting the most out of New Relic MCP Server. Here's a comprehensive guide to all available configuration options.

Environment Variables

Advanced Configuration

For production deployments, you can use a configuration file to manage complex settings:

{
  "server": {
    "port": 3000,
    "host": "localhost",
    "cors": true
  },
  "auth": {
    "type": "api_key",
    "key": "$API_KEY"
  },
  "logging": {
    "level": "info",
    "format": "json",
    "file": "/var/log/new-relic-monitoring-mcp.log"
  },
  "rate_limiting": {
    "enabled": true,
    "max_requests": 100,
    "window_ms": 60000
  }
}

Security Best Practices

When deploying New Relic MCP Server in production, follow these security guidelines:

• Never hardcode API keys in configuration files — use environment variables or secret managers
• Enable rate limiting to prevent abuse
• Use HTTPS for all communications
• Regularly rotate API credentials
• Monitor access logs for suspicious activity
• Consider using a service like HashiCorp Vault MCP for secrets management

API Reference

New Relic MCP Server exposes the following tools and resources through the Model Context Protocol:

Available Tools

The server provides these MCP tools that AI assistants can use:

MCP Resources

The server also exposes these MCP resources for context:

• config://settings — Current server configuration
• status://health — Server health and connectivity status
• docs://api — API documentation and usage examples
• metrics://usage — Usage statistics and quotas

Example Usage

Here's how an AI assistant might interact with New Relic MCP Server:

// List all available resources
await mcp.callTool("new-relic-monitoring-mcp", "list_resources", {
  filter: "active",
  limit: 50
});

// Get a specific resource
await mcp.callTool("new-relic-monitoring-mcp", "get_resource", {
  resource_id: "res_123abc",
  fields: ["name", "status", "config"]
});

// Create a new resource
await mcp.callTool("new-relic-monitoring-mcp", "create_resource", {
  name: "my-new-resource",
  config: { region: "us-east-1", tier: "standard" }
});

Use Cases

New Relic MCP Server enables a wide range of monitoring automation scenarios. Here are some popular use cases:

1. Automated Monitoring Management

Use AI assistants to manage New Relic resources through natural language. Simply describe what you need, and the AI will handle the API calls, error handling, and response formatting. This is particularly useful for teams that want to reduce the learning curve for new monitoring tools. Check out other AI Agents that can leverage this MCP server.

2. Intelligent Monitoring and Alerting

Combine New Relic MCP Server with monitoring tools to create intelligent alerting systems. The AI assistant can analyze metrics, identify anomalies, and suggest remediation steps based on historical data and best practices.

3. DevOps Automation

Integrate New Relic MCP Server into your CI/CD pipeline to automate monitoring tasks. The MCP server can handle resource provisioning, configuration updates, and health checks as part of your deployment workflow. For CI/CD integration, consider pairing with Grafana MCP Server.

4. Data Analysis and Reporting

Leverage AI assistants to query New Relic data and generate reports. The natural language interface makes it easy for non-technical users to access complex monitoring insights without writing code.

5. Multi-Service Orchestration

Combine New Relic MCP Server with other MCP servers to orchestrate complex workflows across multiple services. For example, you might use it alongside Prometheus MCP Server or Datadog MCP Server to build comprehensive automation pipelines.

6. Team Onboarding and Knowledge Sharing

New team members can use AI assistants with New Relic MCP Server to explore and understand your New Relic infrastructure. The natural language interface reduces the learning curve and provides contextual help for common tasks.

Troubleshooting

Here are solutions to common issues when working with New Relic MCP Server:

Connection Issues

Problem: The MCP client cannot connect to New Relic MCP Server.

Solutions:

• Verify your API key is correctly set in environment variables
• Check network connectivity to the New Relic API endpoints
• Ensure the server process is running and accessible
• Review firewall rules that might block outbound connections
• Try increasing the timeout value in your configuration

Authentication Errors

Problem: Receiving 401 or 403 errors when making API calls.

Solutions:

• Regenerate your API key from the New Relic dashboard
• Verify the API key has the necessary permissions and scopes
• Check if the API key has expired or been revoked
• Ensure you're using the correct authentication method (API key vs. OAuth)

Rate Limiting

Problem: Receiving 429 (Too Many Requests) errors.

Solutions:

• Implement exponential backoff in your retry logic
• Reduce the frequency of API calls
• Consider upgrading your New Relic plan for higher rate limits
• Cache frequently accessed data to reduce API calls

Performance Issues

Problem: Slow response times from the MCP server.

Solutions:

• Enable caching with an appropriate TTL value
• Use pagination for large result sets
• Optimize your queries to request only necessary fields
• Consider deploying the server closer to the New Relic API endpoints

Version Compatibility

Problem: The server doesn't work with your MCP client version.

Solutions:

• Update to the latest version of New Relic MCP Server: npm update new-relic-monitoring-mcp
• Check the compatibility matrix in the project documentation
• Ensure your MCP client supports the protocol version used by this server

Frequently Asked Questions

What is New Relic MCP Server?

New Relic MCP Server is a Model Context Protocol (MCP) server that enables AI assistants to interact with New Relic services. It provides a standardized interface for monitoring operations, allowing language models like Claude and GPT to perform complex tasks through natural language commands.

Is New Relic MCP Server free to use?

New Relic MCP Server is open source and free to use. However, you'll need a New Relic account and valid API credentials to access the underlying services. Some New Relic features may require a paid subscription.

Which AI clients support New Relic MCP Server?

New Relic MCP Server works with any MCP-compatible client, including Claude Desktop, Cursor IDE, VS Code with MCP extensions, Continue, and other tools that implement the Model Context Protocol. The server is client-agnostic and follows the standard MCP specification.

How secure is New Relic MCP Server?

New Relic MCP Server follows security best practices including encrypted communications, credential management via environment variables, and access logging. API keys are never stored in plain text, and all data transmission uses TLS encryption. We recommend following the security guidelines in the Configuration section above.

Can I use New Relic MCP Server in production?

Yes, New Relic MCP Server is designed for production use. It includes error handling, retry logic, rate limiting, and logging capabilities suitable for production environments. We recommend following the advanced configuration guide for production deployments.

How do I contribute to New Relic MCP Server?

New Relic MCP Server is open source and welcomes contributions. Visit the GitHub repository to file issues, submit pull requests, or contribute to the documentation.

What's the difference between New Relic MCP Server and other MCP servers?

New Relic MCP Server is specifically designed for New Relic integration, providing deep API coverage and monitoring-specific features. While other MCP servers may offer similar capabilities for different platforms, New Relic MCP Server provides the most comprehensive integration with New Relic services. Browse our MCP Servers directory to compare options.

Does New Relic MCP Server support streaming responses?

Yes, New Relic MCP Server supports both streaming and non-streaming response modes. Streaming is particularly useful for long-running operations or real-time data monitoring. Configure streaming in your MCP client settings for optimal performance.

How often is New Relic MCP Server updated?

The New Relic MCP Server team regularly releases updates to support new New Relic API features, fix bugs, and improve performance. Check the GitHub releases page for the latest version and changelog.

Where can I get help with New Relic MCP Server?

You can get help through several channels: the GitHub repository for bug reports and feature requests, community forums for discussions, and our blog for tutorials and guides.

Related Resources

Explore more tools and resources to enhance your AI workflow:

• Grafana MCP Server
• Prometheus MCP Server
• Datadog MCP Server
• Sentry MCP Server
• AI Agents Directory