First MCP server for Grok/xAI. URL-based access. 17 tools for .faf project context.
First MCP server for Grok/xAI. URL-based access. 17 tools for .faf project context. Exposed over MCP by the .faf for grok mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.
Persistent Project Context for xAI Grok. URL-based • Zero config • Just works
Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.
Everything the assistant can do here goes through one of these:
faf_init — Create project.faf from your projectfaf_auto — Auto-detect stack and populate contextfaf_score — AI-readiness score (0-100%) with breakdownfaf_status — Check current AI-readabilityfaf_enhance — Intelligent enhancementrefresh_faf — Re-ground on the live .faf — re-read + re-score, report drift, return fresh DNA (drift → refresh → re-grounded). Requested by Grok.refresh_fafm — Re-ground on the live .fafm memory layer for one or more souls. Returns a stamped delta (added/updated facts) by default; verbatim: true for fullrefresh_blend — The baked-in two-intensity refresh (Cmd+R / Cmd+Shift+R analog). mode: "blend" (default) fires refresh_faf (light) + refresh_fafm (delta); modefaf_orchestrate_recommendation — The heavy orchestrator. Reads current substrate state, composes the full 1.5 library substrate (drift detection · CheckID · repeat-offender ·faf_get_orchestration_policy — Pure introspection of the effective policy WITHOUT running the orchestrator. Returns { tier, thresholds, source, overrides_applied } — whatfaf_sync — Sync .faf → CLAUDE.mdfaf_bi_sync — Bi-directional .faf ↔ platform contextPlenty of knowledge and memory servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. .Faf For Grok's toolset — faf_init, faf_auto, faf_score and 11 more — is a fair guide to whether it matches your workflow. It is maintained by Wolfe-Jam; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| faf_init | Create project.faf from your project |
| faf_auto | Auto-detect stack and populate context |
| faf_score | AI-readiness score (0-100%) with breakdown |
| faf_status | Check current AI-readability |
| faf_enhance | Intelligent enhancement |
| refresh_faf | Re-ground on the live .faf — re-read + re-score, report drift, return fresh DNA (drift → refresh → re-grounded). **Requested by Grok.** |
| refresh_fafm | Re-ground on the live .fafm memory layer for one or more souls. Returns a stamped delta (added/updated facts) by default; verbatim: true for full content. Read-only · always stamped. Sister to refresh_faf for the RAM/mem |
| refresh_blend | The baked-in two-intensity refresh (Cmd+R / Cmd+Shift+R analog). mode: "blend" (default) fires refresh_faf (light) + refresh_fafm (delta); mode: "nuke" fires both at hard intensity. Blend is **BAKED IN, NOT a dial** — bo |
| faf_orchestrate_recommendation | The heavy orchestrator. Reads current substrate state, composes the full 1.5 library substrate (drift detection · CheckID · repeat-offender · take-a-hint · refresh history), returns a structured Recommendation with recom |
| faf_get_orchestration_policy | Pure introspection of the effective policy WITHOUT running the orchestrator. Returns { tier, thresholds, source, overrides_applied } — what aggressiveness tier the next orchestration call would use, and whether it came f |
| faf_sync | Sync .faf → CLAUDE.md |
| faf_bi_sync | Bi-directional .faf ↔ platform context |
| faf_trust | Validate .faf integrity |
| faf_read | Read any file |
**Or via MCP config:**
```json
{
"mcpServers": {
"grok-faf": {
"command": "bunx",
"args": ["grok-faf-mcp"]
}
}
}Configuration as documented by the project. Restart the client after saving.
A knowledge graph your assistant keeps between sessions — entities, relations and observations that persist.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
A structured scratchpad for hard problems — stepwise reasoning with revisions, branches and visible logic.
Symbol-level code navigation, refactoring and memory for coding agents — the IDE brain your assistant has been missing.
Chat with your second brain — search, read and write vault notes through the Local REST API.