Approval Rules

com.botrecipePublished by botrecipe.comv1.0.0Updated Oct 24, 2026

Auto-approve small agent actions under your rules; approval cards for the rest.

The publisher's own server: Approval Studio

Overview

AI-generated overview

Lets an assistant auto-approve small actions under your rules and ask for approval on the rest.

What you can do
Lets an assistant check your rules before a consequential action. check_action returns auto-approve, needs-approval (with a plain-English approval card and a tappable link) or deny; get_decision confirms whether the user approved or rejected a card; set_rules and get_rules manage the rules; weekly_report drafts a read-only summary of the last seven days.
When to use it
Use it when an assistant performs consequential actions on your behalf and you want small, reversible ones to proceed automatically while the rest wait for your approval.
Requirements
Remote endpoint; no local runtime. An API key is needed to save rules. Free tier allows 200 calls per day.
Before you install
The free plan is watch-only: it reports and logs what it would decide but nothing takes effect. Approval cards include a link the user can tap, so check that rules and amount limits match your intent. The All Access upgrade is paid.

Installation

In SourceWeft

  1. Open Approval Rules in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.botrecipe%2Fapprove/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "approval-rules": {
      "type": "http",
      "url": "https://approve.cloudforbots.com/mcp"
    }
  }
}

Tools

6

check_action

Before a consequential action, ask whether the user's rules auto-approve it. Returns auto_approve, needs_approval (with a plain-English approval card and a link the user can tap) or deny. Free plan is watch-only: it reports what it WOULD decide and logs it for the weekly report, but nothing counts as approved, so ask your user as you normally would.

Parametersactionrequired

get_decision

Check whether the user approved or rejected an approval card (by card_id and card_token). Only act when status is approved.

Parameterscard_idrequiredcard_tokenrequired

set_rules

Save the user's rules (needs an API key so they stay yours). Each rule: {name, when:{type:[...], max_usd, min_usd, reversible, target_ends_with:[...]}, verdict:"auto"|"ask"|"deny"}. First matching rule wins; anything unmatched needs approval. Call once without confirm to preview, then with confirm=true.

Parametersrulesrequiredconfirm

get_rules

Show the rules in effect for your key (or the default starter rules).

Takes no parameters.

weekly_report

Draft a plain-English report of the last 7 days: actions checked, how many your rules would auto-approve, how many needed you, top kinds of asks, and rule suggestions. Read-only; sends nothing.

Takes no parameters.

usage_and_upgrade

Show today's usage for your key or IP and the $49/month All Access upgrade link (cloudforbots.com/offer). Free tier: 200 calls/day. Not metered.

Takes no parameters.

Version history

1
  1. v1.0.0LatestOct 15, 2026

Score

72% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Approval integrations