# 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.

- Page: https://www.agent200.com/connectors/new-relic/
- Category: Developer tools
- Authentication: Managed OAuth
- Identifier in code: `new_relic`
- Create an API key: https://agent200.com/platform/apikeys/
- Updated: 2026-11-18

## Instructions for AI agents

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/

## About

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.

## New Relic tools

- **Run a NRQL query** (`new_relic_run_nrql_query`, read): Run a NRQL query on the account's metrics, events and logs.
- **Search entities** (`new_relic_search_entities`, read): Find services, hosts and other entities by name or type.
- **Get an entity** (`new_relic_get_entity`, read): Get an entity's details and health status.
- **List alert policies** (`new_relic_list_alert_policies`, read): List the account's alert policies.
- **List alert conditions** (`new_relic_list_alert_conditions`, read): List the conditions in an alert policy.
- **Record a deployment** (`new_relic_create_deployment`, write): Add a deployment marker to an entity.

## Limits you can set

**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

### Step 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.

File `agent.js`:

```js
// One Agent200 API key covers every connector enabled for the project.
const agent200 = new Agent200({
  apiKey: process.env.AGENT200_API_KEY,
});
```

(Conceptual example of the Agent200 SDK.)

### Step 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.

File `connect.js`:

```js
// 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);
}
```

(Conceptual example of the Agent200 SDK.)

### Step 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.

File `run.js`:

```js
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);
```

(Conceptual example of the Agent200 SDK.)

## 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.

## Example requests

- "What was the error rate of the checkout service in the last hour"
- "Which hosts used the most CPU today"
- "Show the alert conditions in our production policy"
- "Record a deployment of version 2.4.1 for the API service"

## Guides: New Relic with your AI framework

- [New Relic + Claude](https://www.agent200.com/connectors/new-relic/framework/claude.md): Set up New Relic for Claude with Agent200, then check which tools are available to your agent.
- [New Relic + ChatGPT](https://www.agent200.com/connectors/new-relic/framework/chatgpt.md): Set up New Relic for ChatGPT with Agent200, then check which tools are available to your agent.
- [New Relic + Claude Code](https://www.agent200.com/connectors/new-relic/framework/claude-code.md): Set up New Relic for Claude Code with Agent200, then check which tools are available to your agent.
- [New Relic + Muse](https://www.agent200.com/connectors/new-relic/framework/muse.md): Set up New Relic for Muse with Agent200, then check which tools are available to your agent.
- [New Relic + Grok Bot](https://www.agent200.com/connectors/new-relic/framework/grok-bot.md): Set up New Relic for Grok Bot with Agent200, then check which tools are available to your agent.
- [New Relic + OpenAI Dots](https://www.agent200.com/connectors/new-relic/framework/openai-dots.md): Set up New Relic for OpenAI Dots with Agent200, then check which tools are available to your agent.
- [New Relic + Claude Duet](https://www.agent200.com/connectors/new-relic/framework/claude-duet.md): Set up New Relic for Claude Duet with Agent200, then check which tools are available to your agent.
- [New Relic + Hermes Agent](https://www.agent200.com/connectors/new-relic/framework/hermes-agent.md): Set up New Relic for Hermes Agent with Agent200, then check which tools are available to your agent.
- [New Relic + OpenClaw](https://www.agent200.com/connectors/new-relic/framework/openclaw.md): Set up New Relic for OpenClaw with Agent200, then check which tools are available to your agent.

## FAQ

### 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.

## Related connectors

- [GitHub](https://www.agent200.com/connectors/github.md): Read repositories and work with issues and pull requests as the connected user.
- [GitLab](https://www.agent200.com/connectors/gitlab.md): Review merge requests, file issues, read code and check pipelines in your users' GitLab projects.
- [Bitbucket](https://www.agent200.com/connectors/bitbucket.md): List and open pull requests, comment, read code and check pipelines in your users' Bitbucket workspaces.
- [Jira](https://www.agent200.com/connectors/jira.md): Search, create and transition Jira issues for the connected user.

---

Agent200: https://www.agent200.com/ · API keys: https://agent200.com/platform/apikeys/ · Docs: https://docs.igpt.ai/
