• /
  • EnglishEspañolFrançais日本語한국어Português
  • 로그인지금 시작하기

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 group lacks an organization-scoped role with permission to read the MCP server. Access to this organization-wide feature must be explicitly granted to your group via an organization-scoped role.

Resolution

Your org admin who has the Authentication Domain Manager role must implement one of the following two solutions to grant you access:

  1. Grant your group a role with permission to read the MCP server:

    • The administrator must add one of the following roles to the custom group you belong to: Organization Read Only, Organization Manager, or Organization Product admin.
    • The administrator can create a custom organization-scoped role and assign it to a group you belong to via an organization-coped grant. This custom role must include the New Relic MCP Server read permission.
  2. Add you to an authorized group:

    • The administrator must add you to an existing user group that already has an organization-scoped role with permission to read 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.