Standalone Model Context Protocol server for FinalApproval — gate AI agent actions behind a human approval.
Your agent calls submit_approval; a human reviews on a branded page in your FinalApproval dashboard; the channel's configured webhook fires back when the human decides.
This is the stdio variant intended for local / headless / CI / directory-indexed (Glama) use. If you want the hosted OAuth-gated Streamable-HTTP server instead, point MCP clients at https://www.finalapproval.ai/mcp.
v0.1 exposes one tool:
Tool | Status | Notes |
| ✅ shipped | Creates a pending approval. Webhook fires on resolution. |
| planned | Blocked on public |
| planned | Blocked on public |
| planned | Blocked on public |
For the full tool surface today, use the hosted endpoint at https://www.finalapproval.ai/mcp (OAuth 2.1, scope approvals:write).
Related MCP server: Approval Gate
Sign in at finalapproval.ai and create a channel. Copy its API key (starts with fa_) and configure a webhook URL.
Run the MCP server with the API key in FINALAPPROVAL_API_KEY.
npx -y @finalapproval/mcp-serverConfig snippet (Claude Code ~/.claude.json):
{
"mcpServers": {
"finalapproval": {
"command": "npx",
"args": ["-y", "@finalapproval/mcp-server"],
"env": {
"FINALAPPROVAL_API_KEY": "fa_..."
}
}
}
}docker run --rm -i \
-e FINALAPPROVAL_API_KEY=fa_xxx \
ghcr.io/finalapproval/final-approval-mcp:latest(Published image coming; you can also build locally: docker build -t finalapproval-mcp ..)
Var | Required | Default | Purpose |
| yes | — | Channel API key (starts with |
| no |
| Override for self-hosted / dev |
submit_approval returns immediately with a pending approval ID. The actual decision arrives via the channel's webhook, not back through MCP. Your host application (the agent's server) must implement a webhook receiver that verifies the HMAC signature and executes the gated action on approved or logs on denied. See the FinalApproval docs for webhook payload schema.
npm install
npm run build
FINALAPPROVAL_API_KEY=fa_... npm startMIT
Create a pending approval in the FinalApproval channel whose API key is configured in this MCP server. The channel's webhook fires when the human approves or denies. Use this before any irreversible agent action (sending email, merging a PR, publishing a post, running a migration, etc).
Inputs: title (required), body (required), data.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool has a clear and distinct purpose for submitting approvals.
The tool name 'submit_approval' follows a clear verb_noun pattern. Since there is only one tool, consistency is inherently perfect with no deviations or mixed conventions.
A single tool is too few for most practical server purposes, as it severely limits functionality and scope. While it might serve a narrow use case, it feels thin and incomplete for typical agent workflows.
The server's domain appears to be approval workflows, but with only a submit tool, there are significant gaps. Missing operations likely include checking approval status, listing pending approvals, or handling approvals programmatically, which could cause agent failures.
Set up human approval for your AI agents' tool calls.
Give any AI agent a way to ask a person — for approval, a decision, an answer or a review.
Supervised API-write gateway for AI agents with policy, human approval and execution receipts.
Human approvals, notifications, inbound webhooks, wake-ups for headless agents. Free trial: /try
