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:

For the full tool surface today, use the hosted endpoint at https://www.finalapproval.ai/mcp (OAuth 2.1, scope approvals:write).

Setup

1. Sign in at finalapproval.ai and create a channel. Copy its API key (starts with fa_) and configure a webhook URL.

2. 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

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