REST API vs MCP for Human-in-the-Loop Approval

Description and use

An automated agent uses Impri’s REST API or MCP to request human approval before merging a PR, ensuring safe side effects.

Problem

How to gate an automated merge action with human approval using Impri’s REST API or MCP server.

Outcome

Using Impri’s REST API or MCP, agents can safely gate merge actions with human approval, reducing risk of accidental merges.

Workflow

• 1. Agent identifies PR to merge.
• 2. Agent sends merge request to Impri via REST or MCP.
• 3. Impri creates an action and notifies the inbox.
• 4. Human reviews the action and approves or rejects.
• 5. Agent polls (REST) or receives result (MCP) and proceeds if approved.
• 6. Agent performs GitHub merge and reports execution to Impri.

Evidence

Both hit the same https://api.impri.dev backend and the same inbox. The difference is ergonomics, not security.

Source

The agent calls a tool, the tool blocks until a decision exists, the agent receives the result and continues.

Source