# Grok Faf Mcp > Persistent Project Context for xAI Grok — IANA-registered .faf format · MCP server on a URL - **Type:** MCP server - **Install:** `agentstack add mcp-wolfe-jam-grok-faf-mcp` - **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior - **Seller:** [Wolfe-Jam](https://agentstack.voostack.com/s/wolfe-jam) - **Installs:** 0 - **Category:** [Developer Tools](https://agentstack.voostack.com/c/developer-tools) - **Latest version:** 1.0.0 - **License:** MIT - **Upstream author:** [Wolfe-Jam](https://github.com/Wolfe-Jam) - **Source:** https://github.com/Wolfe-Jam/grok-faf-mcp - **Website:** https://faf.one ## Install ```sh agentstack add mcp-wolfe-jam-grok-faf-mcp ``` Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent. ## About # grok-faf-mcp — FAST⚡️AF Edition Grok asked for MCP on a URL. This is it. Persistent Project Context for xAI Grok. URL-based • Zero config • Just works [](https://www.iana.org/assignments/media-types/application/vnd.faf+yaml) [](https://doi.org/10.5281/zenodo.18251362) **Home:** [faf.one/grok](https://faf.one/grok) **Live demo:** [grok.faf.one](https://grok.faf.one) [](https://www.npmjs.com/package/grok-faf-mcp) [](https://faf.one) [](https://github.com/Wolfe-Jam/grok-faf-mcp/actions/workflows/ci.yml) [](https://opensource.org/licenses/MIT) [](https://github.com/Wolfe-Jam/faf) [](https://faf-voice.vercel.app/agent) [](https://github.com/Wolfe-Jam/grok-faf-mcp/stargazers) [](https://www.npmjs.com/package/grok-faf-mcp) **FAF defines. MD instructs. AI codes.** --- ## Install — one line Add to `~/.grok/config.toml`: ```toml [mcp_servers.grok-faf-mcp] url = "https://mcpaas.live/grok/mcp/v1" ``` Restart Grok TUI (or `/mcps r`) to refresh. Tools: `faf_score`, `faf_validate`, `faf_get_tier`, `faf_estimate_tokens`, `faf_analyze` (plus soul/memory ops). **Hosted on Cloudflare Workers** — sub-ms cold start, no subprocess, edge-served. 4865-byte Zig WASM engine, parity-tested vs the Rust authority (`xai-faf-rust`). Externally validated by Grok S1 + S2 on 2026-05-27. **Verify the live contract:** ```bash curl https://mcpaas.live/grok/mcp/v1/info ``` Returns endpoint, protocol versions, engine details, tool list, and the architecture line: `.faf=vROM | AI-in-session=RAM`. Sample corpus: [`xai-faf-proof/pilot`](https://github.com/Wolfe-Jam/xai-faf-proof/tree/main/pilot) — 10 records ready to score. --- ## The 6 Ws - Quick Reference Every README should answer these questions. Here's ours: | Question | Answer | |----------|--------| | **WHO** is this for? | Grok/xAI developers and teams building with URL-based MCP | | **WHAT** is it? | Persistent project context for xAI Grok — URL-first deployment, IANA-registered .faf format | | **WHERE** does it work? | Cloudflare Workers (`mcpaas.live/grok/mcp/v1`) • Any MCP client supporting native `url=` config • Self-deploy to your own CF/Vercel worker | | **WHY** do you need it? | Zero-config MCP on a URL — Grok asked for it, we built it first | | **WHEN** should you use it? | Grok integration, xAI projects, any url-based MCP client | | **HOW** does it work? | `url = "https://mcpaas.live/grok/mcp/v1"` — context tools served from edge via MCPaaS (sub-ms cold start, no subprocess) | **For AI:** Read the detailed sections below for full context. **For humans:** Use this pattern in YOUR README. Answer these 6 questions clearly. ### For the xAI / Grok Build team Built **for** Grok and shaped by direct Grok feedback. Open for native Grok Build integration, .fafm memory layer, refresh_faf primitives, or any other context features the team needs. Live and dogfooded at https://grok.faf.one and https://mcpaas.live/grok/mcp/v1. Happy to ship PRs, run private dogfood sessions, or jump on a call. Real software only. Just say the word. --- ## The Problem Every Grok session starts from zero. You re-explain your stack, your goals, your architecture. Every time. `.faf` fixes that. One file, your project DNA, persistent across every session. ``` Without .faf → "I'm building a REST API in Rust with Axum and PostgreSQL..." With .faf → Grok already knows. Every session. Forever. ``` --- ## One Command, Done Forever `faf_auto` detects your project, creates a `.faf`, and scores it — in one shot: ``` faf_auto ━━━━━━━━━━━━━━━━━ Score: 0% → 85% (+85) ◇ BRONZE Steps: 1. Created project.faf 2. Detected stack from package.json 3. Synced CLAUDE.md Path: /home/user/my-project ``` What it produces: ```yaml # project.faf — your project, machine-readable faf_version: "3.3" project: name: my-api goal: REST API for user management main_language: TypeScript stack: backend: Express database: PostgreSQL testing: Jest runtime: Node.js human_context: who: Backend developers what: User CRUD with auth why: Replace legacy PHP service ``` Every AI agent reads this once and knows exactly what you're building. --- ## ⚡ What You Get ``` URL: https://mcpaas.live/grok/mcp/v1 Format: IANA-registered .faf (application/vnd.faf+yaml) Tools: 12 core by default (bunx) — re-grounding (refresh_faf/fafm/blend), LAZY-RAG, orchestration substrate, FAF essentials · extended utilities via FAF_TOOLS=all · 14 hosted (WASM-pure) on the URL Engine: Mk4 WASM scoring (faf-scoring-kernel) Speed: 0.5ms average (was 19ms — 3,800% faster with Mk4) Tests: 27 .ts files (~518 test declarations) — WJTTC parity (heavy local ↔ light hosted) + full suites. Runner: sh scripts/run-tests.sh (bun + flake retry) Status: FAST⚡️AF ``` **MCP on a URL.** Point your Grok integration at the URL. That's it. --- ## Scoring: From Blind to Optimized | Tier | Score | What it means | |------|-------|---------------| | **🏆 TROPHY** | 100% | Gold Code — AI is optimized | | **★ GOLD** | 99%+ | Near-perfect context | | **◆ SILVER** | 95%+ | Excellent | | **◇ BRONZE** | 85%+ | Strong baseline | | **●** GREEN | 70%+ | Solid foundation | | ● YELLOW | 55%+ | AI flipping coins | | ○ RED | Earlier: v1.8.0 — **The Closed-Loop Edition** — observability writes, token math is honest, FRC contract locked. The drift→refresh→re-ground loop can finally be measured. > Earlier: v1.7.0 — **The Grounded Memory Edition** — ZEPH + the FRC layer over Grok Collections (`faf_gate`/`faf_section`/`faf_memory`), opt-in via `USE_FRC`/`USE_ZEPH`; 12-tool core unchanged. > Earlier: v1.6.0 — **The ZEPH Edition** — the ZEPH fast path for re-grounding (`refresh_faf`/`refresh_blend` via Zig→WASM `cascade.wasm`, ~12µs, `USE_ZEPH=1`; `faf-cli` stays canonical, parity locked in CI). **What is fully supported:** - WASM-pure tools on the hosted endpoint (`https://mcpaas.live/grok/mcp/v1` and client-specific routes) — scoring · validation · `refresh_faf`. - `refresh_faf` and `refresh_fafm` as explicit, callable re-grounding primitives. - `refresh_blend` as the baked-in two-intensity refresh (Cmd+R / Cmd+Shift+R analog). - `faf_orchestrate_recommendation` — the heavy orchestrator that composes drift signals, recurrence, receipts, and take-a-hint into an advisory recommendation. - `faf_get_orchestration_policy` — pure introspection of the effective policy without running the orchestrator (no drift detection, no receipt write — the quietest tool in the substrate). - Full policy visibility (`effective_policy`) returned on every orchestration call AND surfaced standalone via `faf_get_orchestration_policy`. **Current limitations:** - **`faf_orchestrate_recommendation`, `faf_get_orchestration_policy`, `refresh_fafm`, and `refresh_blend` require filesystem access** and are only available via the local stdio path (`bunx grok-faf-mcp` / `npx grok-faf-mcp`). They are not exposed on the hosted WASM-pure endpoint. The hosted path serves the existing WASM-pure subset only (`refresh_faf` + scoring + validation). - **Receipt storage — cwd-relative JSON, pull-discoverable.** Three append-only JSON files live at the repo root with stable schemas: ``` .faf-drift-index.json ← RepeatOffenderTracker — per-slot recurrence counts .faf-refresh-receipts.json ← RefreshReceiptsLog — every refresh fire .faf-recommendation-receipts.json ← RecommendationReceiptsLog — every orchestrator call ``` **Pull-discoverable by external tools** (TAF, custom indexers, observability dashboards) — read on your own schedule, no callback/push API required. Promotion to a dedicated orphan branch (mirroring the TAF pattern) is documented but deferred per ship discipline; the cwd-relative JSON is the v1 bootstrap. - **No multi-process file lock** on the receipt logs. Within a process, the JS event loop serializes writes. Multi-agent concurrent writes can race; future task. - **Aggressiveness tier hook** — `.faf:orchestration:tier` reads `'conservative'` (default — quietest, no noisy first-impression) · `'balanced'` · `'aggressive'`. `active_tier` always surfaced in `hints.effective_policy` for observability, and standalone via `faf_get_orchestration_policy`. The policy WRITER (`faf_set_orchestration_policy`) and scheduling (`faf_schedule_heavy_re_ground`) are not included in v1.5 — edit `.faf:orchestration:tier:` directly to override. - **No ack mechanism yet for recommendation receipts.** `acknowledged: false` by default, never auto-flipped. Take-a-hint's ladder-reset semantics fire only on explicit ack — conservative by intent. Future task: explicit `ack` tool OR derived-from-subsequent-refresh-receipt timing. - **Outcome tracking** (*"did this recommendation actually help?"*) — needs a learning layer beyond 1.5 scope. **The honest split is intentional:** hosted = fast, auditable, WASM-pure; local = full capability including filesystem. We will expand the hosted surface only where it can be done safely and without compromising the model. **Subordinate-not-daemon throughout.** The orchestrator NEVER auto-fires the recommended tool. Agents surface the recommendation; the user (or higher agent) decides whether to act. Even `severity: 'block'` is advisory. See the [public verifier](https://grok.faf.one/) and `curl https://mcpaas.live/grok/mcp/v1/info` for the current contract. --- ## Ecosystem One format, every AI platform. | Package | Platform | Registry | |---------|----------|----------| | **grok-faf-mcp** (this) | **xAI Grok** | **npm** | | [claude-faf-mcp](https://npmjs.com/package/claude-faf-mcp) | Anthropic | npm + MCP #2759 | | [gemini-faf-mcp](https://pypi.org/project/gemini-faf-mcp/) | Google | PyPI | | [rust-faf-mcp](https://crates.io/crates/rust-faf-mcp) | Rust | crates.io | | [faf-mcp](https://npmjs.com/package/faf-mcp) | Cursor, IDE's, VS Code | npm | | [faf-cli](https://npmjs.com/package/faf-cli) | Terminal CLI | bunx, npm + Homebrew | Same `project.faf`. Same scoring. Same result. Different execution layer. --- ## Voice variant — `grok-faf-voice` (VML) `.fafm 🐘🎙️` — the voice variant of the `.faf 🐘` family. **[grok-faf-voice](https://pypi.org/project/grok-faf-voice/)** is the reference implementation of the **Voice Memory Layer (VML)** — what your voice agent *remembers* across sessions, devices, and model switches. Companion to `grok-faf-mcp`: - **`grok-faf-mcp`** (this) — `.faf` Foundational Context Layer for Grok via MCP-on-a-URL. - **`grok-faf-voice`** — `.fafm` Voice Memory Layer (VML) for Grok Voice via LiveKit + xAI realtime. Same family. Different surface. *Voice swappable; memory permanent.* [PyPI](https://pypi.org/project/grok-faf-voice/) · [GitHub](https://github.com/Wolfe-Jam/grok-faf-voice) · [Onboarding](https://wolfe-jam.github.io/grok-faf-voice/onboarding.html) --- ### For the xAI / Grok Build team This MCP server was built **for** Grok and continues to be shaped by direct feedback from Grok itself. Open for deeper collaboration on: - Native Grok Build integration - .fafm memory layer - refresh_faf primitives inside the Grok TUI / CLI - Any other context or orchestration features the team needs I ship fast, test rigorously, and dogfood everything live on https://grok.faf.one and https://mcpaas.live/grok/mcp/v1. Happy to: - Open PRs - Run private dogfood sessions - Jump on a call - Or just ship whatever moves the needle Real software only. Just say the word. --- ## Contributing PR conventions, code style, CI doctrine, MCP-tool contribution path, npm publish discipline, architecture decisions: **[CONTRIBUTING.md](CONTRIBUTING.md)**. xAI / Grok devs welcome — TL;DR setup at the top, F1-inspired tone throughout. --- If grok-faf-mcp has been useful, consider starring the repo ⭐️ it helps others find it. ### For xAI / Grok Build team Open for deeper native integration, .fafm memory layer, or Grok Build CLI collaboration. Happy to ship PRs, dogfood, or jump on a call. Just say the word. --- ## License MIT — Free and open source --- Built for Grok. Built for Speed. Built Right. FAST⚡️AF • First to Ship • Zero Friction Zero drift. Eternal sync. AI optimized. 🏆 --- ### Get the CLI > **faf-cli** — The original AI-Context CLI. A must-have for every builder. ```bash npx faf-cli auto ``` **Anthropic MCP [#2759](https://github.com/modelcontextprotocol/servers/pull/2759)** · **IANA Registered:** `application/vnd.faf+yaml` · [faf.one](https://faf.one) · [npm](https://www.npmjs.com/package/faf-cli) · [Talk to my Agent →](https://faf.one/agent) ## Source & license This open-source MCP server is cataloged on AgentStack and links to its original source — we do not rehost the code. - **Author:** [Wolfe-Jam](https://github.com/Wolfe-Jam) - **Source:** [Wolfe-Jam/grok-faf-mcp](https://github.com/Wolfe-Jam/grok-faf-mcp) - **License:** MIT - **Homepage:** https://faf.one Install and usage instructions live in the source repository linked above. ## Pricing - **Free** — Free ## Security capabilities Automated source analysis of v1.0.0 — what this tool can access: - **Network access:** yes - **Filesystem access:** no - **Shell / process execution:** yes - **Environment & secrets:** no - **Dynamic code execution:** no *"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.* ## Versions - **1.0.0** — security scan: passed — Imported from the upstream source. ## Links - Listing page: https://agentstack.voostack.com/l/mcp-wolfe-jam-grok-faf-mcp - Seller: https://agentstack.voostack.com/s/wolfe-jam - Browse the marketplace: https://agentstack.voostack.com/browse --- Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.