A
licenseNot graded
qualityD
maintenanceAdds a human-in-the-loop checkpoint to MCP-capable AI coding agents, enabling them to pause and request user feedback before executing actions.
13 npm
72
MIT
confirm-mcp
by confirm-ai
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@confirm-mcp request approval to refund $500 to customer 78910"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
confirm-mcp
An MCP server that gives any MCP-compatible agent (Claude Desktop, Cursor, and others) a human-approval tool. Before the agent does something irreversible, it calls request_approval, a human approves or edits the action at confirm.dev, and the agent proceeds with the approved result. Every decision is logged.
Setup
Get an API key at confirm.dev, then add the server to your MCP client config.
Claude Desktop (claude_desktop_config.json):
{
"mcpServers": {
"confirm": {
"command": "npx",
"args": ["-y", "confirm-mcp"],
"env": { "CONFIRM_API_KEY": "cfm_live_..." }
}
}
}That's it. The agent now has two tools.
Related MCP server: call-a-human-mcp
Tools
request_approval
Pause and ask a human to approve a sensitive action. Blocks until the human decides or the wait elapses.
Input | Description |
| One line the human reads, e.g. "Refund $10,000 to customer #4821". Required. |
| Approver email, or |
| The exact action as structured data. The human can edit it before approving. |
| Why the agent wants to do this. |
| The agent's recent steps, for context (max 10). |
| How long the request stays valid (5 to 10080). |
| How long to block before returning "pending" (default 15). |
On APPROVED, the tool returns the effectivePayload to use (the human may have edited it). On REJECTED or EXPIRED, it tells the agent to stop. If the wait elapses while still pending, it returns the request id so the agent can poll later.
check_approval
Poll a previously created request by id to see whether a human has decided.
Why a tool, not a prompt
The approval is enforced server-side: the agent cannot fake a verdict, and every decision is recorded in an immutable audit log. Teaching the agent when to call this (via a system prompt or an agent skill) is the coverage layer; the tool is the enforcement layer.
For production agents where you need guaranteed coverage of specific actions, use the deterministic policy engine in @confirm/sdk (guard()) rather than relying on the model to remember to call the tool.
Docs: confirm.dev/docs. Node 18+.
Development
This package is developed in a private monorepo alongside the Confirm.dev service and mirrored here on every release, which is why the history starts at the first public release. Issues and PRs are welcome; PRs get cherry-picked upstream.
Build: npm install && npm run build. Test: node smoke.mjs (after a build; uses a mocked client, no network).
Available Tools
2 toolscheck_approvalCheck a pending approvalA
Poll a previously created approval request by id to see if a human has decided yet.
Inputs: id (required).
request_approvalRequest human approvalA
Pause and ask a human to approve a sensitive or irreversible action before you perform it (refunds, deletes, deploys, outbound messages, spending money). Blocks until the human approves, rejects, or the wait elapses. If APPROVED, use the returned effectivePayload exactly (the human may have edited it). If REJECTED or EXPIRED, do not perform the action.
Inputs: notify (required), summary (required), payload, reasoning, +4 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
A4.2/5.0
Scored across 2 tools
Disambiguation5/5
The two tools have clearly distinct purposes: one initiates an approval request and blocks, the other polls an existing request's status. There is no overlap or ambiguity between them.
Naming Consistency5/5
Both tool names follow the consistent verb_noun pattern (request_approval, check_approval), using snake_case and parallel structure. This is a predictable and coherent naming convention.
Tool Count4/5
With only 2 tools, the server is slightly under the typical 3-15 range, but the scope is highly focused on approval workflows. Both tools are essential and the count does not feel excessive or severely lacking.
Completeness4/5
The core lifecycle of approval is covered: creating a request and checking its status. A possible gap is cancellation of an approval request, but the blocking behavior of request_approval partially mitigates this, so the missing functionality is minor.
Maintenance
ActivityInactive
ResponsivenessOutdated data
Related MCP Connectors
Set up human approval for your AI agents' tool calls.
Human-in-the-loop for AI agents over MCP: durable approvals with a hosted review page & audit trail
Preventive human-approval write-gate for AI agents: writes commit only after a human approves.
Human-in-the-loop review and approval for AI agents. Audit trail, approval policies, native MCP.
Related MCP Servers
- AlicenseAqualityAmaintenanceAn MCP server that enables AI agents to pause and request human approval or information via Slack, Telegram, or macOS dialogs before proceeding with actions.215Apache 2.0
- FlicenseNot gradedqualityCmaintenanceProvides a secure MCP boundary for AI agents, intercepting and validating tool calls, redacting secrets, and requiring human approval for sensitive actions with a tamper-evident audit trail.-
- AlicenseNot gradedqualityCmaintenanceMCP server that provides human-in-the-loop approval for risky AI agent actions, with durable state and audit logs.MIT