Partnership Proposal: FAF + Context7 = Complete AI Context

[Wolfe-Jam]

The Opportunity

Context7 brilliantly solves library documentation context.
FAF solves project-specific context.

Together: Complete context for any AI coding session.

The Synergy

Context7	FAF
"How does React Router work?"	"How does OUR routing work?"
Library APIs, version-specific	Project architecture, team conventions
External documentation	Internal DNA

Use both: use context7 for library docs + project.faf for YOUR codebase.

Why FAF?

• IANA-registered format: application/vnd.faf+yaml
• Merged into Anthropic's official MCP servers (PR #2759)
• 28k+ npm downloads across ecosystem
• Works everywhere: Claude, Cursor, Windsurf, Codex, any MCP client
• Just published to Smithery alongside Context7

Integration Ideas

1. Simple: Recommend FAF in Context7 docs as complementary tool
2. Medium: Context7 reads project.faf to understand which libraries matter
3. Deep: Unified context layer - both tools working together

Resources

• Website: https://faf.one
• npm: https://npmjs.com/package/claude-faf-mcp
• GitHub: https://github.com/Wolfe-Jam/claude-faf-mcp
• Smithery: https://smithery.ai/server/wolfe-jam/claude-faf-mcp

Happy to discuss further!

— @Wolfe-Jam

[aniruddhaadak80]

The complementarity argument makes sense, but I think the hard part is not whether external docs context and project-local context are both useful. That part is obvious. The hard part is how they are merged, ranked, and trusted when they disagree or overload the model window.nnIf something like this ever goes deeper than a partnership mention, I would want the integration story to focus on precedence and context budgeting first. Otherwise complete context quickly turns into noisy context.

[Wolfe-Jam]

@aniruddhaadak80 good question — context budgeting is the right thing to worry about.

A few things that help here:

• Size difference: a typical project.faf is ~50 lines / ~800 tokens. Library docs from Context7 can be thousands. They're not competing for the same space.
• Natural precedence: project context ("how WE do routing") always trumps library defaults ("how React Router works"). It's a hierarchy, not a merge.
• Priority truncation: the FAF binary format (FAFb) has section priorities baked in. If the window is tight, low-priority sections drop first. The budget problem is handled at compile time, not runtime.

The short version: structured YAML + priority truncation means "complete context" doesn't have to mean "noisy context."

Would be great to hear from the Context7 team on how they think about this from their side.