convez.ai
MCP ServerAutomaçãoAvançado
zavora-ai

Approval MCP Server

zavora-ai/mcp-approval

Fluxos de aprovação multi-estágio com quórum, delegação e auditoria

Ver no GitHub
InicialPluginScore · de 0 a 100

Motor de fluxos de aprovação multi-estágio para agentes de conteúdo legal e mídia. Suporta regras de decisão (quórum, sequencial, sign-off), delegação, escalação e trilha de auditoria imutável em Rust, com 17 ferramentas MCP.

Instalação

$npx convez-ai zavora-ai/mcp-approval

1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.

Métricas

Estrelas
1
Forks
0
Acompanhando
0
Saúde
50%
Último commit
há 3 meses
Versão
v1.0.0
Issues abertas
1
Contribuidores
1

Casos de uso

  • Aprovações de consentimento de conselho (quórum de diretores)
  • Revisão sequencial de contratos (Legal → Finanças → Executivo)
  • Conformidade de conteúdo e brand compliance
  • Limpeza de direitos e autorização legal
  • Portões de QA editorial antes de publicação

Veredito

Solução robusta e bem-arquitetada para orquestração de aprovações complexas em contextos legais e de mídia. Implementação em Rust garante performance; o design de trilha de auditoria imutável atende rigorosamente compliance.

README

A tradução para o português deste README ainda está na fila.

Approval MCP Server

Crates.io License ADK-Rust Enterprise Registry Ready

A multi-stage approval workflow engine for ADK-Rust Enterprise legal and media-content agents. 17 MCP tools: configurable workflow templates, stage rules (all-of / any-of / quorum), decisions with delegation and escalation, SLA/expiry clocks, and an immutable audit trail on every action.

Yes — this is the approval-workflow server

An approval system is a workflow engine. One model — an ApprovalRequest moving through an ordered set of Stages, each with a decision rule and eligible approvers — serves every agent below. The variety is in the routing, not the mechanics.

DomainAgentTypical workflow shape
LegalBoard Consent Draftersingle stage, quorum (N-of-M directors)
LegalContract Review Agentsequential Legal → Finance → Exec
LegalPolicy Compliance Reviewercompliance sign-off gate
MediaBrand Compliance Reviewerbrand any-of review
MediaContent Localization Agentlinguistic QA → in-country review
MediaPublishing QA Agenteditorial QA gate
MediaRights Clearance Assistantrights review → legal clearance
MediaSocial Post Producerfast content review before publish

Architecture

Core Concepts

  • Workflow template — a reusable, ordered list of stages for a request type. Eight defaults ship (one per agent above); create your own with create_workflow.
  • Stage rule — how a stage resolves from its votes:
    • all_of — every eligible approver must approve
    • any_of — one approval advances
    • quorum — at least N approvals (e.g. 3 of 5 directors)
  • Decision — approve · reject · request_changes · abstain. A reject fails the request; request-changes bounces it back to the requester for resubmission.
  • Delegation — an approver can delegate authority; the delegate's vote is recorded on behalf of the original (preserved in the audit trail).
  • Escalation — reassign the active stage to new approvers (e.g. on SLA breach).
  • Audit trail — every mutation appends an immutable entry (actor, action, timestamp). Essential for board consents and legal sign-offs.

Tools (17)

Agentic (2)

ToolWhat It Does
intake_and_routeCreate and submit a request in one step, auto-selecting the default workflow for the type
request_statusConcise status: workflow position, approvals vs. needed, outstanding approvers, next step

Workflow Templates (3)

ToolWhat It Does
list_workflowsList templates (optionally by domain)
get_workflowGet a template's full stage definitions
create_workflowDefine a custom workflow (stages, rules, approvers, SLAs)

Requests & Lifecycle (6)

ToolWhat It Does
create_requestOpen a request bound to a workflow (optionally submit)
get_requestFull detail: stages, votes, comments, attachments, audit
search_requestsFilter by text, domain, type, status, approver
submit_requestRoute a draft for review (activate first stage)
cancel_requestWithdraw a request (gated)
escalateReassign the active stage to new approvers (gated)

Decisions & Collaboration (6)

ToolWhat It Does
decideRecord a decision on the active stage; evaluates the rule (gated)
my_queueRequests awaiting a given approver
delegateDelegate approval authority for a request (gated)
add_commentComment on the request thread
add_attachmentAttach a document/evidence reference (by URI)
get_audit_trailImmutable record of who did what, when

Example — board written consent (quorum 3 of 5)

> intake_and_route(domain: "legal", request_type: "board_consent",
    title: "Approve 2026 budget", requester: "secretary", subject_ref: "consent:BUDGET-2026")
  → routed AR-1003 · active stage "Board Vote" (quorum)

> decide(id: "AR-1003", approver: "dir.1", decision: "approve")   → in_review (1 of 3)
> decide(id: "AR-1003", approver: "dir.2", decision: "approve")   → in_review (2 of 3)
> decide(id: "AR-1003", approver: "dir.3", decision: "approve")   → approved  (quorum met)

> get_audit_trail(id: "AR-1003")
  → created · submitted · decision ×3 · stage_approved · approved

Example — contract review (sequential, with delegation)

> create_request(request_type: "contract_review", title: "MSA with Acme",
    requester: "legalops", subject_ref: "contract:MSA-ACME", submit: true)
  → AR-1010 · stage "Legal Review"

> delegate(id: "AR-1010", from: "legal.counsel", to: "legal.associate", reason: "OOO")
> decide(id: "AR-1010", approver: "legal.associate", decision: "approve")
  → advances to "Finance Review"  (vote recorded on behalf of legal.counsel)

Installation

1. Build

git clone https://github.com/zavora-ai/mcp-approval
cd mcp-approval
cargo build --release

2. Add to your MCP client

Claude Desktop / Kiro / Cursor / Windsurf:

{
  "mcpServers": {
    "approval": {
      "command": "/path/to/mcp-approval"
    }
  }
}

3. Use it

> list_workflows(domain: "media_content")
> intake_and_route(domain: "media_content", request_type: "social_post",
    title: "Launch thread", requester: "social.producer", subject_ref: "post:LAUNCH-01")

Governance & Data Handling

  • Gated writes — decide, cancel_request, escalate, and delegate require approval in production (requires_approval); reads are read_only.
  • Defensible audit — every state change is recorded immutably with actor and timestamp.
  • No raw documents — items under approval and attachments are opaque references/URIs, never embedded content.
  • Integration scaffold — the in-memory store is for development; back it with a durable store and bind approver/actor to authenticated identities in production.

MCP Server Manifest

server_id = "mcp_approval"
display_name = "Approval Workflows"
version = "1.0.0"
domain = "governance"
risk_level = "high"
writes_allowed = "gated"
transports = ["stdio"]

Contributors

James Karanja Maina

License

Apache-2.0 — see LICENSE for details.


Part of the ADK-Rust Enterprise MCP server ecosystem.

Registry Compliance

This server implements the ADK MCP SDK contract:

  • HealthCheck — async health probe for registry monitoring
  • mcp-server.toml — manifest declaring tools, risk classes, and approval gates
  • Structured tracing — RUST_LOG env-filter for observability
Ver o original no GitHub

Bom para

Relacionados