Connect New Relic to Claude Code

Let Claude query telemetry and manage alerts and incidents in New Relic. From the terminal, inside the sessions where you already work.

Build my connector Talk to us

How do you connect New Relic to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect New Relic, you add a New Relic MCP server: a small hosted service that exposes New Relic's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own New Relic account. No API keys pasted into config files.

claude mcp add --transport http new-relic https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in New Relic once connected?

Full read-write New Relic access lets Claude query telemetry with NRQL, create or tune alert conditions and policies, acknowledge or close incidents, add tags to entities, and update dashboards, all once you approve. The investigation and triage that used to mean tab-switching happen where your observability data already lives.

Run a NRQL query and summarize the result for a service or account
Create or update an alert condition or notification policy
Acknowledge or close (resolve) an open incident
Add or remove tags on an entity to organize your inventory
Update a dashboard widget or NRQL query after you approve it
Mute an alert with a muting rule during a planned maintenance window

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same New Relic access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the New Relic API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when New Relic changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build New Relic connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same New Relic connector work in claude.ai and Claude Code?

Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own New Relic account, so access always matches what that person can already see and do.

Do I need to host or maintain anything myself?

No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on New Relic's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.

Is it safe to give a coding agent write access to New Relic?

Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the New Relic account it signs in with. Revoking access is one click in New Relic.

More on the New Relic connector

New Relic connector for claude.ai Bitbucket + Claude Code CircleCI + Claude Code Jenkins + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connector Talk to us