Ai·rete·rag vs Moxie Docs MCP
A side-by-side look at the Ai·rete·rag and Moxie Docs MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Ai·rete·rag for knowledge & memory work as a local process; choose Moxie Docs MCP for knowledge & memory as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Ai·rete·rag when
- You need dedicated capabilities in the Knowledge & Memory domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
AI_RETE_RAG_API_KEY, AI_RETE_RAG_API_URL. - You want tools like
decide, get_parameters, list_rules.
Choose Moxie Docs MCP when
- You need dedicated capabilities in the Knowledge & Memory domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: OAuth 2.0.
- You want tools like
moxie.get_ai_context, moxie.get_doc_impact, moxie.get_api_context.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Knowledge & Memory | Knowledge & Memory |
| Quality signal | 52/100 · Good | 81/100 · Excellent |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | OAuth 2.0 |
| Pricing | Not declared | Freemium |
| Required env vars | AI_RETE_RAG_API_KEYAI_RETE_RAG_API_URL | None listed |
| Verified owner | Community listing | Verified |
| GitHub stars | 0 | 2 |
| Directory activity | 0 views 0 installs 0 upvotes | 45 views 25 installs 4 upvotes |
| Tools | 9 | 12 |
| Full listing | View Ai·rete·rag | View Moxie Docs MCP |
Tools & capabilities
Ai·rete·rag tools 9
decideMake 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 dayget_parametersThe facts a domain's rules decide on (from your account's own rules), most decisive first — what to collect before `decidelist_rulesInspect a domain's rules — conditions, verdicts, salience, overlapsget_rule_sourceFetch a domain's rule set as editable YAMLimport_policy_rulesTurn a written policy document into draft rules, each citing the sentence it encodes (nothing is saved — review, then `put_rules`)put_rulesCreate or replace a domain's rule set from YAML (dry_run to validate)ingest_textAdd policy text to a domain's knowledge base, optionally dated (`effective_from`, `effective_until`) or replacing an earlier version (`supersedes`)list_documentsBrowse a domain's ingested documentsget_usageCheck your plan and remaining monthly decision quota
Moxie Docs MCP tools 12
moxie.get_ai_contextCompact pre-edit briefing: repo status, verified commands, top conventions, open gaps, team notes. Read this first.moxie.get_doc_impactGiven the paths you're about to change (and any you're deleting), returns the conventions, gaps, and existing docs whose evidence overlaps them - and flags net-new/undocumented surfaces.moxie.get_api_contextGiven paths you're about to touch, returns structured context for any API endpoints they map to: method, path, schema, and known consumers/features.moxie.review_changeSelf-review a change before opening the PR; returns a severity-ranked verdict (clean / warnings / must-fix) covering convention breaches, stale docs, undocumented surface, and broken references.moxie.get_conventionsDiscovered coding conventions, grouped by category, with confidence scores, agent guidance, and source-file citations.moxie.search_docsSemantic + keyword search over generated docs, conventions, gaps, and AI context.moxie.get_doc_gapsUnresolved documentation gaps with severity and the paths they concern.moxie.get_documentation_opportunitiesRecommended doc work: missing docs, drift repairs, and PR templates.moxie.get_documentation_patternsHow the repository organizes and maintains its docs (where new docs belong).moxie.list_docsPaginated, section-grouped table of contents of every generated doc.moxie.propose_doc_updateAdd or update a doc as part of your current change; returns the target path + Markdown to write into your branch.moxie.propose_doc_removalRemove a Moxie Docs-tracked doc your change makes obsolete; returns the path to delete in your branch.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Ai·rete·rag
{
"mcpServers": {
"ai-rete-rag-2": {
"command": "uvx",
"args": [
"ai-rete-rag-mcp"
],
"env": {
"AI_RETE_RAG_API_KEY": "YOUR_AI_RETE_RAG_API_KEY_HERE",
"AI_RETE_RAG_API_URL": "YOUR_AI_RETE_RAG_API_URL_HERE"
}
}
}
}
Moxie Docs MCP
{
"mcpServers": {
"moxie-docs-mcp": {
"command": "npx",
"args": [
"-y",
"moxie-docs"
]
}
}
}
Frequently asked questions
Ai·rete·rag is categorized under Knowledge & Memory and uses a local stdio subprocess. Moxie Docs MCP belongs to Knowledge & Memory and uses a local stdio subprocess. Pick Ai·rete·rag for knowledge & memory work and Moxie Docs MCP for knowledge & memory.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Ai·rete·rag has no declared pricing — check the project's own site. Moxie Docs MCP is listed as freemium — a free tier with paid plans. Auth: oauth 2.0. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add ai-rete-rag-2 and moxie-docs-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Ai·rete·rag has a quality signal of 52/100 (Good) with 0 views, 0 installs and 0 GitHub stars. Moxie Docs MCP has 81/100 (Excellent) with 45 views, 25 installs and 2 GitHub stars.