grok-faf-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FAF_SHOW_ADVANCED | No | If set to 'true', enables 34 advanced MCP tools in addition to the 21 core tools (totaling 55 tools). |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| faf_scoreA | Score a project's AI-readiness 0–100% against the fixed 33-slot context model — how much project DNA an agent has before it has to guess. Deterministic: the same .faf always scores the same. Returns the score, tier, and per-slot breakdown. |
| refresh_fafA | Re-ground on the live .faf — re-read + re-score the current project DNA, report drift vs your last-known score, and return the fresh context. The explicit re-grounding primitive for long sessions: drift → refresh → re-grounded. Built for Grok, by request. |
| refresh_fafmA | Reload the latest structured memory ( |
| faf_orchestrate_recommendationA | Heavy orchestrator — given current substrate state, returns a structured recommendation about drift: which refresh to call (or |
| faf_get_orchestration_policyA | Introspect the effective orchestration policy WITHOUT running the orchestrator. Returns |
| refresh_blendA | Baked-in two-intensity refresh (Cmd+R / Cmd+Shift+R analog). Fires BOTH |
| faf_initA | Create a project.faf — the IANA-registered context file (application/vnd.faf+yaml) that gives Grok persistent project DNA (stack, structure, intent) in one portable file, so an agent reads the whole project cold each session instead of re-discovering it. Writes project.faf to the target directory (created if missing) and refuses to overwrite an existing context file unless |
| faf_trustA | Validate a project.faf's structure and integrity — confirm the context file is well-formed and parses cleanly before an agent grounds on it. The pre-flight trust check: never build on a broken context layer. |
| faf_syncA | Sync project.faf into your AI context files (CLAUDE.md, AGENTS.md, .cursorrules, GEMINI.md). Non-destructive: injects a structured .faf block at the top for fast machine reading and preserves your prose below. One source of truth, every tool kept current. |
| rag_queryA | Ask a question with RAG-enhanced context from xAI Collections. Uses LAZY-RAG cache for 100,000x speedup on repeated queries. |
| rag_cache_statsA | Get LAZY-RAG cache statistics - hits, misses, hit rate, cache size |
| rag_cache_clearA | Clear the LAZY-RAG cache — drop all cached retrievals so the next rag_query rebuilds from source. Use when the underlying context has changed and you want fresh results instead of cached ones. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Current FAF Context | Current project FAF context and metadata |
| FAF Status Summary | Project health and AI readiness status |
| FAF Working Directory | File system access for FAF operations |
TDQS
Scored across 12 tools
Tools are generally distinct across the three subsystems (faf, rag, refresh), but there is some overlap between refresh_faf and refresh_blend—refresh_blend always fires both refresh_faf and refresh_fafm, so an agent might wonder whether to use refresh_faf alone or the compound tool. However, descriptions are clear enough to prevent major confusion.
All tool names follow a consistent snake_case pattern with a clear subsystem prefix (faf_, rag_, refresh_). The naming is uniform and predictable, making it easy to infer the action and resource.
With 12 tools, the server is well-scoped. Each tool serves a distinct function within its subsystem, and the count feels appropriate for the domain of project context management and RAG caching—not too few, not too many.
The tool surface covers initialization, scoring, syncing, validation, orchestration, and refresh for the FAF context, plus cache management for RAG. Minor gaps exist, such as the absence of an explicit update or delete for the project.faf file (though force overwrite exists) and no tool to configure RAG parameters.