Context Fabric
Keep long-running agent sessions aligned with prior decisions by syncing context and logging choices so memory drift does not rewrite your roadmap mid-build.
Overview
Context Fabric is a MCP server for the Operate phase that syncs agent context and decision history to reduce memory drift across coding sessions.
What is this MCP server?
- Context Fabric v1.0.7 npm package context-fabric with stdio and npx runtime hint
- Sync layer focused on continuity and reducing context drift across agent sessions
- Decision-log and cadre-engine keywords in registry metadata
- Stack signals: TypeScript, SQLite, MCP, and git for local durable context
- Publisher metadata marks status stable and priority high
- Registry version 1.0.7
- npm identifier: context-fabric (npx runtime hint)
- Documented stack: TypeScript, SQLite, MCP, git
Community signal: 2 GitHub stars.
What problem does it solve?
Multi-session agent work loses prior decisions, so solo builders repeat arguments and ship inconsistent implementations after every fresh chat.
Who is it for?
Builders running long-horizon Claude Code or Cursor projects who need durable context sync beyond the model window.
Skip if: Single-shot prompts, teams with no MCP setup, or orgs that already enforce full traceability in Linear and Notion without agent hooks.
What do I get? / Deliverables
Agents pull synchronized context and decision logs so continuity holds from research through iteration without manual recap prompts.
- Synchronized agent context across sessions
- Decision log suitable for re-injection into prompts
- Reduced rework from forgotten prior choices
Recommended MCP Servers
Journey fit
Context continuity matters most when you operate and iterate on a product, but the same sync layer helps every phase where agents make incremental decisions. iterate is the canonical shelf for tooling that preserves decisions and state across sessions while you refine shipped work.
How it compares
Agent context-sync MCP with SQLite decision logging, not a brainstorming or writing-plans methodology skill.
Common Questions / FAQ
Who is io.github.VIKAS9793/context-fabric for?
Solo and indie developers using MCP agents on one product over weeks who need automatic continuity instead of pasting session summaries.
When should I use io.github.VIKAS9793/context-fabric?
Use it whenever agents revisit the same repo across phases—especially Operate iterate work—and you see repeated mistakes from forgotten decisions.
How do I add io.github.VIKAS9793/context-fabric to my agent?
Register the npm MCP server context-fabric with stdio transport (runtime hint npx) in Claude Code, Cursor, or compatible clients per the GitHub README.