AgentRaaS wrap

السجل الرسمي الأمن

Wraps any MCP server: identical write-tool calls run once, and every tool call is audit-logged.

ماذا يمكنك أن تفعل مع AgentRaaS wrap؟

  • protect_tool for LangChain/LangGraph and CrewAI, protectTools for the
  • agentraas wrap -- <mcp server> gives any MCP server exactly-once write
  • agentraas scan lists which tools in your MCP servers can move money,
  • The chaos tester exits non-zero, so it can fail CI (GitHub Action).

التثبيت

أضف هذا إلى إعدادات MCP في عميلك (Claude Desktop: claude_desktop_config.json، وCursor: ‏.cursor/mcp.json، ويستخدم VS Code وغيره الصيغة نفسها «mcpServers»).

PYPI package agentraas
Claude Code
claude mcp add agentraas-wrap -- uvx agentraas==0.14.0 wrap -- '<mcp_server_command>'
إعداد JSON (Claude Desktop وCursor وVS Code)
{
    "mcpServers": {
        "agentraas-wrap": {
            "command": "uvx",
            "args": [
                "agentraas==0.14.0",
                "wrap",
                "--",
                "<mcp_server_command>"
            ]
        }
    }
}

التوثيق

مأخوذ من ملف README للمشروع على GitHub ويُحدَّث أسبوعيًا. تفتح الروابط على GitHub.

المحتويات
  1. AgentRaaS
  2. The problem
  3. How it works
  4. Free tools, no server needed
  5. Self-host
  6. What you get
  7. Why not just idempotency keys?
  8. When AgentRaaS is down
  9. Pricing
  10. Testing
  11. Next
  12. Docs and license

AgentRaaS

The reliability layer for what AI agents do.

AgentRaaS sits between your agents and the APIs they act on. Every call runs once even when it is retried, is checked against what that agent may do, waits for a human when it is risky, and is recorded. Connect by webhook URL, SDK headers or MCP. The core is open source and free to self-host.

Look first: live read-only demo, no signup. Built-in services include Stripe, Slack, GitHub, HubSpot, Resend, SendGrid, Notion, Zendesk, Jira, Twilio, Shopify and Alpaca (trading); any other HTTP API works as a Custom Action and any MCP tool through agentraas wrap.

The problem

Your n8n workflow calls Stripe. It times out, n8n retries, and the customer is charged twice. Your agent creates a HubSpot contact, the response is lost, the agent retries, and now there are two.

How it works

flowchart LR
    Agent["Agent<br/>(n8n, Python, MCP)"] -->|request| P
    subgraph P["AgentRaaS"]
        direction TB
        D["Deduplicate"] --> V["Policies and validation"] --> C["Circuit breaker"] --> A["Audit log"]
    end
    P -->|forwarded once| API["API<br/>(Stripe, Twilio, HubSpot, any URL)"]
  1. Your agent calls AgentRaaS instead of the API.
  2. AgentRaaS claims a dedup slot in Redis for that exact request.
  3. The first call is forwarded and its result stored.
  4. A retry gets the stored result, or 409 while the first is still in flight.

A call that times out after it was sent is treated as outcome unknown: never retried, its slot kept, sent to the dead-letter queue. Every forwarded call also carries Idempotency-Key: agentraas-<hash>, so providers that honor it (Stripe and others) run it once even on a replay.

Free tools, no server needed

pip install agentraas runs entirely on your machine.

agentraas chaos --mock -- python my_agent.py   # find calls that would run twice
from agentraas.local import exactly_once

@exactly_once()
def charge(customer, amount, idempotency_key=None):
    return stripe.Charge.create(customer=customer, amount=amount, idempotency_key=idempotency_key).id
  • protect_tool for LangChain/LangGraph and CrewAI, protectTools for the Vercel AI SDK (npm install agentraas).
  • agentraas wrap -- <mcp server> gives any MCP server exactly-once write tools and a log. In the official MCP Registry.
  • agentraas scan lists which tools in your MCP servers can move money, delete data, run code or send messages, without calling any of them (GitHub Action for pull requests).
  • The chaos tester exits non-zero, so it can fail CI (GitHub Action).

Details: src/sdk/README.md, src/sdk-js.

Self-host

git clone https://github.com/agentraas/agentraas.git
cd agentraas
./install.sh

install.sh generates the secrets, builds the image (the first Rust build takes a few minutes), starts Postgres, Redis and MinIO, and runs the migrations. Then open http://localhost:13000/dashboard and register. Kubernetes: a Helm chart is in infra/helm/. Render: one-click deploy.

Works with Docker or Podman. Linux: either one. macOS: Docker Desktop (or Colima). Windows: Docker Desktop with WSL2; run ./install.sh from a WSL terminal, with the repo cloned inside WSL (not on C:\).

On SELinux hosts, install.sh relabels the bind mounts. After changing files by hand, recreate (docker compose or podman-compose, down then up -d) rather than restart.

