Skip to content

New Relic MCP connector

The New Relic connector brings New Relic users, groups, roles, accounts, and workloads into Claude, ChatGPT, Cursor, 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.

  • How it connects. Connects with an API key. The credential goes into a vault nobody reads back.

  • One address. https://api.elaichi.ai/mcp, the same for every user.

  • Their own access. An agent never gets more than the person it acts for.

How to connect

How to connect New Relic to Claude, ChatGPT or Cursor

Two steps, about a minute.

1

In Elaichi

Connect New Relic once

  1. Open Connections, choose Add connection, and pick New Relic.

  2. Optionally set Share with to give a team access, 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.

The credential is vaulted. Nobody reads it back, not even the AI.

Add connection

Choose a connector.

new relic
New Relic
Axiom
Datadog
Grafana Cloud
Honeybadger
Honeycomb
2

In your AI client

Point it at one endpoint

Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.

New Relic MCP connector for Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 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 ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

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

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

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

New Relic MCP connector for Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

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

    Reload Cursor, then sign in and approve.

~/.cursor/mcp.json

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

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

Connect New Relic to any MCP client

  1. 1

    Add the endpoint as a remote MCP server.

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

    Sign in and approve.

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

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

Use cases

What teams do with New Relic through Elaichi

Every one of these runs inside the access the person already has, and lands in the same audit log.

  • Platform

    Check workload health before a release

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

  • IT

    Set up a new engineer in New Relic

    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.

  • Security

    Review who holds which New Relic role

    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.

  • Engineering

    Map every entity in a workload

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

  • Finance

    Reconcile New Relic accounts and seats

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

  • IT

    Remove leavers from New Relic cleanly

    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.

Try asking

  • “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”

See all 54 New Relic tools below

Compare

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.

Elaichi compared with Zapier MCP and Composio for New Relic, by what to check
What to check Elaichi Zapier MCP Composio
Where the AI connects One address for the whole organization. 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 $15 per user per month. 2 tasks per successful call. Billed per tool call.

Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.

Longer take: Zapier MCP alternative and when you don't need an MCP gateway.

AI tools

New Relic tools for your AI agents

54 tools are ready to call through Elaichi's MCP endpoint the moment you connect New Relic, governed by the same roles, restrictions, and audit log as everything else in Elaichi.

See it in Elaichi

What connecting New Relic gets you

6 screens from the product, each doing one job for your New Relic account.

The agent

Ask about New Relic users in plain language.

Three starter prompts return answers from live users, roles and groups.

  • users
  • roles
  • groups
  • authentication domains

Ask Elaichi to work across your apps.

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

Also runs in Claude, ChatGPT or Cursor

MCP clients

Claude, ChatGPT and Cursor share one endpoint.

Connect New Relic over OAuth from any MCP client, no SDK, no shared key.

ElaichiMCP clients
Claude ChatGPT Cursor

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emily Carter

• Connected 4 minutes ago
Cursor
M

Megan Brooks

• Connected 2 hours ago
ChatGPT
R

Ryan Hayes

• Connected Yesterday

Tool catalog

54 New Relic tools, no custom code.

Browse tool names, resources and methods covering users, roles, groups and domains.

  • List all New Relic users
  • Get single New Relic user by ID
  • Delete a New Relic user by ID
  • Create a New Relic user
ElaichiTools
Tool Action Description
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

Toolboxes

Every team gets its own New Relic toolbox.

Toolboxes are scoped per team, so each one sees only what it needs.

  • Platform engineering
  • Site reliability
  • Security
  • IT operations
ElaichiToolboxes
Name Source template Tools Created

Platform engineering toolbox

New Relic · users and groups

New Relic starter 18 Mar 4, 2026

Site reliability toolbox

New Relic · roles and permissions

— 9 Mar 2, 2026

Security toolbox

New Relic · authentication domains

— 24 Feb 27, 2026

IT operations toolbox

New Relic · user provisioning

New Relic starter 6 Feb 19, 2026

Data engineering toolbox

New Relic · group membership

— 31 Jan 30, 2026

Compliance toolbox

New Relic · role reviews and access records

— 12 Jan 22, 2026

Shared connections

Teammates use New Relic without a credential.

The connections table shows who connected each account and how widely it is shared.

  • Platform
  • SRE on call
  • Security EMEA
  • IT operations
ElaichiConnections
Connection Scope Status Access
NE

New Relic (Platform)

Connected by Emily Carter

Personal • Active 1 team · 6 members
NE

New Relic (SRE on call)

Connected by Jake Morgan

Organization • Active 3 teams · 24 members
NE

New Relic (Security EMEA)

Connected by Megan Brooks

Organization • Active 2 teams · 11 members
NE

New Relic (IT operations)

Connected by Tyler Reed

Personal • Needs re-auth 1 team · 3 members
NE

New Relic (Data engineering)

Connected by Ryan Hayes

Personal • Active Not shared
NE

New Relic (Compliance)

Connected by Ashley Parker

Personal • Active 2 teams · 9 members

Audit log

Answer who changed which New Relic role.

Append-only entries record when, who, what happened, type and resource.

  • When
  • Who
  • What happened
  • Type
ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emily Carter

emily.carter@northwind.io

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

Jake Morgan

jake.morgan@northwind.io

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

M

Megan Brooks

megan.brooks@northwind.io

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

T

Tyler Reed

tyler.reed@northwind.io

New Relic Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

R

Ryan Hayes

ryan.hayes@northwind.io

New Relic Users Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

A

Ashley Parker

ashley.parker@northwind.io

New Relic Users List Toolbox

Launching soon

From answering questions to doing the work

A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.

Automations

A schedule fires, a digest ships approved.

Six steps fetch New Relic groups, group them, draft, get approval, post back.

New Relic digest

Run 418 · started 2 minutes ago · on behalf of Emily Carter

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch users

    New Relic

    1.4s
  3. ✓

    Group by owner

    Transform

    0.1s
  4. ✓

    Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Michael Brennan

    Approve
  6. Post the digest

    New Relic

    Queued

Collections and dashboards

New Relic health, computed on a schedule.

Four metrics, a 14 day chart of users created, and a team breakdown.

New Relic health

Refreshed 4 minutes ago · every 15 minutes · from the users collection

Live

Users

1,284 ↓ 12%

Roles

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Users created

Last 14 days

By team

Share of activity

Platform 34%

SRE on call 27%

Security EMEA 21%

IT operations 18%

FAQ

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, 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 hiding particular actions from a team 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 block individual actions on the New Relic connection, such as deleting users, deleting accounts, or updating groups, while leaving the read actions available. A blocked action is never shown to Claude, ChatGPT, or any other client, so no prompt can reach it.

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

Put New Relic in front of your team

14 days on Gold, no credit card. Connect it once and pick what each team can call.

Works with
Claude ChatGPT Cursor and any other MCP client, or the Elaichi Agent.
When the trial ends
Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.