New Relic + clariBI
Connect New Relic through clariBI's MCP catalog. Read-only OAuth, no exports, and reliability data sitting next to your revenue and product metrics: response times, error rates, throughput, and the alerts that fired.
Native New Relic connector via the MCP catalog.
Connect with OAuth, keep the access read-only, and ask questions across New Relic and your other tools in plain English. The setup is the same one-click flow as Google Analytics, Stripe, Meta Ads, or Jira.
What is New Relic?
New Relic is an observability platform that watches the health of applications and infrastructure: how fast requests respond, how often they fail, how much traffic flows, and which alerts fired when something broke.
clariBI reaches your New Relic account through its hosted MCP server. The connection inherits the account access of the person who authorizes it, and the catalog exposes read tools only, so clariBI queries entities, metrics, and alert state and never changes a setting, silences an alert, or edits a dashboard in New Relic.
Learn more at newrelic.com
Connect New Relic in three steps
Open Data Sources in clariBI
In clariBI, go to Data Sources → Add Data Source → MCP Servers tab. Find New Relic in the catalog and click Connect.
Authorize with New Relic (OAuth)
A New Relic sign-in opens in your browser. Approve the read access. clariBI uses Dynamic Client Registration, so there is no New Relic app to set up on your side, and credentials are Fernet-encrypted at rest.
Ask questions, get dashboards
clariBI surfaces error rates, latency, throughput, and alert counts by service. Ask "Which services threw the most errors during last week's checkout outage?" or "Compare API latency before and after the Tuesday release" and the AI engine queries New Relic alongside your CRM, Stripe, and other sources.
What you can analyze
Out of the box with the New Relic MCP connector:
- Error rate by service, release, or time window
- Response time and throughput trends per endpoint
- Alert volume and frequency by service or policy
- Before-and-after comparisons around a deploy
- Apdex and saturation by application or host
- Cross-source: error spikes → support tickets → lost revenue
New Relic is one of 90+ vendors in the clariBI MCP catalog. See the full list →
What the AI engine can call
clariBI discovers New Relic's tool surface at connection time and exposes the read-only tools to the planner. Write or configuration tools are filtered out by the catalog's read-only heuristic, so the connector stays analytical.
When you connect, clariBI lists the tools your New Relic MCP server advertises and keeps the read-only ones: querying entities, reading metrics and events, and reading alert and incident state. The exact set tracks whatever New Relic ships, so the connector does not go stale when New Relic adds a tool.
Anything that would change New Relic (acknowledging an incident, editing a policy, muting an alert) is excluded at the catalog layer and never reachable through clariBI.
See the live tool list once connected, or read the setup guide →
Cross-source questions New Relic makes possible
Reliability data matters most next to revenue and customer data. clariBI's planner composes New Relic with Stripe, your CRM, and your support tools through the same entity-join primitives that back every cross-source analysis.
New Relic × Stripe
"During the checkout error spike on the 14th, how much revenue did we lose?"
Planner: read error rate for the checkout service from New Relic over the window, then sum the Stripe charges that failed or never started in the same period.
New Relic × Release notes
"Did the Tuesday release change latency or error rate on any service?"
Planner: pull per-service latency and error rate from New Relic before and after the deploy timestamp, then flag the services that moved beyond their normal range.
New Relic × Support
"Do alert bursts line up with spikes in support tickets?"
Planner: count alerts per service per day from New Relic, join to ticket volume from your support tool on the same days, and chart the correlation.
New Relic connector FAQ
Do I need to register an app with New Relic?
No. clariBI uses Dynamic Client Registration (RFC 7591), so New Relic issues the connection credentials at connect time. You do not manage any keys or secrets in clariBI.
Can clariBI change anything in New Relic?
No. The catalog exposes read tools only, and the read-only heuristic filters out anything that would write. clariBI reads entities, metrics, and alert state; it never acknowledges incidents, edits policies, or mutes alerts.
A service returns no data. Why?
The connected New Relic account may not have access to that entity, or the service reports under a different name. Confirm the service name in New Relic and that your user can see the account or sub-account it reports under.
The connection says authorization expired.
The OAuth grant timed out or was revoked in New Relic. Reconnect from Settings → Integrations in clariBI; the one-click authorization runs again.
Which clariBI plan includes the New Relic connector?
MCP integrations are available on the Trial, Starter, Professional, and Enterprise plans. You can connect New Relic during the free 14-day trial.
Start your free trial and connect New Relic in a minute
OAuth in, read-only, dashboards in seconds.
Start free trial