What you get

  • Runs once: dedup across retries and machines, near-duplicate matching, step checkpoints, a cross-agent resource lock.
  • Policies: what each agent may call and where it may send data, allowed hours in any time zone, validation rules, call and money caps per hour or day, loop limits. Quoted numbers ("5000") are held to the same limits.
  • One key per agent: works for every service you connect; switch services off per key.
  • Human approval: risky calls wait for approve or deny from the dashboard, Slack, or a one-time link sent to Teams, Telegram, Discord or email, with escalation.
  • Resilience: circuit breaker, rate limits, dead-letter queue with replay.
  • Undo: an action that ran can be reversed from the dashboard for 30 days (Stripe charge refunded, Slack message deleted, or your own reverse action), exactly once.
  • Audit and identity: tamper-evident log, SIEM export, OpenTelemetry and Prometheus, short-lived scoped agent tokens.
  • Data safety: PII redaction, prompt-injection filtering on tool output, schema drift alerts.
  • Keys: stored service keys are encrypted (AES-256-GCM); self-hosted, the master key can live in Vault, AWS KMS, Google Cloud KMS or Azure Key Vault, and Enterprise can leave service keys in your own secrets manager and have them fetched per call (docs).
  • Teams: OIDC SSO, roles, client tenants with white-label branding.

Curated services (Stripe, Twilio, HubSpot, Shopify, Slack, PayPal, Alpaca paper and live trading and more in config/services.json), or register any URL as a Custom Action, SSRF-guarded. Guardrails for trading agents: agentraas.io/trading.

Why not just idempotency keys?

If you only call Stripe from your own code, its Idempotency-Key is enough. AgentRaaS is for the rest: providers without one (most SaaS APIs and every internal endpoint), no-code tools that can't set headers (n8n, Make, Zapier), and one audit trail across every service an agent touches.

When AgentRaaS is down

It fails closed. Nothing in the SDKs, the n8n node or the MCP gateway falls back to calling the API directly, because that is exactly the unguarded retry this product exists to stop. Treat it like a database on your critical path.

Latency: 2.1 to 2.4 ms added at the median, 2.9 to 3.7 ms at p95, measured on one machine (Intel Core i3-12100, local stack, three runs of 500 calls) with infra/scripts/bench-overhead.py. A retried duplicate is answered from cache.

Pricing

Self-hosted (Community + Team)Enterprise
PriceFree, no license keyTalk to us
LimitsNo action limit, up to 3 seatsUnlimited seats
IncludesExactly-once execution, MCP gateway, dashboard, audit trail, DLQ, undo, record and replay, spend caps and action policies, DLP redaction, human approvals, semantic dedup, SSOEverything in Self-hosted, plus agent identity, inbound webhooks, white-label branding, service keys read from your own secrets manager

AgentRaaS Cloud starts with a free trial of 1,000 actions with every feature, for trying it out; for production, self-host. The core server is AGPL-3.0; the Team and Enterprise features are source-available (see LICENSE.md).

Testing

cd src/api-gateway-rs
cargo test --workspace --features enterprise          # unit tests
TEST_BASE_URL=http://localhost:13000 npm test         # integration tests, real server

The integration tests send concurrent duplicates, replays and failures through the built-in mockpay service, so no real API keys are needed.

Next

  • Verify the undo log against real Stripe and Slack accounts (tested with mockpay so far).
  • The n8n node in n8n's community directory (in review).

Docs and license

agentraas.io/docs has the API, the troubleshooting guide and self-hosting details. Questions: agentraas.io/community (GitHub Discussions).

The server is AGPL-3.0. The Team and Enterprise features (crates/api/src/ee/, crates/core/src/{semantic_dedup,hmac_verify}.rs, compose.ee.yaml) are source-available under the AgentRaaS Enterprise License from 0.16.0: free to read and try, production use needs a license key (releases 0.10.0 to 0.15.1 stay under the Functional Source License). The SDKs are MIT/Apache-2.0. See LICENSE.md.

CONTRIBUTING.md · SECURITY.md (report vulnerabilities privately, not as issues) · CODE_OF_CONDUCT.md

Built with Rust (Axum, Tokio, sqlx), Postgres and Redis.

الأسئلة الشائعة

ما هو AgentRaaS wrap؟

Wraps any MCP server: identical write-tool calls run once, and every tool call is audit-logged.

كيف أثبّت AgentRaaS wrap؟

يعمل على جهازك. في Claude Code: claude mcp add agentraas-wrap -- uvx agentraas==0.14.0 wrap -- '<mcp_server_command>'. وفي العملاء الآخرين، الصق إعداد JSON من هذه الصفحة في إعدادات MCP الخاصة بهم.

هل يحتاج AgentRaaS wrap إلى مفتاح API؟

لا يذكر إدراجه في السجل أي مفتاح أو سر إلزامي. قد تتطلب بعض الميزات حسابًا لدى الخدمة التي يتصل بها.

هل AgentRaaS wrap مفتوح المصدر؟

شيفرته علنية على GitHub، لكن المستودع لا يعلن ترخيصًا قياسيًا.

من يصون AgentRaaS wrap؟

ينشره agentraas. يدرجه AI.tn لكنه لا يصونه ولا يوصي به.

من سجل MCP الرسمي. الإدراج ليس توصية: راجع شيفرة الخادم وصلاحياته قبل منحه الوصول إلى بياناتك.