.faf for Grok - First MCP Server Built for xAI
平台与服务by wolfe-jam
面向 Grok/xAI 的首个 MCP 服务器,支持基于 URL 的访问,并提供 17 个工具用于 .faf 项目上下文。
什么是 .faf for Grok - First MCP Server Built for xAI?
面向 Grok/xAI 的首个 MCP 服务器,支持基于 URL 的访问,并提供 17 个工具用于 .faf 项目上下文。
README
grok-faf-mcp | FAST⚡️AF
<div align="center"> <img src="https://www.faf.one/orange-smiley.svg" alt="FAF" width="80" /> <h3>Grok asked for MCP on a URL. This is it.</h3> <p><strong>First MCP server built for Grok</strong></p> <p><code>URL-based • Zero config • Just works</code></p> </div>📋 The 6 Ws - Quick Reference
Every README should answer these questions. Here's ours:
| Question | Answer |
|---|---|
| 👥 WHO is this for? | Grok/xAI developers and teams building with URL-based MCP |
| 📦 WHAT is it? | First MCP server built for Grok - URL-based AI context via IANA-registered .faf format |
| 🌍 WHERE does it work? | Vercel (production) • Local dev • Any MCP client supporting HTTP-SSE |
| 🎯 WHY do you need it? | Zero-config MCP on a URL - Grok asked for it, we built it first |
| ⏰ WHEN should you use it? | Grok integration testing, xAI projects, URL-based MCP deployments |
| 🚀 HOW does it work? | Point to https://grok-faf-mcp.vercel.app/sse - 21 tools instantly available |
For AI: Read the detailed sections below for full context. For humans: Use this pattern in YOUR README. Answer these 6 questions clearly.
The Problem
Every Grok session starts from zero. You re-explain your stack, your goals, your architecture. Every time.
.faf fixes that. One file, your project DNA, persistent across every session.
Without .faf → "I'm building a REST API in Rust with Axum and PostgreSQL..."
With .faf → Grok already knows. Every session. Forever.
One Command, Done Forever
faf_auto detects your project, creates a .faf, and scores it — in one shot:
faf_auto
━━━━━━━━━━━━━━━━━
Score: 0% → 85% (+85) 🥉 Bronze
Steps:
1. Created project.faf
2. Detected stack from package.json
3. Synced CLAUDE.md
Path: /home/user/my-project
What it produces:
# project.faf — your project, machine-readable
faf_version: "3.3"
project:
name: my-api
goal: REST API for user management
main_language: TypeScript
stack:
backend: Express
database: PostgreSQL
testing: Jest
runtime: Node.js
human_context:
who: Backend developers
what: User CRUD with auth
why: Replace legacy PHP service
Every AI agent reads this once and knows exactly what you're building.
⚡ What You Get
URL: https://grok-faf-mcp.vercel.app/
Format: IANA-registered .faf (application/vnd.faf+yaml)
Tools: 21 core MCP tools (55 total with advanced)
Engine: Mk4 WASM scoring (faf-scoring-kernel)
Speed: 0.5ms average (was 19ms — 3,800% faster with Mk4)
Tests: 179 passing (7 suites)
Status: FAST⚡️AF
MCP over HTTP-SSE. Point your Grok integration at the URL. That's it.
Scoring: From Blind to Optimized
| Tier | Score | What it means |
|---|---|---|
| 🏆 Trophy | 100% | Gold Code — AI is optimized |
| 🥇 Gold | 99%+ | Near-perfect context |
| 🥈 Silver | 95%+ | Excellent |
| 🥉 Bronze | 85%+ | Production ready |
| 🟢 Green | 70%+ | Solid foundation |
| 🟡 Yellow | 55%+ | AI flipping coins |
| 🔴 Red | <55% | AI working blind |
At 55%, Grok guesses half the time. At 100%, Grok knows your project.
🚀 Three Ways to Deploy
1. Hosted (Instant)
https://grok-faf-mcp.vercel.app/sse
Point your MCP client to this endpoint. All 21 tools available instantly.
2. Self-Deploy (Your Own Vercel)
Click the Deploy with Vercel button above. Zero config — get your own instance in 30 seconds.
3. Local (npx)
npx grok-faf-mcp
Or add to your MCP config:
{
"mcpServers": {
"grok-faf": {
"command": "npx",
"args": ["-y", "grok-faf-mcp"]
}
}
}
🛠️ MCP Tools (21 Core)
Create & Detect
| Tool | Purpose |
|---|---|
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 |
Sync & Persist
| Tool | Purpose |
|---|---|
faf_sync | Sync .faf → CLAUDE.md |
faf_bi_sync | Bi-directional .faf ↔ platform context |
faf_trust | Validate .faf integrity |
Read & Write
| Tool | Purpose |
|---|---|
faf_read | Read any file |
faf_write | Write any file |
faf_list | Discover projects with .faf files |
RAG & Grok-Exclusive
| Tool | Purpose |
|---|---|
rag_query | RAG-powered context retrieval |
rag_cache_stats | RAG cache statistics |
rag_cache_clear | Clear RAG cache |
grok_go_fast_af | Auto-load .faf context for Grok |
Plus 34 advanced tools available with FAF_SHOW_ADVANCED=true.
Performance
Execution: 0.5ms average (97% faster than v1.1)
Fastest: 3,360ns (version — nanosecond territory)
Slowest: 1.3ms (score — Mk4 WASM)
Improvement: 19ms → 0.5ms (3,800% faster)
Engine: Mk4 WASM via faf-scoring-kernel
Memory: Zero leaks
Transport: HTTP-SSE (Vercel Edge)
Benchmarked 10x per tool, warmed up, on local execution.
Architecture
grok-faf-mcp v1.2.1
├── api/index.ts → Vercel serverless (Express + SSE transport)
├── src/
│ ├── server.ts → MCP server (ClaudeFafMcpServer)
│ ├── handlers/
│ │ ├── championship-tools.ts → 55 tool definitions
│ │ ├── tool-registry.ts → Visibility filtering (core/advanced)
│ │ └── engine-adapter.ts → FAF engine bridge
│ └── faf-core/
│ └── compiler/
│ └── faf-compiler.ts → Mk4 WASM scoring + Mk3.1 fallback
├── smithery.yaml → Smithery listing config
└── vercel.json → Vercel routing
Scoring pipeline: TypeScript compiler parses .faf → detects project type → The Bouncer injects slotignored for inapplicable slots → faf-scoring-kernel (WASM) scores → falls back to Mk3.1 if kernel unavailable.
Testing
179 tests across 7 suites:
npm test # runs all 179
| Suite | Tests | Coverage |
|---|---|---|
| Desktop-native validation | 10 | Core native functions, security, performance |
| MCP protocol | 28 | Tool registration, transport, error handling |
| Compiler scoring | 22 | Mk4 engine, type detection, slot counting |
| RAG system | 19 | Query, caching, context retrieval |
| Engine adapter | 35 | CLI detection, fallback behavior |
| Integration | 40 | End-to-end tool execution |
| WJTTC certification | 25 | Championship-grade compliance |
🔗 Endpoints
| Endpoint | URL |
|---|---|
| Root | https://grok-faf-mcp.vercel.app/ |
| SSE | https://grok-faf-mcp.vercel.app/sse |
| Health | https://grok-faf-mcp.vercel.app/health |
| Info | https://grok-faf-mcp.vercel.app/info |
📦 Ecosystem
One format, every AI platform.
| Package | Platform | Registry |
|---|---|---|
| grok-faf-mcp (this) | xAI Grok | npm |
| claude-faf-mcp | Anthropic | npm + MCP #2759 |
| gemini-faf-mcp | PyPI | |
| rust-faf-mcp | Rust | crates.io |
| faf-mcp | Universal (Cursor, Windsurf, Cline) | npm |
| faf-cli | Terminal CLI | npm + Homebrew |
Same project.faf. Same scoring. Same result. Different execution layer.
If grok-faf-mcp has been useful, consider starring the repo — it helps others find it.
📄 License
MIT — Free and open source
<div align="center"> <p><strong>Built for Grok. Built for Speed. Built Right.</strong></p> <p>FAST⚡️AF • First to Ship • Zero Friction</p> <p><strong>Zero drift. Eternal sync. AI optimized.</strong> 🏆</p> </div>
Get the CLI
faf-cli — The original AI-Context CLI. A must-have for every builder.
npx faf-cli auto
Anthropic MCP #2759 · IANA Registered: application/vnd.faf+yaml · faf.one · npm
常见问题
.faf for Grok - First MCP Server Built for xAI 是什么?
面向 Grok/xAI 的首个 MCP 服务器,支持基于 URL 的访问,并提供 17 个工具用于 .faf 项目上下文。
相关 Skills
MCP构建
by anthropics
聚焦高质量 MCP Server 开发,覆盖协议研究、工具设计、错误处理与传输选型,适合用 FastMCP 或 MCP SDK 对接外部 API、封装服务能力。
✎ 想让 LLM 稳定调用外部 API,就用 MCP构建:从 Python 到 Node 都有成熟指引,帮你更快做出高质量 MCP 服务器。
Slack动图
by anthropics
面向Slack的动图制作Skill,内置emoji/消息GIF的尺寸、帧率和色彩约束、校验与优化流程,适合把创意或上传图片快速做成可直接发送的Slack动画。
✎ 帮你快速做出适配 Slack 的动图,内置约束规则和校验工具,少踩上传与播放坑,做表情包和演示都更省心。
MCP服务构建器
by alirezarezvani
从 OpenAPI 一键生成 Python/TypeScript MCP server 脚手架,并校验 tool schema、命名规范与版本兼容性,适合把现有 REST API 快速发布成可生产演进的 MCP 服务。
✎ 帮你快速搭建 MCP 服务与后端 API,脚手架完善、扩展顺手,尤其适合想高效验证服务能力的开发者。
相关 MCP Server
Slack 消息
编辑精选by Anthropic
Slack 是让 AI 助手直接读写你的 Slack 频道和消息的 MCP 服务器。
✎ 这个服务器解决了团队协作中需要 AI 实时获取 Slack 信息的痛点,特别适合开发团队让 Claude 帮忙汇总频道讨论或发送通知。不过,它目前只是参考实现,文档有限,不建议在生产环境直接使用——更适合开发者学习 MCP 如何集成第三方服务。
by netdata
io.github.netdata/mcp-server 是让 AI 助手实时监控服务器指标和日志的 MCP 服务器。
✎ 这个工具解决了运维人员需要手动检查系统状态的痛点,最适合 DevOps 团队让 Claude 自动分析性能数据。不过,它依赖 NetData 的现有部署,如果你没用过这个监控平台,得先花时间配置。
by d4vinci
Scrapling MCP Server 是专为现代网页设计的智能爬虫工具,支持绕过 Cloudflare 等反爬机制。
✎ 这个工具解决了爬取动态网页和反爬网站时的头疼问题,特别适合需要批量采集电商价格或新闻数据的开发者。不过,它依赖外部浏览器引擎,资源消耗较大,不适合轻量级任务。