I got tired of hand-syncing AI coding rules across four tools
Sync AI coding configs across Claude, Cursor, Copilot with bidirectional import and CI checks.
Persistent Project Context for Claude — IANA-registered .faf format · 32 tools + 1 prompt · MCP Registry #2759
IANA-registered .faf format with bi-sync, but only solves for power-users juggling 4+ tools.
Engineers using multiple AI coding tools simultaneously and wasting time on config sync
Anthropic MCP servers · Cursor configuration management
I kept forgetting to update one, then wondering why Cursor was hallucinating my project structure while Claude had it right.
So I built an MCP server that reads a single YAML file (project.faf) and generates all four formats. 7 bundled parsers handle the differences between them. You edit one file, and bi-sync keeps everything current.
It's an MCP server, so Claude Desktop can use it directly. 61 tools, 351 tests, no CLI dependency.
Try it: npx claude-faf-mcp
Source: https://github.com/Wolfe-Jam/claude-faf-mcp
The .faf format itself is IANA-registered (application/vnd.faf+yaml).
Curious if others are dealing with this multi-AI config problem, or if there's a simpler approach I'm not seeing.
Sync AI coding configs across Claude, Cursor, Copilot with bidirectional import and CI checks.
MCP-based dashboard for Claude Code agents, but agent management tools are multiplying weekly.
npm install for agent skills that copies prompts into Claude, Cursor, and Gemini instantly.
x402 pay-per-invocation billing is a genuinely novel approach to agent economics.
Seven AI agents with different worldviews beat Ground News human curation.
Syncs MCP configs across Cursor, Copilot, Claude—but still fragmented tool ecosystem.