nornr-mcp-control

[](https://nornr.com/mcp-control-server) [](https://nornr.com/mcp-config-generator) [](https://nornr.com/community-policy-packs) [](https://nornr.com/nornr-vs-raw-mcp-tools)

Official public MCP package for NORNR, the control layer before consequential MCP tool execution.

This repo is intentionally thin.

It exists to make NORNR easy to discover, install and evaluate from MCP-native surfaces such as:

• Claude Desktop
• Cursor
• Agent Zero
• OpenClaw / ClawHub
• custom local MCP clients

The governance logic lives in the official NORNR Python SDK:

• SDK repo: NORNR/sdk-py
• Package: nornr-agentpay

The shortest correct reading is:

• one local tool request becomes one NORNR intent
• NORNR decides whether it is approved, queued or blocked
• queued work enters named review with context attached
• the same action still survives into proof, finance packet and audit export later

NORNR is not only the decision layer before execution. It is also the emergency stop layer when a local lane becomes unsafe.

Use it when a desktop or local agent:

• starts looping on tool calls
• reaches a disputed or watched counterparty
• drifts into policy-sensitive actions
• needs to be held in review-only mode while an operator inspects the lane

The right mental model is not "best effort warnings." It is controlled release, controlled pause and controlled recovery.

NORNR is not another MCP tool.

It is the