Skip to main content
Glama
CTRLRun

CTRLRun Approval Console

Official
by CTRLRun
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to CTRLRun Approval Console

  • Approval Gate

    Keldrik
    A
    license
    Not graded
    quality
    D
    maintenance
    Provides a human approval gate for AI agents, enabling interactive inline cards for approving, editing, or rejecting actions before they are executed.
    MIT

  • agent-mandate-mcp

    API-Disk-Integrations
    A
    license
    A
    quality
    C
    maintenance
    Verifies agent actions against mandates via a single tool, returning allow, deny, or requires_approval receipts without executing the actions.
    1
    MIT

Related Servers

  • @cqnce/mcp-server

    cqnce-app
    A
    license
    A
    quality
    C
    maintenance
    Exposes cQnce human-in-the-loop authorization as MCP tools, letting AI agents request and await human approval for risky actions. Includes request submission, monitoring, and project/team management capabilities.
    6
    7 npm
    1
    MIT

  • confirm-mcp

    confirm-ai
    A
    license
    A
    quality
    C
    maintenance
    Provides a human-approval tool for MCP-compatible agents, pausing execution until a human approves or edits the action, with every decision logged.
    2
    2 npm
    2
    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
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.2/5.0

Scored across 8 tools

Disambiguation5/5

Each tool maps to a distinct resource or workflow step: pending list, approval/denial mutations, action history, raw receipts, effect states, aggregate stats, and effect resolution. No two tools are interchangeable, and the descriptions explicitly direct agents to the right one.

Naming Consistency3/5

Names split between bare verbs (approve, deny, resolve), verb-noun read commands (list_pending_approvals, inspect_action), and bare plural nouns for data views (receipts, effects, stats). They are readable and meaningful, but the naming convention is not uniformly predictable.

Tool Count5/5

Eight tools fit the approval-console domain well: write operations are covered by approve, deny, and resolve, while read-side views cover pending items, per-action history, raw receipts, effects, and statistics. No tool feels redundant or missing as filler.

Completeness5/5

The tool set covers the full workflow: identify pending requests, decide them, inspect full action history, inspect effect outcomes, and record resolutions that unblock retries. Auditing is supported through receipts and stats, so there are no obvious dead ends.

Maintenance

ActivityNo data
ResponsivenessWithin a week

Resources