How to add the NORNR MCP control server to Cursor.

1. Why Cursor needs more than raw MCP capability

Cursor can already make local coding agents useful. The issue starts when raw local tool access also implies raw spend, vendor authority or policy-sensitive execution. Capability alone is not the control model.

NORNR turns the local tool request into an intent, decides whether it should proceed, and keeps the resulting action attached to one review and export path later.

2. Install and authenticate once

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

3. Generate the Cursor MCP config

nornr mcp cursor-config --server-name nornr --agent-id cursor-agent

Paste the resulting stanza into Cursor's MCP configuration, or use the MCP config generator if you want the same output through a guided surface.

4. Pick one first local tools lane

The strongest first lane is one action a coding agent can already reach inside the IDE.

• a tool path that triggers a paid model or provider request
• a local task that can create vendor-side consequence
• a coding workflow that should queue above a threshold instead of running fully autonomously

Start from mcp-local-tools-guarded so the posture is explicit from the first rollout.

5. What Cursor gets through the control server

• nornr.check_spend and nornr.request_spend before the local tool call clears
• nornr.pending_approvals, nornr.approve_spend and nornr.reject_spend for the review path
• nornr.review_bundle, nornr.intent_timeline and nornr.finance_packet for proof and handoff

6. The simple buyer-safe lane

1. Cursor proposes one consequential tool action.
2. NORNR decides approved, queued or blocked.
3. Queued work lands in one review owner path.
4. The same action survives into proof and finance export later.

That makes Cursor part of the same control model as the rest of NORNR instead of a local blind spot.

7. Where to go next

• Open the MCP control server package
• Use the MCP config generator
• See the canonical proof path