Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"grok-faf": {
"args": [
"-y",
"grok-faf-mcp"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Every README should answer these questions. Here's ours:
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y 'grok-faf-mcp' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
Checked grok-faf-mcp against OSV.dev.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in ai-ml
Persistent memory using a knowledge graph
Privacy-first. MCP is the protocol for tool access. We're the virtualization layer for context.
An open-source AI agent that brings the power of Gemini directly into your terminal.
Just a Better Chatbot. Powered by Agent & MCP & Workflows.
MCP Security Weekly
Get CVE alerts and security updates for io.github.Wolfe-Jam/grok-faf-mcp and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Persistent Project Context for xAI Grok.
URL-based • Zero config • Just works
FAF defines. MD instructs. AI codes.
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? | Persistent project context for xAI Grok — URL-first deployment, 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 — context tools served via MCP SSE |
For AI: Read the detailed sections below for full context. For humans: Use this pattern in YOUR README. Answer these 6 questions clearly.
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.
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.
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: 169 passed · 0 failed · 169 total (7 suites)
Status: FAST⚡️A
... [View full README on GitHub](https://github.com/Wolfe-Jam/grok-faf-mcp#readme)