We are the 'C' in MCP • Universal AI Context
The official MCP documentation for .faf — persistent project context across Claude, Grok, Gemini, Cursor, Windsurf, Cline, VS Code, and every MCP-compatible platform.
MCP is an open protocol connecting AI assistants to context. .faf is the IANA-registered context format (application/vnd.faf+yaml) — one source, every model and tool.
.faf owns the write side. The Context-Ingestion contract owns the read side. faf-cli authors it — Claude-first, cross-vendor.
.faf is the universal Context layer for any Model using the MCP Protocol
Formats = facts.
One IANA-registered format. A server for every model — plus the CLI that authors it.
The Claude-first MCP server — persistent .faf context for Claude Desktop and Claude Code.
.faf ↔ CLAUDE.mdnpx claude-faf-mcpThe core, universal MCP server for Cursor, Windsurf, Cline, VS Code, and any MCP-compatible client.
.faf ↔ your context filesnpx faf-mcpThe MCP server for xAI Grok — the same .faf context, read by Grok.
.faf formatnpx grok-faf-mcpThe MCP server for Google Gemini — Python, published to PyPI.
uvx gemini-faf-mcp (PyPI).faf formatuvx gemini-faf-mcpChampionship-grade MCP testing. If a server passes WJTTC, it works.
npx wjttcThe CLI on-ramp — author, score, and sync your .faf from any terminal. Claude-first, works cross-vendor.
faf init, faf score, faf sync.faf ↔ CLAUDE.mdnpm install -g faf-clibrew install wolfe-jam/faf/faf-cliAlso in the family: rust-faf-mcp (Rust · crates.io) — six FAF servers total in the official MCP Registry.
Tools: core ~12–14 per server, family ~29–33 total. Each server's README is the source of truth.
npm install -g faf-mcp{
"mcpServers": {
"faf": {
"command": "npx",
"args": ["-y", "faf-mcp"]
}
}
}Then start prompting: "Use FAF to initialize your project"
Just start prompts with Use FAF.
Use FAF to initialize your projectUse FAF to sync my project.faf to all platformsUse FAF to score my AI-readinessUse FAF to enhance my context