Skip to main content
Glama
Sign In
Approval Gate MCP

Approval Gate MCP

by itcustomsolution
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to Approval Gate MCP

No user-submitted related servers found.

    Related Servers

    • raposa-mcp

      raposa-mcpofficial

      agentlabbusiness
      A
      license
      A
      quality
      B
      maintenance
      Human approval for AI agents: request_human_approval pauses a high-stakes action until a named person approves or rejects (console, email, Telegram, Slack); silence is not consent. Every decision is sealed in a hash-chained audit log. EU-hosted.
      3
      47 PyPI
      1
      MIT

    • shield-kya

      The-Pixel-Boys
      A
      license
      Not graded
      quality
      B
      maintenance
      A local gate that lets agents submit risky tool actions for policy evaluation and receive ALLOW, DENY, or REQUIRE_APPROVE decisions before executing irreversible side effects. It can also open human approval holds and record an activity trail without executing the side effect itself.
      1,179 npm
      3
      MIT

    • Agent Inbox

      Zijian-Ni
      A
      license
      Not graded
      quality
      C
      maintenance
      A local human-in-the-loop gate for AI agents that blocks actions until human approval, with timeout defaulting to denial.
      31 npm
      MIT

    • final-approval

      finalapproval
      A
      license
      A
      quality
      D
      maintenance
      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.
      1
      1
      MIT
    • @quirna/mcp

      @quirna/mcpofficial

      quirna
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to request human approval before consequential actions, with policy-based routing, phone-based approver decisions, and signed audit evidence.
      40 npm
      MIT
    Deploy Server
    Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

    TDQS

    A4.2/5.0

    Scored across 6 tools

    Disambiguation4/5

    Each tool maps to a distinct lifecycle stage: register, poll, block, enumerate, deny/revoke, and consume. The only fuzzy cluster is check_approval vs wait_for_approval vs consume_approval, all of which report status; the descriptions do explicitly separate them (informational poll vs blocking wait vs single-use authorization), which keeps misselection recoverable but still requires careful reading.

    Naming Consistency4/5

    Five of six tools follow a clean verb_noun pattern (request_approval, check_approval, wait_for_approval, decide_approval, consume_approval). list_pending breaks the pattern by omitting the noun object (implied 'approvals'), a minor deviation but still readable and unambiguous.

    Tool Count5/5

    Six tools is well-scoped for an approval gate: one per lifecycle operation with no redundant entries. Nothing feels padded or missing on the surface.

    Completeness4/5

    Covers the full request-poll-wait-list-decide-consume loop, with the notable and intentional absence of an MCP-side approve (humans approve out-of-band). Minor gap: there is no way to enumerate decided/expired/consumed requests by status, so an agent that lost a request id can only recover via paginated list_pending.

    Maintenance

    ActivityActive
    ResponsivenessSyncing

    Resources