# New Relic MCP connector

The New Relic connector brings New Relic users, groups, roles, accounts, and workloads into Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent, so your team can ask about them and manage them in plain language while every call runs as the person who signed in.

Source: https://elaichi.ai/connectors/newrelic/

## Facts

| | |
| --- | --- |
| Application | New Relic |
| Category | Observability |
| AI tools | 54 |
| Authentication | Connects with an API key |
| Bring your own OAuth app | No |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once New Relic is connected

- List New Relic users added to the SRE group this month
- Which New Relic roles grant admin on our authentication domains
- Show groups in New Relic with no members assigned

## Connect New Relic in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick New Relic.
2. Optionally set Share with, then press Connect.
3. Paste a New Relic API key. One person generates a token in New Relic and pastes it once. Everyone else works through Share with, and never sees it.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which New Relic tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## New Relic MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
4. Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

## New Relic MCP connector for Claude Code

Endpoint: https://api.elaichi.ai/mcp

1. In a terminal, run `claude mcp add` with the endpoint.
2. Start Claude Code and run `/mcp`.
3. Pick elaichi, then sign in and approve in the browser.

```bash
claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
```

Use `--scope project` instead to share it with the repository through `.mcp.json`.

## New Relic MCP connector for ChatGPT

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
3. Leave Authentication on OAuth, then tick the risk acknowledgement.
4. Press Create, then sign in and approve.

Works on the web. The plugin directory lives at chatgpt.com/plugins.

## New Relic MCP connector for Cursor

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## New Relic MCP connector for Microsoft Copilot

Endpoint: https://api.elaichi.ai/mcp

1. In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
2. Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
3. Create a new connection, sign in and approve, then press Add to agent.
4. Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.

## Connect New Relic to any MCP client

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Every scope the client asks for starts ticked except "Delete things", which you tick yourself. Calling a New Relic tool needs "Use your connected apps". Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Think hard before granting Use your connected apps, which can also delete in connected apps and cannot be undone.

## What teams do with New Relic through Elaichi

### Check workload health before a release

Platform. Ask which New Relic workloads are degraded right now and which services and hosts sit inside them, then decide whether to ship or hold.

### Set up a new engineer in New Relic

IT. Create the person's New Relic user, put them in the right group, and confirm which roles that group carries, without opening the admin console.

### Review who holds which New Relic role

Security. Pull the full list of New Relic users, their groups, and their roles across each authentication domain to find people with more access than their job needs.

### Map every entity in a workload

Engineering. List the services, hosts, and other entities grouped under a New Relic workload, along with their tags, to see what a team actually owns.

### Reconcile New Relic accounts and seats

Finance. List every New Relic account and the users attached to each one, then spot inactive people and duplicate accounts before the next renewal.

### Remove leavers from New Relic cleanly

IT. When someone leaves, remove their New Relic user and take them out of every group in one conversation, and keep a record of who did it.

## Elaichi vs Zapier MCP vs Composio for New Relic

All three can connect New Relic to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

| What to check | Elaichi | Zapier MCP | Composio |
| --- | --- | --- | --- |
| Where the AI connects | One address for the whole organization. Endpoint: https://api.elaichi.ai/mcp | A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over New Relic tools | Allow or restrict single New Relic tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per New Relic call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |

