one.fafPublished by faf.onev7.1.0Updated Nov 6, 2026
Persistent project context for Claude. IANA-registered .faf format.
The publisher's own server: Claude Platform Docs
Creates, scores and syncs a project.faf context file so Claude starts each session knowing the project's stack, goal and decisions.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Follow the launch instructions in the repository.
[npm version] [Smithery] [FAF ✪ 100%] [IANA: vnd.faf+yaml][IANA: vnd.fafm+yaml] [DOI: Context paper][DOI: Memory paper]
Home: faf.one/mcp Site: claude.faf.one
Persistent Project Context with Memory, looped for you. One-click setup. 30 seconds. 🐘 Nelly Never Forgets.
[MCP Registry: one.faf/claude-faf-mcp] [CI] [NPM Downloads] [License: MIT] [Chat to FAFA live] [Business card · Get yours →]
FAF defines. MD instructs. AI codes.
⭐ Star faf-cli on GitHub, the CLI this server is built on: 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(faf_tri_sync), alongside.faf→CLAUDE.md(faf_sync).
⚡ The
fafprompt — pick it from your host's prompt list (Claude Code shows it as/mcp__<server name>__faf). It scores your project, fills what the repo can, asks you only what only you can answer, verifies, and syncs.
7.0.0 is a major release — scores can move. claude-faf-mcp now scores with faf-cli 8's always-33 engine. A
.fafwithout the 12 enterpriseslotignoredmarkers counts them as empty (21 filled = 64%): runfaf_autoand it writes the markers. The npx config and the SessionStart hook are not pinned to a version, so an install that runsnpx -y claude-faf-mcpmoves to 7.x on its next start. Every change is in the CHANGELOG.
Context for Claude: faf-cli writes this repo's CLAUDE.md from its scored project.faf — faf_sync 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 FAF_TOOLS=all). IANA-registered formats (application/vnd.faf+yaml · application/vnd.fafm+yaml).
claude-faf-mcp now tells Claude how its tools fit together: server instructions in initialize (637 characters), plus faf-cli 8.5.0, which knows a skills repo when it sees one.
faf_init and faf_auto detect a skills repo: SKILL.md folders make it skills (10 slots), and a Claude Code plugin manifest makes it skills-plugin (14).--version and --help print and exit, instead of starting the server.One engine, one number: claude-faf-mcp 7 scores with faf-cli 8's always-33 kernel — the same score faf-cli and faf-kernel give.
slotignored unless your app-type uses them. faf_score scores against all 33; slotignored slots drop out of the denominator..faf without the 12 markers now scores against 33. Run faf_auto — it writes them and your score returns (56% → ✪ 100% on a real v7-era file).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.
faf it finds on your PATH.faf_auto writes;faf_go;faf_setup and faf_tri_sync join the default list.faf_go answers can't pollute objects..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.faf_clear, faf_friday, faf_guide, faf_write, the interop imports into project.faf, and faf_check protect/unlock. The archive tag archive/cfm-v5-surface keeps them.Every great product started with 3 answers to the 3Ws — Who, What, Why:
Same pattern. Every product that works starts here. .faf captures it:
30 seconds. Claude builds your project.faf from this. Every session after, AI starts smart.
3Ws gets you started. For fully optimized AI, complete the set — Where, When, How:
3Ws initiates the project with AI. 6Ws optimizes AI to 100%. Same YAML, same file. More examples → faf.one/ideas
Needs Node 22 or later.
⬇ Download claude-faf-mcp-7.1.0.mcpb
Open it in Claude Desktop. The extension runs the server bundled inside it (no npx, no network at start) and lists the Core 14 tools.
Add to claude_desktop_config.json, then restart Claude Desktop:
After npm install -g claude-faf-mcp you can use the installed bin instead: { "command": "claude-faf-mcp" }. With Bun on Claude Desktop's PATH, { "command": "bunx", "args": ["claude-faf-mcp"] } works too.
The npx config and the SessionStart hook faf_setup installs (npx -y claude-faf-mcp --session-refresh) are not pinned: they run the latest release, so fixes arrive without a reinstall, and a new major arrives the same way. To stay on a major, write it in your config yourself: "args": ["-y", "claude-faf-mcp@6"]. The .mcpb runs the version it was built from.
Run the faf prompt — Claude scores your project, fills what the repo can, asks you what only you can answer, verifies and syncs.
Or tell Claude your 3Ws: "I'm building [what] for [who] because [why]"
Same .faf, every surface — Claude, Gemini, Grok, Cursor. faf-cli on npm →
Language, framework, package manager, build tools — faf-cli detects them from your existing files. The human context is the part only you can give.
.faf lives in the repo. Your context travels with the code — committed, versioned, done.
Every session starts grounded. Install the native SessionStart hook once (faf_setup — preview first, your settings preserved). After that, every Claude Code session opens with a one-line heartbeat instead of a blank slate:
That line is the relay: Claude already knows your stack and your score — and the +N is the intent the code can't carry: the goal and 6Ws only you can give or confirm. No re-explaining "what this project is" at the top of every session.
It scales to the team by construction:
faf_sync writes CLAUDE.md from .faf — only its faf-managed block, so your own notes stay put. Add MEMORY.md for cross-session memory (tri-sync 🐘)..faf, same number, on every machine and in CI. A teammate can't be accidentally less grounded than you.Onboarding becomes git clone → grounded. The context a new teammate would normally pick up by asking around is already in the repo, machine-readable, from the first clone.
At 55%, AI guesses half the time. At 100%, AI knows your project. The score is faf-cli's scoreFafYaml — the always-33 number faf score prints for the same file.
FAF_TOOLS=allBy default claude-faf-mcp lists the Core 14 — the lifecycle tools you reach for. Set FAF_TOOLS=all to list the Extended tools too; every tool is callable by name either way. Retired in 6.0.0: faf_clear, faf_friday, faf_guide and faf_write (a call by name returns one line naming what to use instead), the AGENTS.md / .cursorrules / GEMINI.md / conductor imports into project.faf, and faf_check protect/unlock.
Every tool runs on the faf-cli this package depends on. Nothing is run from your PATH.
Core
Extended (FAF_TOOLS=all)
faf_sync writes CLAUDE.md from .faf, so the two stay aligned.
tri-sync adds MEMORY.md — your AI remembers your project across every session.
Pro feature, free for developers. Teams & Enterprise: faf.one/pro (plans)
IANA-registered (application/vnd.faf+yaml). One file, one format. Define once, use everywhere.
Same project.faf. Same scoring. Same result. Different execution layer.
Tests run with bun on ubuntu, macOS and Windows; the built package is packed, installed and started on Node 22 and 24 on all three. CI →
claude-faf-mcp runs on your machine. No analytics, no telemetry, no accounts. Its one network use is faf_git, and only when you ask it to read a repo: git clones it from the URL you give. The files it writes are listed in the privacy policy →
If claude-faf-mcp has been useful, consider starring the repo — it helps others find it.
If you use claude-faf-mcp or the .faf / .fafm / .fafa formats in research or production, please cite the format papers:
Wolfe, J. (2025). Format-Driven AI Context Architecture: The .faf Standard for Persistent Project Understanding. Zenodo. https://doi.org/10.5281/zenodo.18251362
Wolfe, J. (2026). Permanent Memory and Instant Recall: The .fafm Standard for Multi-Profile AI Agent Memory. Zenodo. https://doi.org/10.5281/zenodo.20348942
Wolfe, J. (2026). Why Agents Need a Passport: .fafa — Portable Identity for the Agentic Era. Zenodo. https://doi.org/10.5281/zenodo.21951641
MIT — Free and open source
format | driven 🏎️⚡️ wolfejam.dev
faf-cli — The original AI-Context CLI. A must-have for every builder.
MCP Registry: one.faf/claude-faf-mcp · 2 IANA registrations: vnd.faf+yaml (Context) · vnd.fafm+yaml (Memory) · faf.one · npm
Zero-Config. Context that's just there — every session.
Source: README.md at commit a4eb502
About .faf
Explain what the .faf format is — project context for AI, IANA-registered as application/vnd.faf+yaml — and how this server uses it. Returns a short plain-text overview with this server's version. Reads nothing and writes nothing. Use it when someone asks what FAF is.
Takes no parameters.
Score .faf
Score the project's .faf with faf-cli's scorer — the one score every faf tool reports: 0–100%, the tier, populated/active slots, and a faf-parity/v1 hash of the result. details: true lists every slot as populated, empty or slotignored. Reads only. Use faf_doctor for what to fix.
pathdetailsCreate project.faf
Create a new project.faf for a folder: faf-cli detects its name, language and stack, and the reply gives the file path, faf-cli's starting score and the birth .faf-dna. An existing project.faf is left as it is — use faf_auto to fill its empty slots from your manifests, or faf_go for the human 6Ws. force: true replaces an existing project.faf with a fresh one, after copying the old file to a backup beside it.
pathforceTrust Receipt
Attest the project's .faf: faf-cli's validateFaf, faf-cli's score, and a faf-parity/v1 hash (claude-faf-mcp's own spec) of that score that anyone can check with sha256(projection) === parityHash. Returns a trust receipt whose subject is the project. An invalid .faf, or a score that is unknown, gets no receipt (isError). Reads only.
pathSession Hook Setup
Install the native SessionStart hook in the project settings (<project>/.claude/settings.json) — every Claude Code session in this project starts with fresh .faf context. Shows the exact settings first (preview); writes only with confirm: true, install or remove. faf changes only its own hook entry; every other key and hook stays as written. remove: true takes out only the hook whose command is exactly the faf hook command. Never writes the user settings: the home folder is refused.
pathremoveconfirmSync .faf to CLAUDE.md
Write project.faf into CLAUDE.md as a faf-managed block (faf-cli's render and injector), and on request into AGENTS.md (agents), .cursorrules (cursor), GEMINI.md (gemini) and .github/copilot-instructions.md (copilot) — or all of them (all) — with faf-cli's writers. Each file keeps every line outside faf's block. Returns the files written and any requested file that could not be written, with the reason (then isError). Use it after editing project.faf.
allpathagentscursorgeminicopilotActive Project
Show the active project — the folder every faf_* call without a path uses — and the .faf there; pass path to make another folder the active project (your home folder and the filesystem root are refused). detail: true also returns the .faf's text. Writes no file. Call it once at the start of a session.
pathdetailGuided Interview
The human half of project.faf. Without answers it returns the Table-of-8 — project name, goal and the 6Ws (who, what, why, where, when, how) — each filled, seeded from the goal, or empty, with faf-cli's score and, for each slot still empty, whether it is a fact from repo (faf_auto writes it: its dry run, the one faf_formats shows) or needs an answer here. With answers (slot path → text, e.g. {"stack.hosting": "<the answer>"}) it writes them into <folder>/project.faf in place and returns the new score; a value already in a slot you answer is replaced. With no project.faf yet it runs faf_init and faf_auto first. faf_auto writes each fact from repo; a stack slot with no fact in repo is answered here.
pathanswersFill from the Repo
Create <folder>/project.faf, or fill the empty slots of the one there, with faf-cli's detection over the repo's own files (package.json, Cargo.toml, pyproject.toml, go.mod…) — no hardcoded defaults. A value already there is kept. A typed None or placeholder word is an empty slot: in a tech slot the app-type uses, only a repo fact replaces it (with no fact it stays as typed); in a tech slot the app-type leaves out, faf_auto writes slotignored; in a 6W it stays as typed (faf_go asks). Every value it changes is listed. Then writes CLAUDE.md's faf-managed block. Returns what was filled and faf-cli's score before and after. faf_go does the human 6Ws.
pathGrounding Benchmark
Prove the .faf earns its place — measure how much the context is worth, on THIS repo, falsifiably. Questions derive from the project.faf's own populated slots (the .faf is the answer key), so grading is mechanical — no judge, no rubric. action=questions returns the answer-key-safe question set; action=grade takes your answers WITHOUT the .faf (cold) and WITH it (faf), grades both, and returns the cold→with-faf lift with a receipt hash. The delta is the product; the cold number belongs to the absence of context, never to FAF. Reads only.
fafcoldpathmodelactionfafTokenscoldTokensDiagnose .faf
Diagnose the project's .faf: faf-cli's validateFaf errors, faf-cli's score with every empty slot and the tool that fills it (faf_auto from the repo, faf_go for the 6Ws), whether CLAUDE.md is there, and the formats faf-cli finds in the folder. Returns a checklist of findings, each with its fix. Reads only. Use it when faf_score is below 100%.
pathTri-Sync to MEMORY.md
Write project.faf as a faf-managed block into the MEMORY.md Claude Code loads for this project (~/.claude/projects/<project-id>/memory/MEMORY.md, or under CLAUDE_CONFIG_DIR). Only the block changes; every note of Claude's is kept, and the reply says so only after reading the file back. action: status reads only. faf_sync writes CLAUDE.md.
pathactionEtch Memory
Remember a decision, gotcha, or win across sessions by writing it to the project soul (soul.fafm) with faf-cli's Soul. Returns the stored memory and the soul's size. Re-etching an id updates that memory in place. Use it to persist something an AI should recall later; faf_recall reads them back.
idpathtagstextrequiredtypepriorityRecall Memory
Recall memories from the project soul (soul.fafm), ranked by priority then recency, filtered by query/tags/type. Returns the matching entries. Reads only. Use it to surface past decisions; faf_etch adds new ones.
pathtagstypelimitqueryminPriority90% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
com.claude.platformOfficial publisher
Remote MCP server that lets an assistant search and read the Claude Platform documentation and API reference.
Published by GitHub account faisalkhanzemi
Bridge that lets Claude drive the full 274-tool editor in Instagram Edits for Mac, keeping the tool list in sync as projects open.
Published by GitHub account daniel-munoz
Local MCP server that saves Claude Code session state to a checkpoint file in the project and reloads it as a compact resume brief.
Published by GitHub account spk-c
Qwen DAP MCP — C/C++ Debugger for Claude Code, Codex & Qwen's local MCP server; no sign-in required; STDIO; 18 tools.
Published by GitHub account lemberalla
Local AVE timeline editing and exports for Claude Code only. Existing AVE connection required.
human_context: who: "people who need a ride across town" what: "tap a button, car arrives in minutes" why: "taxis are slow, expensive, and hard to find" where: "mobile app, iOS and Android" # where does it live? when: "launch in 3 months" # when is it shipping? how: "GPS matching, real-time pricing" # how does it work?{ "mcpServers": { "faf": { "command": "npx", "args": ["-y", "claude-faf-mcp"] } }}claude mcp add faf -- npx -y claude-faf-mcpnpx faf-cli autoYou → 3 answers → project.faf → AI reads it → every session → forever
project.faf ──→ CLAUDE.md (faf_sync)project.faf ──→ MEMORY.md (faf_tri_sync 🐘)faf: context ✪ 100% — fresh · +7 intent the code can't carrycommit project.faf → every teammate's Claude starts with the same contextgit clone → a new dev's Claude is grounded before they write a linefaf_sync = .faf → CLAUDE.md ← written from .faftri-sync = .faf → MEMORY.md (faf_sync writes CLAUDE.md) ← Nelly never forgets 🐘Model Context Protocol───── ─────── ────────Claude → .faf → MCPGemini → .faf → MCPCodex → .faf → MCPAny LLM → .faf → MCP@article{wolfe2025faf, title = {Format-Driven AI Context Architecture: The .faf Standard for Persistent Project Understanding}, author = {Wolfe, James}, year = {2025}, month = {nov}, publisher = {Zenodo}, doi = {10.5281/zenodo.18251362}, url = {https://doi.org/10.5281/zenodo.18251362}}
@article{wolfe2026fafm, title = {Permanent Memory and Instant Recall: The .fafm Standard for Multi-Profile AI Agent Memory}, author = {Wolfe, James}, year = {2026}, month = {may}, publisher = {Zenodo}, doi = {10.5281/zenodo.20348942}, url = {https://doi.org/10.5281/zenodo.20348942}}
@article{wolfe2026fafa, title = {Why Agents Need a Passport: .fafa — Portable Identity for the Agentic Era}, author = {Wolfe, James}, year = {2026}, month = {aug}, publisher = {Zenodo}, doi = {10.5281/zenodo.21951641}, url = {https://doi.org/10.5281/zenodo.21951641}}npx faf-cli auto