In-depth architectural comparison of the Claude Faf MCP and Moxie Docs MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Claude Faf MCP
Knowledge & Memory · Local stdio
Quality: 65/100 (Great) | Auth: No auth required
Moxie Docs MCP
Knowledge & Memory · Local stdio
Quality: 80/100 (Excellent) | Auth: API Key required
Verdict Summary: Choose Claude Faf MCP if you need specialized Knowledge & Memory tools running via a local process. Choose Moxie Docs MCP if your workspace requires Knowledge & Memory integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Claude Faf MCP when:
You need dedicated capabilities in the Knowledge & Memory domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
First & only persistent project context MCP. Provides .faf (Foundational AI-context Format) Project DNA with 33+ tools, Podium scoring (0-100%), and format-driven architecture. Official Anthropic Registry. 10k+ npm downloads.
MCP & Agent Skills for Automated Documentation, and codebase conventions + context
Tools & Capabilities Breakdown
Claude Faf MCP Tools (30)
faf_init
Create project.faf for a folder (faf-cli detects the stack)
faf_auto
Fill project.faf from the repo's own files, then CLAUDE.md
faf_go
The goal and the 6Ws, by question and answer
faf_score
AI-readiness score (0-100%), from faf-cli
faf_bench
Benchmark AI grounding — cold vs with the .faf, graded mechanically, with a receipt
faf_doctor
Diagnose project.faf: each finding with the tool that fixes it
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Claude Faf MCP is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Moxie Docs MCP belongs to Knowledge & Memory using local stdio subprocess. Select Claude Faf MCP when you need capabilities focused on knowledge & memory and Moxie Docs MCP when you require tools for knowledge & memory.
Validate project.faf and return a trust receipt for its score
faf_sync
Write CLAUDE.md from project.faf — `agents`/`cursor`/`gemini`/`copilot`/`all` also write AGENTS.md / .cursorrules / GEMINI.md / copilot-instructions.md
faf_tri_sync
Write faf's block into the MEMORY.md Claude Code loads for this project 🐘
faf_setup
Install the SessionStart hook in the project settings (preview first)
faf_context
Show or set the active project; `detail` returns the .faf text
faf_etch
Remember a decision across sessions (the project soul, soul.fafm)
+18 more tools listed on main page
Moxie Docs MCP Tools (12)
moxie.get_ai_context
Compact pre-edit briefing: repo status, verified commands, top conventions, open gaps, team notes. Read this first.
moxie.get_doc_impact
Given 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_context
Given 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_change
Self-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_conventions
Discovered coding conventions, grouped by category, with confidence scores, agent guidance, and source-file citations.
moxie.search_docs
Semantic + keyword search over generated docs, conventions, gaps, and AI context.
moxie.get_doc_gaps
Unresolved documentation gaps with severity and the paths they concern.
moxie.get_documentation_opportunities
Recommended doc work: missing docs, drift repairs, and PR templates.
moxie.get_documentation_patterns
How the repository organizes and maintains its docs (where new docs belong).
moxie.list_docs
Paginated, section-grouped table of contents of every generated doc.
moxie.propose_doc_update
Add or update a doc as part of your current change; returns the target path + Markdown to write into your branch.
moxie.propose_doc_removal
Remove a Moxie-tracked doc your change makes obsolete; returns the path to delete in your branch.