Sources: Zapier MCP [docs](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### How do I connect New Relic to Claude?

Connect New Relic in Elaichi first: paste a New Relic API key when asked, and the connection is ready in under a minute. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp as the address. There is no OAuth application to register in New Relic and no client ID or secret to generate.

### Does New Relic work with ChatGPT and Cursor as well as Claude?

Yes. Once New Relic is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client, and the Elaichi Agent. You connect New Relic once and every client picks it up.

### What can an AI agent actually do with my New Relic data?

An agent connected to New Relic through Elaichi can list your users, groups, roles, authentication domains, and accounts, create or update users and groups, and tell you which workloads are healthy or degraded and which services sit inside them. It can also read the tags on your accounts and workloads to answer questions like which team owns a service. Because New Relic exposes a lot of actions, short concrete asks such as show me degraded workloads work better than long paragraphs.

### Does connecting New Relic give the AI access to every account and role?

No. The AI only sees what the New Relic API key you connected can see, so if that key covers one account it cannot reach the others. Elaichi can narrow that further by restricting particular actions for a role or a person, and it can never grant anything the key itself does not have.

### Can my team share one New Relic connection?

Yes. One administrator connects New Relic with an API key and shares the connection with a team in Elaichi, and nobody else ever sees or handles that key. Each teammate still signs in to Elaichi as themselves, so the audit log names the actual person behind every New Relic change.

### Can I stop an agent from deleting or changing things in New Relic?

Yes. In Elaichi you can restrict individual actions on the New Relic connection, such as deleting users, deleting accounts, or updating groups, while leaving the read actions available. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, or any other client cannot run it, whatever the prompt says.

### What happens to a New Relic connection when someone leaves?

When you offboard a person in Elaichi, their access to the New Relic connection ends immediately, along with every other connector they had. A shared New Relic connection keeps working for everyone else on the team. If you disconnect New Relic entirely in Elaichi, it disappears from Claude, ChatGPT, Cursor, Microsoft Copilot, and every other client at once.

### Does the New Relic MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. New Relic is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

### Is Elaichi an alternative to Zapier MCP for New Relic?

Yes. Both let Claude, ChatGPT or Cursor use New Relic. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every New Relic call.

### How is Elaichi different from Composio for New Relic?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to New Relic: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

## All 54 New Relic tools

Every tool below is callable through https://api.elaichi.ai/mcp once New Relic is connected, subject to the toolbox it is in and the restrictions on the caller.

- **List all New Relic users** (List). Use this endpoint to list all users available in the New Relic account.
- **Get single New Relic user by ID** (Get). Use this endpoint to retrieve detailed information about a specific user in New Relic.
- **Delete a New Relic user by ID** (Delete). Use this endpoint to delete a user from your New Relic account.
- **Create a New Relic user** (Create). Use this endpoint to create a new user in a manually provisioned New Relic authentication domain. You provide the authentication domain ID, the user’s email address, display name, and the requested user type tier (for example, BASIC_USER_TIER, CORE_USER_TIER, or FULL_USER_TIER)
- **Update a New Relic user by ID** (Update). Use this endpoint to update an existing user’s email address and/or user type tier, identified by their user ID
- **List all New Relic roles** (List). Use this endpoint to list all the roles available in New Relic.
- **Get single New Relic role by ID** (Get). Use this endpoint to retrieve detailed information about a specific role.
- **List all New Relic authentication domains** (List). Use this endpoint to list all authentication domains configured in your New Relic account.
- **Get single New Relic authentication domain by ID** (Get). Use this endpoint to retrieve detailed information about a specific authentication domain.
- **List all New Relic me** (List). Use this endpoint to retrieve information about the currently authenticated user.
- **List all New Relic groups** (List). Use this endpoint to list all groups in your New Relic account.
- **Get single New Relic group by ID** (Get). Use this endpoint to retrieve detailed information about a specific group.
- **Create a New Relic group** (Create). Use this endpoint to create a new user group in a specific New Relic authentication domain, providing the authentication domain ID and the group’s display name.
- **Update a New Relic group by ID** (Update). Use this endpoint to update the display name of an existing user group in New Relic, identified by its group ID.
- **Delete a New Relic group by ID** (Delete). Use this endpoint to delete an existing user group from New Relic, identified by its group ID.
- **List all New Relic accounts** (List). Use this endpoint to list all New Relic accounts that are visible to the authenticated user, including their IDs and basic metadata.
- **Create a New Relic account** (Create). Use this endpoint to create a new New Relic account (or sub-account) within the authenticated organization using the provided account details.
- **Update a New Relic account by ID** (Update). Use this endpoint to update an existing New Relic account’s properties, such as its name or settings, identified by its account ID.
- **Delete a New Relic account by ID** (Delete). Use this endpoint to delete or deprovision an existing New Relic account, identified by its account ID, according to New Relic’s account lifecycle rules
- **Get single New Relic account by ID** (Get). Use this endpoint to retrieve information about a specific managed account in your New Relic organization.
- **List all New Relic tags** (List). Use this endpoint to list all tags and their values attached to entities in New Relic, based on the entity search criteria you provide.
- **List all New Relic account workloads** (List). Use this endpoint to list all workload entities associated with a New Relic account, returning each workload’s GUID, name, and other identifying fields.
- **List all New Relic workload entities** (List). Use this endpoint to list the individual entities that belong to a specific workload, given the workload’s GUID or related identifiers.
- **List all New Relic workload status** (List). Use this endpoint to retrieve the computed status information for one or more workloads, such as their workloadStatus value for the given workload GUID.
- **List all New Relic alert policies** (List). Use this endpoint to list all alert policies configured for a New Relic account, including each policy’s ID, name, and incident preference.
- **Create a New Relic alert policy** (Create). Use this endpoint to create a new alert policy in a specific New Relic account, providing the account ID, policy name, and incident preference to control how incidents are opened and grouped.
- **Get single New Relic alert policy by ID** (Get). Use this endpoint to retrieve detailed information about a specific alert policy in a New Relic account, given the account ID and policy ID, including its name and incident preference.
- **Update a New Relic alert policy by ID** (Update). Use this endpoint to update an existing alert policy in a New Relic account, such as renaming the policy, identified by the account ID and policy ID.
- **Delete a New Relic alert policy by ID** (Delete). Use this endpoint to delete an existing alert policy from a New Relic account, identified by the account ID and policy ID, removing the policy and its associated alerting behavior.



- **List all New Relic dashboard** (List). Use this endpoint to list all dashboards available to the authenticated user, returning each dashboard’s GUID, name, and associated account ID.
- **Get single New Relic dashboard by ID** (Get). Use this endpoint to retrieve the full configuration of a specific dashboard, given its dashboard GUID, including metadata, pages, widgets, and variables.
- **Create a New Relic dashboard** (Create). Use this endpoint to create a simple New Relic dashboard in a specific account, using a single NRQL query.
The account is selected by its ID, and you provide the dashboard name, optional description, and an NRQL query. The endpoint creates a dashboard with one page and one billboard widget that visualizes the provided NRQL query.
- **Delete a New Relic dashboard by ID** (Delete). Use this endpoint to delete an existing New Relic dashboard, identified by its dashboard GUID.

- **List all New Relic log parsing rules** (List). Use this endpoint to list all log parsing rules defined for a New Relic account, including their IDs, patterns, NRQL, and enablement status.


- **Create a New Relic log parsing rule** (Create). Use this endpoint to create a new log parsing rule for a New Relic account.

- **Update a New Relic log parsing rule by ID** (Update). Use this endpoint to update an existing log parsing rule for a New Relic account.

- **Delete a New Relic log parsing rule by ID** (Delete). Use this endpoint to delete an existing log parsing rule from a New Relic account.

- **List all New Relic log data partition rules** (List). Use this endpoint to list all log data partition rules configured for a New Relic account, showing how logs are routed to target data partitions.
- **List all New Relic organization** (List). Use this endpoint to retrieve information about the current New Relic organization, including its organization ID and name.
- **List all New Relic teams** (List). Use this endpoint to list all teams defined in the New Relic organization, including each team’s ID, name, description, and aliases.
- **Create a New Relic team** (Create). Use this endpoint to create a new team in the New Relic organization, providing a team name, an optional description, and the organization ID that scopes the team.
- **Get single New Relic team by ID** (Get). Use this endpoint to retrieve detailed information about a specific New Relic team, given its team entity ID, including the team’s ID, name, description, and aliases.
- **Update a New Relic team by ID** (Update). Use this endpoint to update an existing New Relic team’s basic details, such as its name and description, identified by the team’s entity ID.
- **List all New Relic service levels** (List). Use this endpoint to retrieve the service level configuration (SLIs and their SLO objectives) for a specific New Relic entity, given its entity GUID, including each indicator’s metadata, target, and rolling time window.
- **Create a New Relic service level** (Create). Use this endpoint to create a new service level (SLI with a single SLO) for a specific New Relic entity.
You provide the entity GUID, NRDB account ID, SLI name and description, NRQL FROM/WHERE clauses for valid and good events, an SLO target percentage, and a rolling time window in days. Internally it calls the serviceLevelCreate mutation with an indicator that defines the valid and good events and creates one objective in the objectives list. The endpoint returns the newly created service level’s ID and description.
- **Get single New Relic service level by ID** (Get). Use this endpoint to retrieve the service level configuration for a specific entity and then select a single service level (SLI) by its ID
- **Update a New Relic service level by ID** (Update). Use this endpoint to update the SLO objectives for an existing service level indicator (SLI), identified by its SLI ID.
- **List all New Relic synthetic monitors** (List). Use this endpoint to list all synthetic monitors (ping, API, browser, and scripted monitors) visible to the authenticated user, returning each monitor’s GUID, name, account ID, monitor type, and key configuration tags.
- **Get single New Relic synthetic monitor by ID** (Get). Use this endpoint to retrieve basic information about a specific synthetic monitor, given its monitor entity GUID. It returns the entity’s GUID, name, type, account ID, and basic monitor-specific summary information.
- **List all New Relic golden metrics** (List). Use this endpoint to retrieve the golden metrics configuration for a specific New Relic entity, given its entity GUID, returning each golden metric’s NRQL query, title, and other key details that define the entity’s primary health signals
- ...and 4 more tools. Call `tools/list` via the MCP endpoint, or see the full catalog via the API, for the complete set.
