# How to connect New Relic to Claude

> Set up New Relic for Claude with Agent200, then check which tools are available to your agent.

- Page: https://www.agent200.com/connectors/new-relic/framework/claude/
- Connector: [New Relic](https://www.agent200.com/connectors/new-relic.md)
- Framework: Claude
- Updated: 2026-11-18

## Instructions for AI agents

Goal: connect New Relic to Claude with Agent200, through its MCP server.
Guide: https://www.agent200.com/connectors/new-relic/framework/claude/

1. The user needs an Agent200 API key. If they have none, send them to https://agent200.com/platform/apikeys/ to choose "Create an API key". They paste it into Claude's settings themselves: never ask for it in chat and never write it into files you share.
2. Make sure New Relic is enabled for their project in the Agent200 dashboard (Connectors), with the tools the task needs.
3. Add Agent200's MCP server to Claude: URL https://api.agent200.com/mcp/, transport streamable HTTP, header "Authorization: Bearer <the user's Agent200 API key>". Follow the setup steps on the guide page for Claude's exact menus or commands.
4. The first New Relic request returns an authorization link if the user has not connected New Relic yet: show it to them and continue once they have approved access on New Relic's own page.
5. Check it works with this request: "Ask Claude to list the Agent200 tools available for New Relic, including which are read-only."
   What should come back:
   - A list of the New Relic tools enabled for this Agent200 project, with their names and descriptions. If no tools appear, check that the connector is available to the project and its tools are enabled.
6. If a tool is missing or a call is refused, check the project's Connectors settings in the dashboard and the access the user granted in New Relic, then retry.

## Overview

This guide connects New Relic to Claude through Agent200's MCP server. When you finish, Claude can search, read and act in New Relic with the tools Agent200 provides, whenever a request needs them.

You add one MCP server to Claude with your Agent200 API key. Your New Relic account is connected through managed OAuth: you approve access once on New Relic's own page, and Agent200 keeps the connection working.

- **Connector:** [New Relic](https://www.agent200.com/connectors/new-relic/)
- **Works with:** Claude · Agent app, through MCP
- **Authentication:** Managed OAuth, per end user
- **You need:** [An Agent200 API key](https://agent200.com/platform/apikeys/)
- **Tools:** [6 tools](https://www.agent200.com/connectors/new-relic/framework/claude/#tools)
- **MCP server:** `https://api.agent200.com/mcp/`

## Before you start

- **An Agent200 API key.** Create one on the [API keys page](https://agent200.com/platform/apikeys/) of the dashboard.
- **New Relic enabled for your project.** In the dashboard's Connectors settings, with the endpoints and scopes your agent needs.
- **An end user with a New Relic account.** They approve access once, on New Relic's own page.
- **Claude, with custom MCP servers allowed.** Custom connectors are on every Claude plan (Free: one). Sending an API key uses the Request headers option, a beta that only some accounts have; on Team and Enterprise an Owner adds the connector for everyone.

## Connect New Relic to Claude

### Step 1: Create your Agent200 API key

Open the API keys page in the Agent200 dashboard and choose Create an API key. You add it to Claude in the next step, as "Authorization: Bearer <your key>". One key covers New Relic and every other connector enabled for your project. Keep it out of chats and source control.

Create an API key: https://agent200.com/platform/apikeys/

### Step 2: Open Connectors in Claude

On a Free, Pro, Max or Ultra plan, go to **Customize > Connectors**. On Team or Enterprise, an Owner goes to **Organization settings > Connectors**; members then find the connector under Customize > Connectors.

### Step 3: Add a custom connector

Select **Add**, then **Add custom connector**. Enter a name, Agent200, and the remote MCP server URL, then choose **Continue**.

### Step 4: Send your key as a request header

Under Authentication choose **No sign-in**. Open **Request headers**, pick `authorization`, enter `Bearer` followed by a space and your key, mark it Required and choose **Add**. Claude sends the value exactly as typed.

File `Add custom connector`:

```text
Remote MCP server URL:  https://api.agent200.com/mcp/
Authentication:         No sign-in
Request header name:    authorization
Value:                  Bearer YOUR_AGENT200_API_KEY
```

### Step 5: Turn it on in a chat

In a chat, select **+ > Connectors** and turn Agent200 on. Ask Claude to list the Agent200 tools to check the connection; Claude asks before a tool runs the first time.

### Step 6: Connect your New Relic account

The first time you ask Claude for something in New Relic, Agent200 returns an authorization link. Open it and approve access on New Relic's own page. Agent200 stores the connection and keeps it working; your password never reaches Claude or Agent200.

## Test your connection

Ask: "Ask Claude to list the Agent200 tools available for New Relic, including which are read-only."

What should come back:

- A list of the New Relic tools enabled for this Agent200 project, with their names and descriptions. If no tools appear, check that the connector is available to the project and its tools are enabled.

If no tools appear, check your Agent200 project access for New Relic and make sure its tools are enabled. Tool availability depends on your project setup.

## New Relic tools Claude can call

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

## How it works

1. **You ask Claude.** In your own words, for something in New Relic.
2. **Claude picks a tool.** It sees the New Relic tools on the Agent200 MCP server and calls the one the request needs.
3. **Agent200 runs the call.** With your own New Relic connection, within the tools and scopes your project allows.
4. **Claude answers.** It gets the result back from the MCP server and uses it in its reply or its next step.

**Each user's own connection.** Connections belong to individual end users. A request for one user never reaches another user's New Relic account.

**Permissions at every level.** Your project settings decide what the agent may request, the end user decides what they authorize, and New Relic enforces what its API grants.

## Troubleshooting

### There is no Request headers section

Request headers are a Claude beta that only some accounts have. Without it, Claude cannot send an API key to a custom connector: use Claude Code, or the Agent200 SDK in your own agent.

### Claude cannot reach the server

Check the header value is `Bearer`, a space, then your key, and that the URL is exactly the Agent200 MCP server address.

### A Team or Enterprise member cannot add the connector

Only an Owner adds custom connectors, in Organization settings > Connectors. Members then connect it under Customize > Connectors.

### You created a new API key

Claude does not let you edit a connector’s authentication. Remove the Agent200 connector and add it again with the new key.

### Claude does not use the New Relic tools

Open + > Connectors in that chat and check Agent200 is on, and that no tool is set to Blocked under Customize > Connectors. Naming New Relic in the request also helps.

### Claude shows a New Relic authorization link

You have not connected New Relic yet, or the connection needs to be approved again. Open the link, approve access on New Relic's own page, then ask Claude again.

### A tool call is refused or returns less than expected

Agent200 runs only what your project allows. Check that New Relic and the tools you need are enabled in the dashboard's Connectors settings, and that you granted New Relic the access the task needs.

### The API key was pasted into a chat or committed

Create a new key on the [API keys page](https://agent200.com/platform/apikeys/), replace it in Claude's MCP settings, and stop using the old one. Paste the key only into Claude's settings, never into a chat.

## Use New Relic with another framework

- [New Relic + ChatGPT](https://www.agent200.com/connectors/new-relic/framework/chatgpt.md)
- [New Relic + Claude Code](https://www.agent200.com/connectors/new-relic/framework/claude-code.md)
- [New Relic + Muse](https://www.agent200.com/connectors/new-relic/framework/muse.md)
- [New Relic + Grok Bot](https://www.agent200.com/connectors/new-relic/framework/grok-bot.md)
- [New Relic + OpenAI Dots](https://www.agent200.com/connectors/new-relic/framework/openai-dots.md)
- [New Relic + Claude Duet](https://www.agent200.com/connectors/new-relic/framework/claude-duet.md)
- [New Relic + Hermes Agent](https://www.agent200.com/connectors/new-relic/framework/hermes-agent.md)
- [New Relic + OpenClaw](https://www.agent200.com/connectors/new-relic/framework/openclaw.md)

---

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