Overview
What is nr-mcp: New Relic MCP Server?
nr-mcp is an MCP server that enables AI agents to query New Relic data for debugging incidents. It integrates with the New Relic API to run NRQL queries, fetch dashboard data, and analyze logs.
How to use nr-mcp: New Relic MCP Server?
You need a New Relic account with an API key, account ID, and region (US or EU). The recommended method is to run the Docker container: docker run -it --rm -e NEW_RELIC_API_KEY=... -e NEW_RELIC_ACCOUNT_ID=... -e NEW_RELIC_REGION=US danielng123/nr-mcp. Alternatively, install locally and configure your MCP client with the provided JSON. When using AI assistants, include a prompt specifying tasks like NRQL queries, dashboard data, log analysis, and debugging.
Key features of nr-mcp: New Relic MCP Server
- Run NRQL queries against New Relic data
- Fetch dashboard data from New Relic
- Analyze logs for debugging incidents
- Debug incidents with AI assistance
- Supports Docker and local installation
Use cases of nr-mcp: New Relic MCP Server
- Debug application incidents by querying New Relic data via AI assistants
- Run NRQL queries to analyze performance
- Fetch and review dashboard data
- Analyze logs for troubleshooting
- Integrate AI assistants with New Relic observability platform
FAQ from nr-mcp: New Relic MCP Server
What are the prerequisites for using nr-mcp?
A New Relic account with an API key, account ID, and region (US or EU).
What installation methods are available?
Docker is recommended; local installation is also possible. The npx method is not yet supported.
What environment variables are required?
You need to set NEW_RELIC_API_KEY, NEW_RELIC_ACCOUNT_ID, and NEW_RELIC_REGION.
How do I configure my MCP client?
Add the provided JSON configuration to your MCP client setup, either for Docker or local installation, including the environment variables.
What transport does nr-mcp use?
It uses the Stdio transport for MCP communication, as shown in the inspector testing instructions.
