Noci AI in your AI assistant

How does Noci AI get into your AI assistant?

You add Noci AI to your AI assistant as a connector, over MCP. From then on the assistant can use Noci’s tools, so you can ask about your incidents in the same place you already ask about everything else.

What can you ask it?

Ask for a brief and it tells you today’s alerts, the incidents that are open and who was paged. Ask about an open incident and you get where it stands and what changed before it started, in one answer.

The answers come from Noci’s record: the same Context Lake the Noci console and its agents read from. Your assistant and your team see the same incident.

What happens when you ask for a change?

Your assistant files the change in Noci and changes nothing itself. The change waits there for a person. Someone who is allowed to make that change confirms it, and only then does it run.

A confirmed change can be undone in Noci. Where your workspace asks for a second approver, the undo waits for one more person too.

This is the same rule as an action Noci proposes in Slack, which also runs only when a person confirms it. See incident response in Slack and how agents ask first.

Who decides whether an assistant can request changes?

An admin decides, for the whole workspace, whether people’s assistants can request changes. The admin also decides whether each person may turn it on for themselves.

Each person can also keep their own assistant to questions, whatever the workspace allows.

How do you see a change’s impact before it runs?

A change to routing, severity or a service shows its impact first. Noci replays the last thirty days against the change, so the person confirming it sees what it would have done before deciding.