@decionis/presence-mcp

@decionis/presence-mcp — the Human Approval Gate as an MCP server

A stdio Model Context Protocol server that lets an AI agent pause its consequential tool calls until a named person approves them. It is the Human Approval Gate (docs/48) distributed where agent tool calls happen: every verdict is minted server-side by the Presence API, the exact action is bound into an immutable envelope the approver sees, and each outcome seals a signed Presence Record.

Fail-closed by construction: without a live approver session there is no path to PROCEED that skips the human, and expiry, cancellation, and errors all resolve to DENIED.

Tools

Tool	Purpose
presence_request_human_verification	Hold an action: returns PROCEED/DENIED from a live approver session's server-minted decision, or HUMAN_REQUIRED with the approval_url.
presence_get_verification_status	Poll by request_id to a terminal verdict: PROCEED (with the sealed receipt), DENIED, or ESCALATED.

Run

The tenant key is a server-side secret — run this on the agent's backend host, never in a browser.

PRESENCE_API_KEY=presence_sk_… npx -y @decionis/presence-mcp

Claude Code — .mcp.json at the repo root:

{
  "mcpServers": {
    "presence": {
      "command": "npx",
      "args": ["-y", "@decionis/presence-mcp"],
      "env": { "PRESENCE_API_KEY": "presence_sk_…" }
    }
  }
}

PRESENCE_BASE_URL overrides the API origin (default https://presence.decionis.com).

The loop

• The agent calls presence_request_human_verification with the action, the approver, and a required idempotency_key (reuse the identifier the calling system already has — a payment reference, a workflow id — so a retry cannot seal two records).
• On HUMAN_REQUIRED, hand approval_url to the approver — email, chat, calendar, or QR.
• Poll presence_get_verification_status until the verdict is terminal, then act on it. Treat DENIED and errors as refusals.

Discovery

Described for crawlers and agent hosts at presence.decionis.com/.well-known/mcp.json; registry manifests (server.json, smithery.yaml, glama.json) live beside the package in the repository.