# Grok FAF

Keeps your project description in a .faf file and lets the agent score, check and analyse it. Installs with one npx line.

- MCP server · `type=mcp` · Claude Code, Codex, Cursor, GitHub Copilot, Windsurf (Devin Desktop), Cline, Zed, Gemini CLI · ★ 19
- Author: Wolfe-Jam
- License: MIT · policy=link-only · description only; the file stays with the author
- Source: https://github.com/Wolfe-Jam/grok-faf-mcp
- Updated: 2026-10-23
- HTML: https://affpapa.org/en/nevibecode/mcp/grok-faf

## What it does

The server stores project context in `project.faf` and exposes tools such as `faf_score`, `faf_validate`, `faf_get_tier`, `faf_estimate_tokens` and `faf_analyze`. Since v2.1 each tool carries an annotation saying whether it only reads, writes, or can overwrite — handy when your client decides what to confirm first.

Run it locally with `npx` over stdio, so any MCP client that supports stdio can use it. A hosted endpoint also exists at `https://mcpaas.live/grok/mcp/v1`. Only `rag_query` touches the network, through Anthropic Collections.

Node 22 or later is required. Several tools (`refresh_faf`, `refresh_fafm`, `refresh_blend`, `faf_gate`, `faf_section`, `faf_memory`) drop small receipt files into your project folder, so untracked files will show up — keep that in mind when the directory is under version control.

## Requirements
- Needs: Node.js (commands run via npx)

## Install

### Claude Code (native platform)

**Platform CLI**
```bash
claude mcp add grok-faf-mcp -- npx -y grok-faf-mcp
```

### Codex

**Platform CLI**
```bash
codex mcp add grok-faf -- npx -y grok-faf-mcp
```

### Cursor

**Config file**
File `.cursor/mcp.json`:
```json
{
    "mcpServers": {
        "grok-faf": {
            "command": "npx",
            "args": [
                "-y",
                "grok-faf-mcp"
            ]
        }
    }
}
```

### GitHub Copilot

**Config file**
File `.vscode/mcp.json`:
```json
{
    "servers": {
        "grok-faf": {
            "type": "stdio",
            "command": "npx",
            "args": [
                "-y",
                "grok-faf-mcp"
            ]
        }
    }
}
```

### Gemini CLI

**Platform CLI**
```bash
gemini mcp add grok-faf npx -y grok-faf-mcp
```

## When to use it
- keep one project description file the agent can read
- validate the `.faf` file before committing
- estimate how many tokens the project context costs
- see whether the project description is complete enough
- wipe stale context with a single tool call

## Example prompts
- Score `project.faf` and tell me what's missing.
- Validate the `.faf` file and list the problems.
- How many tokens will this context file use?

## Similar
- [REA](https://affpapa.org/en/nevibecode/mcp/rea.md) — MCP server · ★ 386989
- [GitHub](https://affpapa.org/en/nevibecode/mcp/github.md) — MCP server · ★ 33918
- [Netdata](https://affpapa.org/en/nevibecode/mcp/netdata.md) — MCP server · ★ 81115
- [browser-use](https://affpapa.org/en/nevibecode/mcp/browser-use.md) — MCP server · ★ 119160
- [Codebase Memory](https://affpapa.org/en/nevibecode/mcp/codebase-memory.md) — MCP server · ★ 47392
- [mcp-server](https://affpapa.org/en/nevibecode/mcp/mcp-server.md) — MCP server · ★ 43872

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md