New Relic

Developer tools

New Relic for AI agents. Managed auth, ready-made tools.

Query telemetry with NRQL, find entities, review alert policies and record deployments in New Relic on behalf of each of your users.

About New Relic

With the New Relic connector, your agent works in each user’s own New Relic account. It can run NRQL queries on metrics, logs and events, find services and hosts, review alert policies and conditions, and record a deployment, using only the tools your project allows.

New Relic is an observability platform for application performance, infrastructure, logs and alerts.

Tools

What your agent can do in New Relic.

Each tool is a capability the model can call. You decide which ones a project allows, and every call runs with the end user's own New Relic connection.

  • Run a NRQL query

    Read
    new_relic_run_nrql_query

    Run a NRQL query on the account's metrics, events and logs.

  • Search entities

    Read
    new_relic_search_entities

    Find services, hosts and other entities by name or type.

  • Get an entity

    Read
    new_relic_get_entity

    Get an entity's details and health status.

  • List alert policies

    Read
    new_relic_list_alert_policies

    List the account's alert policies.

  • List alert conditions

    Read
    new_relic_list_alert_conditions

    List the conditions in an alert policy.

  • Record a deployment

    Write
    new_relic_create_deployment

    Add a deployment marker to an entity.

Control

Limits you can set.

You decide what your agent may do in New Relic, and Agent200 runs every call within those limits.

  • Turn single tools on or off

    Let the agent query data and read alerts, and switch off new_relic_create_deployment so it can never add a marker.

  • Restrict what the agent reaches

    Choose the endpoints and scopes a project may use, for example NRQL queries but not alert settings. A call outside them is refused.

Get started

Connect New Relic
in three steps.

  1. 1

    Set up the SDK

    Add the Agent200 SDK to the codebase you already have and authenticate with your API key. The key covers every connector enabled for the project.

    agent.js
    Conceptual example
    Set up the SDK with the Agent200 API key
    // One Agent200 API key covers every connector enabled for the project.
    const agent200 = new Agent200({
      apiKey: process.env.AGENT200_API_KEY,
    });
  2. 2

    Let your user connect New Relic

    Each end user authorizes their own New Relic account once. Agent200 runs the OAuth flow, handles the callback, stores the tokens and refreshes them.

    connect.js
    Conceptual example
    Let an end user connect their account (managed OAuth)
    // Each end user authorizes their own New Relic account, once.
    const connection = await agent200
      .user("user_123")
      .connect("new_relic");
    
    if (connection.authorizationUrl) {
      // Show this link to your user; Agent200 handles the rest.
      console.log(connection.authorizationUrl);
    }
  3. 3

    Run with the New Relic tools

    Name the user, the model and the tools. The model decides which New Relic tools to call, and Agent200 executes them with that user's connection.

    run.js
    Conceptual example
    Run a request with the connector's tools
    const result = await agent200
      .user("user_123")
      .run({
        model: "openai/gpt-5.6-sol",
        input: "What was the error rate of the checkout service in the last hour",
        tools: ["new_relic"],
      });
    
    console.log(result.output);

Access

Sign-in and permissions.

  • Who signs in

    Each of your users, once, by connecting their own New Relic account. Each connection is their own.

  • What access is requested

    The connection acts with that user's access in New Relic, such as querying data, reading entities and reading alert settings. Users can revoke it later from their New Relic account settings.

For agents

Instructions for AI agents.

Using a coding agent? Paste this brief into it, or give it the address of this page. It describes the New Relic connector and how to use it.

Agent brief
Connector: New Relic, through Agent200. In code: "new_relic".
What it does: Query telemetry with NRQL, find entities, review alert policies and record deployments in New Relic on behalf of each of your users.
Page: https://www.agent200.com/connectors/new-relic/

1. Get an Agent200 API key. If the developer has none, send them to https://agent200.com/platform/apikeys/ and ask them to choose "Create an API key". Read the key from the AGENT200_API_KEY environment variable. Never ask for it in chat, and never write it into code, prompts or logs.
2. Sign-in is managed OAuth. Each end user approves access once, on New Relic's own page, through the authorization link Agent200 returns. Never ask a user for a New Relic password or token in chat.
3. Give every request a stable id for the end user. Agent200 uses only that user's own connection.
4. Read tools: new_relic_run_nrql_query, new_relic_search_entities, new_relic_get_entity, new_relic_list_alert_policies, new_relic_list_alert_conditions. Write tools: new_relic_create_deployment. Name "new_relic" in the tools of a request; the model decides which tool to call.
5. Stay within the project's settings. If a tool is turned off or a call is refused, tell the user. Do not work around it.
6. Before a write, confirm with the user, unless they asked for that exact change.
7. For setup with a specific framework, follow its guide:
   https://www.agent200.com/connectors/new-relic/framework/claude/
   https://www.agent200.com/connectors/new-relic/framework/chatgpt/
   https://www.agent200.com/connectors/new-relic/framework/claude-code/
   https://www.agent200.com/connectors/new-relic/framework/muse/
   https://www.agent200.com/connectors/new-relic/framework/grok-bot/
   https://www.agent200.com/connectors/new-relic/framework/openai-dots/
   https://www.agent200.com/connectors/new-relic/framework/claude-duet/
   https://www.agent200.com/connectors/new-relic/framework/hermes-agent/
   https://www.agent200.com/connectors/new-relic/framework/openclaw/

The code on the connector page is a conceptual example of the SDK. SDK reference: https://docs.igpt.ai/

This page is also available as Markdown, for agents and LLMs: /connectors/new-relic.md

Guides

Use New Relic with the AI you build on.

Step-by-step setup for New Relic with a specific model, assistant or agent framework.

FAQ

New Relic and Agent200, answered.

Who handles the New Relic OAuth flow and the tokens?

Agent200. It runs the authorization, handles the callback on its own domain, stores the tokens and refreshes them. You do not build or maintain an OAuth integration for New Relic.

Does my agent act as the end user?

Within what that user authorized, yes. Every request names an end user, and Agent200 uses only that user's New Relic connection, never another user's. It cannot reach anything the user or New Relic has not authorized.

Can I limit what my agent can do in New Relic?

Yes. You choose which services, endpoints and authorization scopes are allowed in your Agent200 configuration, and the agent works only within them.

  • GitHub

    GitHub

    Read repositories and work with issues and pull requests as the connected user.

    Managed OAuth Developer tools
  • GitLab

    GitLab

    Review merge requests, file issues, read code and check pipelines in your users' GitLab projects.

    Managed OAuth Developer tools
  • Bitbucket

    Bitbucket

    List and open pull requests, comment, read code and check pipelines in your users' Bitbucket workspaces.

    Managed OAuth Developer tools
  • Jira

    Jira

    Search, create and transition Jira issues for the connected user.

    Managed OAuth Developer tools
200 OK

Start with New Relic.
Your agent does the rest.

Your users connect their own New Relic accounts. Agent200 handles the OAuth, the tokens and every tool call.

Book a demo.
See it in action.

Tell us who you are, then pick a time for a 1:1 session with an expert from our team.

We use your details only to email you about Agent200. See the Privacy Policy.

Pick a time. We'll take it from there.

A 1:1 session with an expert from our team, about what you are building.

Open in Calendly (opens in a new tab)