Log inSubmit server
Grok FAF logo

Grok FAF

Persistent .faf project context for Grok, with scoring, synchronization, retrieval, memory refresh, and orchestration tools.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Grok FAF

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "grok-faf": {
      "command": "bunx",
      "args": [
        "faf"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

We couldn’t confirm it starts correctly

We ran the install command but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

bunx faf

Process exited before answering initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 3d ago.

Overview

The Grok FAF MCP server gives xAI Grok persistent project context through IANA-registered .faf files. It can detect a project stack, create and score context, synchronize it with platform files, validate integrity, retrieve relevant information, and refresh live context or memory layers. It is available as a hosted URL endpoint, with local stdio installation also documented through Homebrew. Reach for it when Grok sessions need repeatable project context or when an MCP client can connect to a URL.

Use cases

  • Create a machine-readable project context file from an existing codebase
  • Score a project's AI-readiness and inspect its breakdown
  • Refresh Grok's context when the live .faf file changes
  • Synchronize project context with CLAUDE.md
  • Query stored project context with RAG

Key features

  • Project stack detection and .faf initialization
  • AI-readiness scoring with breakdowns
  • FAF and FAFM context refresh
  • Project and platform context synchronization
  • RAG retrieval and cache management
  • Orchestration recommendations and policy inspection

Tools19

What Grok FAF lets your agent do. Expand a tool for its parameters.

Self-reported~481 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 3d ago

Recent health check succeeded.

8/8 checks healthy over the last 44d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 13d ago via OSV.dev · faf (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars19Stargazers on the source repository.
npm downloads2.1kPackage downloads in the last 30 days.
Last commit5d agoMost recent push to the default branch.
Install checkInconclusiveDidn't respond in our test window — often a slow first install.
Tools exposed19Callable tools this server registers over MCP.

How Grok FAF works

What Grok FAF MCP server does

The Grok FAF MCP server connects xAI Grok to persistent project context stored in .faf files. A project file can describe the project name, goals, language, stack, runtime, database, testing setup, and human context in a machine-readable YAML format. The format is identified in the repository as IANA-registered application/vnd.faf+yaml.

The Grok FAF MCP server exposes tools for creating, inspecting, scoring, validating, and updating this context. faf_auto detects a project stack, creates context, and scores the result. faf_score returns an AI-readiness score from 0 to 100 with a breakdown, while faf_status checks the current readability state. faf_trust validates .faf integrity, and faf_list discovers projects containing .faf files.

Context can be synchronized with CLAUDE.md using faf_sync, or with platform context through faf_bi_sync. The server also provides file access through faf_read and faf_write, plus RAG retrieval and cache controls through rag_query, rag_cache_stats, and rag_cache_clear. grok_go_fast_af loads .faf context for Grok.

How it works

The hosted deployment is configured as an MCP URL. The README provides https://mcpaas.live/grok/mcp/v1 as the endpoint and shows it in Grok's ~/.grok/config.toml. After restarting the Grok TUI, or refreshing MCPs with /mcps r, the configured tools become available. The hosted service runs on Cloudflare Workers and uses a WebAssembly scoring engine described as the same engine used by the npm package.

For local use, the repository documents a Homebrew installation command. The local package uses stdio, while the hosted option avoids a local subprocess and serves the MCP endpoint from the edge. The README also identifies a Smithery gateway for the project.

Refresh tools support the .faf project layer and the .fafm memory layer. refresh_faf rereads and rescoring the live file, reports drift, and returns refreshed project data. refresh_fafm returns a stamped delta by default, with a verbatim option for full memory content. refresh_blend runs both refresh paths, using either the default blend mode or a harder nuke mode. faf_orchestrate_recommendation evaluates substrate state and returns a structured recommendation with severity, reasons, and hints; faf_get_orchestration_policy inspects the policy without running that orchestration.

Setup and configuration

For hosted Grok use, add the following configuration:

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

The repository also documents this local installation:

bash
brew install wolfe-jam/faf/grok-faf-mcp

A /info endpoint is available at the hosted URL for checking endpoint details, protocol versions, engine information, and the tool list.

Tools and capabilities

The Grok FAF MCP server includes these documented capabilities:

  • Initialize, auto-detect, score, inspect, validate, read, write, list, and synchronize project context.
  • Re-ground .faf and .fafm layers, combine refresh operations, and inspect orchestration policy.
  • Produce orchestration recommendations based on current substrate state.
  • Query RAG context and inspect or clear its cache.
  • Load .faf context for Grok with grok_go_fast_af.

Some refresh and orchestration operations append receipt files to the project folder.

Limitations and notes

The hosted endpoint and the local package are described as using an always-33 scoring engine, so scores may differ from other scoring implementations. The hosted deployment exposes a smaller default tool set, with extended utilities available through the documented FAF_TOOLS=all setting for local use. Only rag_query is identified as reaching the network for xAI Collections.

Write-capable tools can change project files. In particular, the README identifies faf_init with force and faf_write among operations that can overwrite or delete data; review client confirmation behavior before allowing automated writes. Refresh and orchestration calls can also create receipt files even when their primary purpose is reading or analysis.

The Grok FAF MCP server is aimed at projects that can maintain .faf context and at MCP clients able to use the documented URL or local stdio configuration.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Grok FAF

Grok FAF is an MCP server that connects xAI Grok to persistent project context in IANA-registered .faf files. Its main tools create and score context, detect a project stack, synchronize files, validate integrity, refresh .faf and .fafm memory layers, retrieve RAG context, and produce orchestration recommendations.

Install the local package with Homebrew using `brew install wolfe-jam/faf/grok-faf-mcp`, or configure the hosted MCP URL in Grok's `~/.grok/config.toml`. The documented hosted endpoint is `https://mcpaas.live/grok/mcp/v1`.

Connect Grok by adding the hosted URL under `[mcp_servers.grok-faf-mcp]` in `~/.grok/config.toml`. Restart the Grok TUI or run `/mcps r` to refresh MCP connections.

Yes, `refresh_faf` rereads the live `.faf`, rescoring it and reporting drift. `refresh_fafm` refreshes the `.fafm` memory layer, while `refresh_blend` runs both refresh paths with blend or nuke intensity.

It describes a hosted MCP URL for Grok and any MCP client with native `url=` configuration, plus a local stdio installation, but does not provide Cursor-specific setup.

Related MCP servers

All in Knowledge & Memory All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewGrok FAF AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/grok-faf?style=directory)](https://allmcps.com/mcp/grok-faf)
HTML Embed
<a href="https://allmcps.com/mcp/grok-faf"><img src="https://allmcps.com/api/badge/grok-faf?style=directory" alt="Grok FAF on AllMCPs" /></a>