.Faf MCP Server

Universal project context for all MCP platforms. Auto-detects CLI, 50 MCP tools. The .faf mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 14 defined tools rather than through you.

What it actually does

Its toolset

Everything the assistant can do here goes through one of these:

• faf_agents — OpenAI Codex
• faf_cursor — Cursor IDE
• faf_gemini — Google Gemini
• faf_conductor — Conductor
• faf_git — GitHub
• faf_init — Initialize project.faf
• faf_score — Check AI-readiness (0-100%)
• faf_sync — Sync context across platforms
• faf_bi_sync — Bi-directional .faf ↔ CLAUDE.md
• faf_read — Parse and validate FAF files
• faf_write — Create/update FAF with validation
• faf_cloud_publish — Upload to mcpaas.live

Adding it to your client

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

When to reach for it

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. .Faf's toolset — faf_agents, faf_cursor, faf_gemini and 11 more — is a fair guide to whether it matches your workflow. It is maintained by Wolfe-Jam; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Caveats

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch .Faf.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the .faf mcp server does with a few real requests.