Generate the MCP control server stanza before local tool execution becomes a blind spot.

Choose the MCP client, keep the server name narrow, and copy the ready-to-paste config. NORNR still decides approved, queued or blocked before the local action reaches provider spend or vendor consequence.

This generator is intentionally small: one client, one server stanza, one default rollout pack and one local lane to govern first.

Generator

One config, one command path, one default rollout posture.

If this is hard to generate, MCP remains interesting but not ambient.

1 / Client

Choose the MCP client

MCP client Server name Agent id Auth path (optional)

2 / Install

Install and authenticate once

bash

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

Use the hosted path first, then let the config stanza point the local client at the same control plane.

3 / Config

Paste the control server stanza

Paste this into Claude Desktop's MCP settings.

json

4 / Serve

Run the server locally

bash

The config points to this command path, so the client can ask NORNR before consequential tool execution continues.

Default rollout pack

mcp-local-tools-guarded should be the obvious first posture.

Start in shadow or review-first mode, then prove one local tools lane before widening autonomy.

Pack shape

Review-first posture for consequential local tools

Use it when desktop or local agents can reach paid providers, external services or risky automation surfaces.

What it protects

Counterparty, threshold and review ownership stay explicit

The pack matters because it preserves mandate, reviewer and export posture for local actions too.

Next move

Replay once, then enforce one lane

Use policy replay or the control room to show what would queue or block before you rely on local autonomy.