claude-faf-mcp
Home: faf.one/mcp Site: claude.faf.one
Persistent Project Context with Memory, looped for you. One-click setup. 30 seconds. 🐘 Nelly Never Forgets.
FAF defines. MD instructs. AI codes.
⭐ Bookmarks it for you, helps other devs find it too.
v0.2-conformant reader of the FAF Context Ingestion Contract.
🐘 tri-sync | .faf → MEMORY.md (faftrisync), alongside .faf → CLAUDE.md (fafsync).
⚡ The faf prompt — pick it from your host's prompt list (Claude Code shows it as /mcp<server namefaf). It scores your project, fills what the repo can, asks you only what only you can answer, verifies, and syncs.
6.0.0 is a major release. It needs Node 22 or later. fafclear, faffriday, fafguide and fafwrite are retired, and so are the AGENTS.md / .cursorrules / GEMINI.md / conductor imports into project.faf. The .mcpb now runs the server bundled inside it. The npx config and the SessionStart hook are not pinned to a version, so an install that runs npx -y claude-faf-mcp moves to 6.x on its next start: check your Node before you upgrade. Every change is in the CHANGELOG.
Context for Claude: faf-cli writes this repo's CLAUDE.md from its scored project.faf — fafsync here, faf sync in faf-cli. See FAF-CLI for Claude Code 👀.
Composes faf-cli (the version is pinned in package.json). Detection, scoring, the renders and every writer are faf-cli's own functions, loaded as a dependency; claude-faf-mcp does not fork them and never runs a faf found on your PATH.
Core 14 MCP tools (30 with FAFTOOLS=all). IANA-registered formats (application/vnd.faf+yaml · application/vnd.fafm+yaml).
---
What's New in v6.0.0 — The Earned Badge Edition
Every badge earned, none claimed: claude-faf-mcp 6.0 composes faf-cli, touches only what it wrote, and every tool tells the truth — one score, facts from repo, nothing from your PATH.
- Composes faf-cli 7.13. Detection, scoring, the renders and every writer are faf-cli's own functions. claude-faf-mcp never runs a faf it finds on your PATH.
- Touches only what it wrote.
- Every write is atomic and goes through faf-cli's safe path, and a file that links out of the project is refused.
- project.faf edits keep your comments and exact values.
- Your soul.fafm and Claude's own MEMORY.md notes stay as you left them.
- One score. Every tool shows faf-cli's score, and ✪ appears only at 100%.
- Facts from repo. Every empty slot says what fills it:
- a fact from repo, which fafauto writes;
- no fact in repo, which you answer with fafgo;
- or yours, for the 6Ws.
- Tools that tell the truth.
- Every title, hint and schema matches what the tool does, and bad arguments are refused before anything runs.
- Core 14: fafsetup and faftrisync join the default list.
- Safe with any repo.
- A cloned repo's symlinks never reach your AI's context.
- fafgo answers can't pollute objects.
- The file tools stay inside the active project.
- Ships what it runs. The .mcpb runs the server bundled inside it, and it's started and checked before its sha is recorded. Node 22+, with CI on Node 22 and 24 across Ubuntu, macOS and Windows.