Context Fabric MCP server
io.github.VIKAS9793/context-fabric·v1.2.2·2 starsContext sync layer for AI agents. Ensures continuity and eliminates memory drift automatically.
2 stars36 downloads/wk
Reviews
Write oneNobody has reviewed Context Fabric yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Context Fabric tools (5)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
cf_captureCapture current project state.
cf_driftCheck context drift. Returns severity.
cf_healthReport local database, capture, and hook health.
cf_log_decisionLog an architecture decision.
cf_queryGet project context briefing.
Public scan report
scanner v0.1.9 · 2026-09-25 · same rubric, same numbers if you re-run it
- Code scan53 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 0 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How Context Fabric compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 92/100
- higher than 90% of 48,273 servers
- Tools
- 5
- the typical server has 7
- Tools that change things
- 0%
- typical: 0%. Fewer write tools means less an agent can break
- GitHub stars
- 2
- more than 75% of 28,534 servers
- Downloads a week
- 36
- more than 28% of 11,915 servers with a package
What its tools let an agent do: 5 read
Install Context Fabric in Claude Code, Cursor or VS Code
Runs npx -y context-fabric on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add context-fabric -- npx -y context-fabric
What the publisher says
From the Context Fabric repository's README, as published. We do not edit it. Read it on GitHub
Context Fabric
Current stable release: v1.2.2. See CHANGELOG.md for the release notes.
Official Registry Support
Context Fabric is configured for official inclusion in the Model Context Protocol (MCP) Registry.
- Namespace: io.github.VIKAS9793/context-fabric
- Metadata: server.json
- Distribution: Published as an npm package with official MCP Registry metadata.
The context synchronization layer for AI coding agents. Ensure project continuity, eliminate agent memory drift, and manage token budgets automatically across any coding session.
Context Fabric is an MCP server that automatically captures project state on every git commit, detects when stored context has drifted from codebase reality, and delivers structured, token-budgeted briefings to AI agents — without requiring any developer action.
The Problem
Developers using AI coding agents manually construct and maintain documentation systems, session handoff rituals, and context workflows to compensate for the absence of native project continuity tooling. These workarounds share one property: they go stale after commits, and nothing detects it.
The problem is not that AI forgets. The problem is context drift — stored context becomes incorrect after code changes, and AI agents proceed with that incorrect context confidently.
Context Fabric is the infrastructure layer that solves it at the root.
CADRE — Context-Aware Drift Resolution Engine
Context Fabric is powered by CADRE, a five-engine internal architecture. Every engine solves a specific, documented failure mode observed in real developer workflows.
What CADRE is. CADRE is the automated replacement for every manual context management system developers currently build themselves. It sits between the git event stream and the AI agent, deciding what context to capture, when it has drifted, which parts are relevant to the active query, what they cost in tokens, and how to deliver them structured and reliably.
Who CADRE is for. Developers building multi-session AI-assisted software projects who currently spend time on any of the following: updating markdown files after commits, creating session-end summaries, maintaining CLAUDE.md or AGENTS.md files, building RAG pipelines for project context, or manually deciding which documentation to load before each task.
The Five Engines
E1 — WATCHER
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Context Fabric: common questions
- Is Context Fabric MCP server safe?
- Yes, by our scan: it is graded A (92/100). Read the Context Fabric safety report
- How do I install Context Fabric?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Context Fabric need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Context Fabric maintained?
- The last commit was 38 days ago (2026-09-25). The latest release is v1.2.2.
- How does Context Fabric compare with other MCP servers?
- safety score 92/100 (higher than 90% of 48,273 servers); tools 5 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.