agentleFS
Wolfe-JamWolfe-Jam/grok-faf-mcp/CLAUDE.md

grok-faf-mcp

CLAUDE.md19 starsChanged 10 months agoMITView on GitHub

Persistent project context for xAI Grok. The first MCP for Grok — Grok asked for MCP on a URL. STATUS: SYNC ACTIVE — 2026-11-05T18:02:00.133Z <!-- faf:end -->

The file

We split this CLAUDE.md into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Why: Every AI session starts from zero.

    line 25

≈ “Common” is an estimate: at least 1 in 5 of the 28,029 CLAUDE.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
CLAUDE.md
<!-- faf:start --><!-- faf: grok-faf-mcp | TypeScript | mcp | Persistent project context for xAI Grok. The first MCP for Grok — Grok asked for MCP on a URL. --><!-- faf: claim=project.faf | family=FAF -->

CLAUDE.md — grok-faf-mcp

What This Is

Persistent project context for xAI Grok. The first MCP for Grok — Grok asked for MCP on a URL.

Stack

  • Language: TypeScript
  • Backend: MCP SDK (TS)
  • API: MCP (stdio + Streamable HTTP)
  • Runtime: Node.js
  • Hosting: Cloudflare Workers
  • Build: TypeScript (tsc)
  • CI/CD: GitHub Actions

Context

  • Who: Developers using xAI Grok with MCP
  • What: First MCP for Grok — also first FAF MCP online. Persistent AI context via IANA-registered .faf + .fafm.
  • Why: Every AI session starts from zero. grok-faf-mcp gives Grok persistent project DNA.
  • Where: npm registry, Cloudflare Workers (mcpaas.live/grok/mcp/v1), MCP Registry (one.faf/grok-faf-mcp)
  • When: Shipped 2026-10-27 — current v2.2.4 The Instructions Edition (initialize tells Grok how its tools fit together, context and memory; faf-cli 8.5.0 inside, which detects skills repos). v2.1.0 The New Era Edition (2026-10-05): every tool says if it reads, writes or rewrites. v2.0.0 The Always33 Edition (2026-09-27): every score is faf-cli 8's always-33 kernel.
  • How: bunx grok-faf-mcp (local stdio) or hosted on Cloudflare Workers (mcpaas.live/grok/mcp/v1) — 12 core tools by default (extended set behind FAF_TOOLS=all), Streamable HTTP transport, Mk4 WASM scoring kernel

STATUS: SYNC ACTIVE — 2026-11-05T18:02:00.133Z

<!-- faf:end -->

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.