• /
  • EnglishEspañolFrançais日本語한국어Português
  • EntrarComeçar agora

Troubleshoot New Relic MCP

OAuth flow not starting

  • Ensure your browser can access localhost.
  • Check firewall settings.
  • Verify that your tools can access OAuth URLs.

API key not working

  • Verify key format (starts with NRAK-).
  • Check key permissions in New Relic.
  • Ensure the key is not expired.

MCP server not detected

  • Restart the application completely.
  • Check JSON syntax validity.
  • Verify file paths and permissions.

mcp-remote proxy issues

  • Ensure Node.js is installed.
  • Check internet connectivity.
  • Verify npx can access mcp-remote package.

Access denied for custom groups

Problem

You are unable to successfully connect to or authenticate with the New Relic AI MCP Server and receive the following error message: Missing required capabilities to access MCP server. Please ensure you have the necessary permissions. This typically occurs if you are a member of a custom user group without any organization-level grant.

Cause

Your custom group lacks the required organization-level access controls or roles needed to use the MCP Server endpoints. Access to this organization-wide feature must be explicitly granted to your group or user role.

Resolution

An administrator in your organization must implement one of the following two solutions to grant you access:

  1. Grant the group an organization-level role:
    • The administrator must add an appropriate organization-level role (or the specific required grant) to the custom group you belong to.
  2. Move you to an authorized group:
    • The administrator must add you to an existing user group that already has the necessary organization-level access privileges for the MCP Server.

For detailed information on user management concepts, roles, and organization grants, refer to the New Relic user management documentation. If your organization uses System for Cross-domain Identity Management (SCIM) for user management, these group and role adjustments must be performed within your external Identity Provider (IdP).

Error messages

  • Connection refused: Check URL and network connectivity of your tools.
  • Authentication required: Verify that the API key is still active and was inputted correctly or complete OAuth flow.
  • Invalid client: OAuth configuration issue, try mcp-remote proxy.
  • Time.UnmarshalJSON: Use mcp-remote proxy for OAuth.
Copyright © 2025 New Relic Inc.

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.