New Relic Ground Truth

Ground Truth is New Relic's operational intelligence layer. Model Context Protocol (MCP) tools help organize your observability data so that AI agents can better understand your tech stack.

MCP is a standard way for AI models or agents to receive relevant information (context) about a specific system or environment. This context can help the AI understand the current situation, perform tasks more accurately, and provide more useful responses. The MCP server allows supported AI agent(s) to call certain tools that may help you query, investigate, or act on New Relic data in natural language. This in turn can help speed incident response and performance analysis.

Potential benefits

The MCP server offers practical benefits for engineers and operations teams in the following ways:

• Direct integration: Access New Relic's MCP tools directly from your supported development environment. This avoids switching between different AI tools.
• Faster troubleshooting: Use MCP to help quickly find and fix issues from your observability data, analyze error logs, and determine probable causes with AI-provided insights.
• Operational queries: Ask your AI agent to check alert statuses, generate alert event reports, or analyze how deployments affect your systems.
• Simple data queries: Formulate questions in plain English, and the server converts them into New Relic Query Language (NRQL) to get results, even if you are not familiar with NRQL.

Supported AI development tools

New Relic MCP works with these AI development environments (supported MCP clients):

• Claude Code: Command-line interface for Claude
• Antigravity CLI: Command-line interface for Antigravity
• Kiro CLI: Command-line interface for Kiro
• Claude Desktop: Desktop application for interactive AI development
• VS Code: Integrated development environment with MCP support

Each environment offers unique advantages depending on your workflow preferences. Refer to our setup guide for MCP client-specific configuration instructions.

Prerequisites

To use New Relic MCP, you need:

• A New Relic account (MCP is available to all accounts: all data and CCU users can access core tools, aCCU users can access all tools including advanced tools)
• Node.js installed (required for some authentication methods)
• One of the supported MCP clients mentioned earlier installed

Organization access

Before you can connect, a New Relic administrator must perform the following:

Group membership and roles

You must be a member of a group assigned either a default organizational role (Organization Read Only, Organization Manager, or Organization Product Admin) or a custom organization-scoped role with permission to read the MCP server. If your group does not have the required permission, contact an administrator with the Organization Manager or Authentication Domain Manager role to have it granted.

Feature control manager

Your organization administrator must enable MCP access via feature control manager. The following toggles control MCP access. New Relic MCP Server and Local Clients are enabled by default. All other sub-toggles are disabled by default and can be enabled by your New Relic administrator as needed.

• New Relic MCP Server: Required for MCP set up. Main toggle that must be on for any MCP access to work.
• Local Clients: Required for local client connections (Claude Code, Claude Desktop, VS Code, Kiro).
• API Keys: Required for API key connections, including automated scripts.
• Preview Tools: Required if you want to access MCP preview (non-GA) tools.
• Atlassian: Required for Atlassian integration
• AWS: Required for AWS integration

Authentication options

• OAuth (recommended): New Relic provides pre-configured OAuth endpoints:

  • Client ID: pUWGgnjsQ0bydqCbavTPpw==
  • Authorization URL: https://oauth2.service.newrelic.com/oauth2/auth
  • Token URL: https://oauth2.service.newrelic.com/oauth2/token
  • Scopes: ["observability:read", "offline", "offline_access"]

• User API Key: Note that some MCP tools are only accessible via OAuth.

  1. Log in to New Relic.
  2. Select user menu -> API keys.
  3. Create new user key or copy existing one.
  4. Key format: NRAK-XXXXXXXXXXXXXXXXXXXXX.

Next steps

Ready to connect your supported MCP clients to New Relic observability data?

1. Choose your supported MCP client from our supported environments.
2. Follow our setup guide for step-by-step configuration.
3. Explore available tools in our tool reference.
4. Start querying your New Relic data using natural language.
5. Troubleshoot common issues.