About final-approval
final-approval is an MCP server in the Communication category: human-in-the-loop approval gate for AI agents. Your agent calls submit_approval before any irreversible action; a human reviews on a branded page; a signed webhook fires back with the decision. It has been installed 0 times through Conduid.
Install
git clone https://github.com/finalapproval/final-approval-mcpThis server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.
Ask AI
Ask AI about final-approval
Powered by Claude · Grounded in docs
Security checks
- ·README presentNot checked yet.
- ·License declaredNot checked yet.
- ·Tests presentNot checked yet.
- ·Dependencies pinnedNot checked yet.
- ·No dynamic code executionNot checked yet.
- ·Scoped permissionsNot checked yet.
README
FinalApproval MCP Server
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.
Scope
v0.1 exposes one tool:
| Tool | Status | Notes |
|---|---|---|
submit_approval |
✅ shipped | Creates a pending approval. Webhook fires on resolution. |
wait_for_resolution |
planned | Blocked on public GET /api/v1/approvals/:id. Use webhook today. |
list_pending |
planned | Blocked on public GET /api/v1/approvals. |
get_approval |
planned | Blocked on public GET /api/v1/approvals/:id. |
For the full tool surface today, use the hosted endpoint at https://www.finalapproval.ai/mcp (OAuth 2.1, scope approvals:write).
Setup
- 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.
Claude Code / Cursor (Node)
npx -y @finalapproval/mcp-server
Config snippet (Claude Code ~/.claude.json):
{
"mcpServers": {
"finalapproval": {
"command": "npx",
"args": ["-y", "@finalapproval/mcp-server"],
"env": {
"FINALAPPROVAL_API_KEY": "fa_..."
}
}
}
}
Docker
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 ..)
Environment variables
| Var | Required | Default | Purpose |
|---|---|---|---|
FINALAPPROVAL_API_KEY |
yes | — | Channel API key (starts with fa_) |
FINALAPPROVAL_URL |
no | https://www.finalapproval.ai |
Override for self-hosted / dev |
Closing the loop
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.
Development
npm install
npm run build
FINALAPPROVAL_API_KEY=fa_... npm start
License
MIT
README mirrored from the source repository 4 months ago. The original is authoritative.