Observability and cloud costs · Available
New Relic for Claude, ChatGPT and Copilot
New Relic questions tend to arrive mid-incident: which issues are open, how an APM service's throughput and errors changed, whether service levels are on target and what deployed just before a slowdown. mcpbizapps lets engineers ask them in Claude, ChatGPT or Copilot. Questions run as NRQL within the accounts each role may see, and muting rules need approval. The guided pilot brings New Relic accounts in one at a time.
- Status
- Available
- Setup
- Guided pilot with your team
- AI assistants
- Claude, ChatGPT, Copilot Studio
- Access
- By role, view only or with approvals
Ask in a sentence
What can your team ask New Relic?
Questions from SRE, engineering manager, head of operations and others, answered from live New Relic data and only for the people allowed to see them.
Records it works with
- Entities
- APM services
- Alert policies
- Alert conditions
- Issues
- Dashboards
- Service levels
- Workloads
- SRE
“Which issues are open in the production account, and which alert policies raised them?”
- Engineering manager
“Compare the error rate for the cart service this week with last week, by deployment.”
- Head of operations
“Which service levels in the Checkout workload are below target for the last 28 days?”
- Mobile lead
“What is the crash rate for the latest iOS release compared with the previous one?”
- FinOps lead
“How much data did each account ingest last month, and which source grew most?”
- On-call engineer
“Which change tracking markers were recorded on the inventory service in the last two hours?”
Changes, governed
What the assistant can prepare in New Relic
The assistant never saves on its own. It prepares the change, the person checks the preview and confirms, and anything above your limits waits for an approver.
- 1 Prepare The assistant drafts the change from the request.
- 2 Preview and confirm The person sees exactly what will change.
- 3 Approve Above your limits, a second person decides.
- 4 Saved and logged Written to New Relic under a named person.
-
Create a muting rule for a scheduled database upgrade
The service owner confirms; rules lasting more than three hours need the SRE lead.
-
Acknowledge an issue and assign it to a teammate
The on-call engineer confirms the assignee; nobody else needs to approve.
-
Add a widget to a team dashboard
Team dashboards need their owner's yes; shared executive dashboards need the analytics owner.
Example rules. During the pilot you set the limits, the approvers and which roles may prepare each change.
Why it needs care
Governance built for New Relic
New Relic holds traces, logs and browser sessions that can include customer details, and a broad muting rule can hide an outage. Each role sees only the accounts and entities assigned to it. A muting rule shows the conditions it would silence, and long ones need sign off. Every NRQL query is saved alongside the person who ran it.
-
Sign-in by work email
Only people you invite, with a one-time code. No shared logins.
-
Roles per tool
Each role reaches only the New Relic records it needs.
-
View only, if you prefer
Admins can keep a connection to lookups with one switch.
-
A preview first
Every change is shown in full before anything is saved.
-
Approval rules
Above your limits, a second person approves the change.
-
One audit log
Every request tied to a named person, ready for review.
Setup
How New Relic gets connected
We connect New Relic for your team in a guided pilot, on the same gateway every app uses. No code on your side.
- 01
Agree the questions
We list the New Relic questions and changes your team needs, and who may use each.
- 02
Connect with your admin
Your New Relic administrator creates a dedicated integration user with only that access.
- 03
Test with your people
A small group tries it in Claude, ChatGPT or Copilot while we tune the tools.
- 04
Roll out with rules
Roles, approval limits and the audit log are in place before everyone joins.
Then people use it from the assistant they already have
New Relic questions
Can Claude write NRQL queries?
Yes. The assistant writes NRQL for the question, runs it against the accounts your role allows with a time limit, and shows the query beside the answer, so engineers can paste it into a dashboard later.
Can an assistant change alert conditions?
Not thresholds. Assistants can acknowledge issues and prepare muting rules with an end time. Changing alert conditions stays with the team that owns them, inside New Relic, where their review process already applies.
Does it support multiple New Relic accounts?
Yes. Roles can be limited to one account, such as production for a team, or span several for platform leads. Answers name the account so data from staging and production are never confused.
Does mcpbizapps keep a copy of our New Relic data?
No. When someone asks a question, mcpbizapps reads the answer live from New Relic through a dedicated integration user and returns it without storing it. The audit log records who asked, which tool ran and the result, with personal fields and free text removed.
New Relic is a trademark of its owner. mcpbizapps is not affiliated with New Relic; the name describes the connection only.
Related
Often connected alongside New Relic
Part of IT, security and operations: Service desks, identity, monitoring and cloud costs.
Start
Bring New Relic into your AI assistant
Tell us how your team uses New Relic, and we will plan a guided pilot around your own questions.
- We agree the tools and approval rules with you
- Your admin creates the integration user; no code
- Business data is read live and not stored
Thank you
We received your request and will reply by email to find a time.
Last updated