New Relic Preflight

Official New Relic Observability

Lets an agent use New Relic Preflight to track AI coding assistants' actions, costs, and efficiency. Summary written by AI Index.

The registry’s description: New Relic MCP server for observing AI coding assistants (Claude Code, Cursor, Copilot, etc.)

Local package (npm)

Add to your client

Add the New Relic Preflight MCP server to Claude Code

  1. Run the command

    claude mcp add new-relic-preflight -- npx -y @newrelic/preflight
  2. Fill in the values ↓

  3. Check it’s connected

If the file already has servers, add the entry inside the existing object. To check it’s connected, restart or reload the client and look for new-relic-preflight in its list of MCP servers. A server that needs sign-in opens it on first use.

What you fill in

Required values appear as <NAME> placeholders in the snippets; add optional ones the same way. Descriptions are the server’s registry entry’s.

  • <NEW_RELIC_LICENSE_KEY> Environment variable Optional · Secret

    New Relic ingest license key. Optional: while NR_AI_MODE is unset or local, Preflight runs local-only with the dashboard at localhost:7777. A license key with no mode set by NR_AI_MODE or the config file makes the server fail to start.

  • <NR_AI_MODE> Environment variable Optional

    Where telemetry goes: "cloud" (New Relic only), "both" (New Relic plus the local dashboard) or "local". Required when NEW_RELIC_LICENSE_KEY is set, unless the config file sets a mode. cloud turns off the local dashboard and local alerts.

  • <NEW_RELIC_ACCOUNT_ID> Environment variable Optional

    New Relic account id. Required when NR_AI_MODE is cloud or both; also used for dashboard and alert deployment.

Client compatibility

By transport: whether the client’s docs list a transport this server offers. It doesn’t cover sign-in or other requirements.

Sources

This data comes from the Official MCP Registry.