New One-call approvals are live in the console
Developers

One address. Every client you already use.

Claude, ChatGPT, Cursor, your own agents, a CLI, a desktop app — every one of them reaches the same address and the same approval screen. You set your apps up once, not once per vendor.

~/.cursor/mcp.json
{
  "mcpServers": {
    "govna": {
      "url": "https://agw.govna.io/mcp"
    }
  }
}
01 Authorization

An ordered OAuth and consent sequence

Every client goes through the same six steps, in the same order, before a single tool can be used.

  1. 01 Finding the sign-in details The client looks up how to sign in to Govna.
  2. 02 Starting sign-in A standard OAuth sign-in begins, in the browser, as a person.
  3. 03 Protecting the exchange PKCE secures the handoff so it cannot be intercepted in transit.
  4. 04 Checking the address We confirm the request is for this exact service before showing anyone an approval screen.
  5. 05 Picking what to allow A person sees the request and chooses the logins, the tools and the time limit.
  6. 06 Opening the session Their decision opens one session, limited to exactly what they picked.
03 Audit

Every governed call becomes a signed event

Send governance events where you already watch. Each receipted call is delivered as a signed CloudEvents webhook, in order, with bounded retries until your endpoint acknowledges it.

POST /webhooks/govna
{
  "specversion": "1.0",
  "id": "01J9WZ4N8QK7",
  "type": "io.govna.call.receipted",
  "source": "govna/audit",
  "subject": "session-2214",
  "time": "2026-08-25T14:03:07Z",
  "datacontenttype": "application/json",
  "data": {
    "tool": "search_records",
    "outcome": "allowed",
    "receipt": "receipt-1041"
  }
}
Next step

Where to go next

Two readers, two different next steps.

Security leader

See what a security review actually asks.

Platform engineer

See the full endpoint, transport and consent reference.