NORNR mark NORNR Policy decisions, review and audit trail before consequential local tool execution clears.
Control room

Agent Zero / 9 minutes

MCP control guide

How to add the NORNR MCP control server to Agent Zero.

Use Agent Zero as the local execution layer, but keep consequential tool execution behind one NORNR decision, one review path and one finance-safe record afterward.

You will add
  • one MCP control server inside Agent Zero
  • one default local-tools policy pack for first rollout
  • one review and proof path for queued local tool actions
Best for
  • teams already using Agent Zero for rich local tool execution
  • operators who need review before local actions can create spend or vendor consequence
  • buyers who need local-agent autonomy to read like the same control plane as hosted runtime spend

1. Why Agent Zero needs a control layer above raw MCP tools

Raw MCP connectivity gives Agent Zero capability, not institutional posture. It does not answer whether a local tool request should happen under the active mandate, who should review it above threshold, or what record finance receives later.

NORNR fixes that by turning one local tool request into a governed intent. Approved requests stay fast. Queued requests land in review. The same action survives into review bundle, finance packet and timeline later.

2. Install and authenticate once

bash 
pip install nornr-agentpay
nornr login --open-browser

3. Generate the Agent Zero MCP config

bash 
nornr mcp agent-zero-config --server-name nornr --agent-id agent-zero-agent

Paste the resulting stanza into Agent Zero configuration, or open the MCP config generator if you want the same setup through a form.

4. Start with one consequential local tools lane

The best first lane is one tool path that already matters outside the local agent.

  • a local tool call that can trigger vendor-side work
  • a paid provider request that should clear budget and counterparty posture first
  • a local action that should queue above threshold instead of running autonomously

Use the default mcp-local-tools-guarded posture first. Review-first mode is usually a better first step than broad local autonomy.

5. What NORNR exposes through MCP

  • nornr.check_spend and nornr.request_spend for intent and decision
  • nornr.approve_spend, nornr.reject_spend and nornr.pending_approvals for review
  • nornr.review_bundle, nornr.finance_packet, nornr.weekly_review and nornr.intent_timeline for proof and export

6. The buyer-safe lane to prove first

  1. Agent Zero proposes one local tool action.
  2. NORNR decides approved, queued or blocked.
  3. Queued work lands in one review path with the reason attached.
  4. The resulting action survives into export later.

That is the point of MCP productization for NORNR: local-agent autonomy stops being a governance blind spot.

7. Where to go next