zaharajabeen13-create/ai-rete-rag-mcp

Use ai·rete·rag — deterministic rule-based decisions with
RAG-powered explanations — from Claude Code, Claude Desktop, or any MCP client.
The verdict always comes from the Rete rule engine (auditable, reproducible);
the LLM only explains *why*, grounded in your ingested policy documents.
Tools
| Tool | What it does |
|---|---|
| decide | Make a decision in a domain — structured facts and/or free text, with optional Pattern 01 (rules scope retrieval) and Pattern 02 (retrieval into working memory). as_of reads the policy documents in force on an earlier day |
| get_parameters | The facts a domain's rules decide on (from your account's own rules), most decisive first — what to collect before decide |
| list_rules | Inspect a domain's rules — conditions, verdicts, salience, overlaps |
| get_rule_source | Fetch a domain's rule set as editable YAML |
| import_policy_rules | Turn a written policy document into draft rules, each citing the sentence it encodes (nothing is saved — review, then put_rules) |
| put_rules | Create or replace a domain's rule set from YAML (dry_run to validate) |
| ingest_text | Add policy text to a domain's knowledge base, optionally dated (effective_from, effective_until) or replacing an earlier version (supersedes) |
| list_documents | Browse a domain's ingested documents |
| get_usage | Check your plan and remaining monthly decision quota |
Prompt: decide_case
An agent workflow for deciding a case in any domain on your account, including
your own: it calls get_parameters to learn which facts the rules decide on,
reads the case — text, photos, document scans, voice notes or video (the agent
reads the media itself; the API only receives the facts) — maps it onto those
exact fields, calls decide with fact_sources recording which file each fact
came from (kept in the decision's audit trail), and — while the result's
missing_parameters is non-empty (facts that could still change the verdict)
— asks you for them, most decisive first, and decides again. The verdict always
comes from the rules.
Connect by URL (no install)
The server is also hosted, which is the only route for clients that connect to a
URL and have no field for a static header — claude.ai and Claude Desktop custom
connectors, in particular.
| URL | Auth | Reaches |
|---|---|---|
| https://ai-rete-rag.com/mcp/auth | Sign in with Google, once, in the browser | Your account — your domains, your plan quota |
| https://ai-rete-rag.com/mcp | None, or Authorization: Bearer ik_... | Shared demo domains anonymously; your account with a key |
Add https://ai-rete-rag.com/mcp/auth as a custom connector and approve the
prompt. Connections are listed under **Settings → Connected apps**, and
disconnecting one takes effect immediately.
Install
No install needed with uv — uvx ai-rete-rag-mcp
fetches and runs the server on demand (see the config snippets below).