grok-faf-mcp

Grok FAF is the name on the MCP registries; grok-faf-mcp is the package and the repo. The MCP server for xAI Grok: persistent project context from project.faf, on a URL or locally over stdio.

Run it

On a URL — add to ~/.grok/config.toml:

[mcp_servers.grok-faf-mcp]
url = "https://mcpaas.live/grok/mcp/v1"

Restart Grok (or /mcps r). Nothing to install.

Locally, when you want the tools that read and write your repo:

bunx grok-faf-mcp      # or: npx grok-faf-mcp

One number

Every score is the always-33 score — the same number faf score gives. Locally, scoring runs the faf-cli this package bundles, in-process; nothing that scores shells out to a faf on your PATH. The hosted URL scores and validates with the same kernel. See Scoring.

Tools

Twelve shown by default on the local server; FAF_TOOLS=all exposes the rest. Every tool stays callable by name either way.

Tool	Does
refresh_faf · refresh_fafm · refresh_blend	re-ground a long session on project.faf, on the .fafm memory, or both
rag_query · rag_cache_stats · rag_cache_clear	ask Grok about the project, with a cache
faf_orchestrate_recommendation	read the drift signals and recommend a refresh — advisory, it never runs one
faf_get_orchestration_policy	show the policy the orchestrator uses
faf_init	write project.faf for this folder, with the enterprise slots marked, and report its score
faf_score	AI-readiness 0–100, populated/active slots
faf_sync	write the .faf block into CLAUDE.md, AGENTS.md, .cursorrules, GEMINI.md — your prose below it is kept
faf_trust	check the file and report its score

Resources: claude-faf://context (the parsed .faf + score) and claude-faf://status (path, score, slots).

What each tool may change

Every tool carries MCP tool annotations, so your client knows when to ask first:

• Read only: faf_score, faf_trust, faf_get_orchestration_policy, rag_cache_stats, and rag_query (the one tool that reaches the network, xAI Collections). With FAF_TOOLS=all, also faf_list and faf_read.
• Can delete or overwrite: faf_init with force; with FAF_TOOLS=all, faf_clear and faf_write. faf_write never writes .faf-dna, stays inside the project folder (not .git/), and replaces an existing project.faf, *.faf, CLAUDE.md or AGENTS.md only with overwrite: true.
• Write without losing anything: the rest. faf_sync keeps your prose, rag_cache_clear only empties memory, and refresh_faf, refresh_fafm, refresh_blend, faf_orchestrate_recommendation and the FRC tools append small receipt files (.faf-refresh-receipts.json, .fafm-refresh-receipts.json, .frc-usage-receipts.json) to your project folder.

Local or hosted

The hosted URL serves its own set — scoring, validation, refresh_faf, a content-in faf_orchestrate_recommendation, souls and search. The live list is at https://mcpaas.live/grok/mcp/v1/info. Tools that read or write your files (faf_init, faf_sync, refresh_fafm, refresh_blend) run locally only.

Passport

Grok FAF has its own FAF passport, agent.fafa, at https://grok.faf.one/.well-known/fafa, with AI Catalog and ARD entries at /.well-known/ai-catalog.json and /.well-known/ard.json that point to it. The MCP Server Card is the hosted one, at https://mcpaas.live/grok/mcp/v1/server-card (the <streamable-http-url>/server-card path from SEP-2127). https://grok.faf.one/mcp/server-card and the older https://grok.faf.one/.well-known/mcp/server-card.json both redirect to it. See Cards.

ZEPH

ZEPH is a Zig fast path for refresh_faf. It is off by default and turns on with USE_ZEPH=1; it stays opt-in until the Zig engine gives the always-33 number on every file.

---

Next: Scoring — how the 33 slots count