New Relic

What a member can do

• Run NRQL queries, or turn a plain-language question into NRQL.
• Find entities and dashboards, and list alert policies, conditions, incidents and open issues.
• Read logs, error groups, distributed traces, change events and synthetic monitor results.
• Get analyses of deployment impact, golden metrics, transactions and alert patterns.
• It is read-only: it cannot change alerts, dashboards or settings.

Each task names the New Relic tools it may call. new-relic on a task means every tool the New Relic server offers; a name such as new-relic.<tool> means that tool alone. A tool the task does not name is refused, whatever the connection allows.

Who connects it

A New Relic connection acts as the New Relic account that signed in when it was connected. It can do what that account can do, and no more.

Anyone who may change tools in your enterprise can connect New Relic for a member or a team. Connecting it for the whole enterprise is for the owner, and the people the owner allows.

A connection can sit on the enterprise, a team, a member, a role or a task, and the one further down replaces the one above: task, then role, then member, then team, then enterprise. A connection on anything but a task also reaches the chat of every member it covers.

What waits for you

In a run, nothing on New Relic waits for you unless the task declares a gate on it. To approve each change before it happens, gate the tools that change something on the task. See Gates and tool scopes.

In a chat, a New Relic tool that its server does not mark as read-only asks you before it runs, unless you chose Always allow for that member and tool.

Setup

Before you connect

A New Relic admin must enable MCP for the organisation first. Each person is limited to 2,000 tool calls an hour. This address serves US accounts: EU accounts use a different address.

Connect it

New Relic is an Express tool, so there is no server address, key or app to set up. Work in one browser window throughout: the sign-in returns to the portal in the window you started from.

1. In the portal, open the member's page → Tools. To connect it for a team or the whole enterprise, open Tools in the sidebar.
2. Under Express, find New Relic and choose Connect. On the Tools page you are asked who uses it: one member, a team or the whole enterprise.
3. New Relic's sign-in opens. Sign in with the account the member should work as, and approve what it asks for.
4. You are back on Tools, and New Relic shows as connected.
5. Name the tools on the task, new-relic for all of them or each by name.
6. Check it. Run a task that reads something from New Relic. The run page shows the call and what came back.

You can take the access back at any time: delete the connection on Tools, or remove Zero Human OS from the connected apps in your New Relic account.

A first task to try

With New Relic connected, give a member a task that uses it. For example:

Each morning, list the open issues and incidents, and summarise the errors behind the three most serious.

Start this task in the portal. It opens a conversation with your COO with the request written out. Read it, change what you like and send it. The COO asks what it still needs to know, then proposes the task for you to approve: its name, who owns it, its guardrails, the New Relic tools it may use and its instructions. Nothing is created until you approve it.