by Intina47
Local persistent memory store for LLM applications including continue.dev, cursor, claude desktop, github copilot, codex, antigravity, etc.
# Add to your Claude Code skills
git clone https://github.com/Intina47/context-syncGuides for using mcp servers skills like context-sync.
Last scanned: 5/30/2026
{
"issues": [
{
"type": "npm-audit",
"message": "@modelcontextprotocol/sdk: Anthropic's MCP TypeScript SDK has a ReDoS vulnerability",
"severity": "high"
},
{
"type": "npm-audit",
"message": "simple-git: simple-git Affected by Command Execution via Option-Parsing Bypass",
"severity": "critical"
}
],
"status": "FAILED",
"scannedAt": "2026-05-30T16:01:29.887Z",
"npmAuditRan": true,
"pipAuditRan": true
}context-sync is an open-source mcp servers skill for AI coding assistants such as Claude Code, Codex CLI, and ChatGPT, built by Intina47. Local persistent memory store for LLM applications including continue.dev, cursor, claude desktop, github copilot, codex, antigravity, etc. It has 182 GitHub stars.
context-sync failed SkillsLLM's automated security scan, which flagged one or more high-severity issues. Review the Security Report section carefully before using it.
Clone the repository with "git clone https://github.com/Intina47/context-sync" and add it to your Claude Code skills directory (see the Installation section above).
context-sync is primarily written in TypeScript. It is open-source under Intina47 on GitHub, so you can review or fork the full source.
Yes. SkillsLLM lists many other MCP Servers skills you can browse and compare side by side. Open the MCP Servers category from the badge at the top of this page, or use the Related Skills and comparison links further down to weigh context-sync against similar tools.
No comments yet. Be the first to share your thoughts!
Top skills in this category by stars
Requires a passing catalog security scan. Resolve the flagged issues and resubmit to enable featuring.
Local-first project memory for AI coding tools over MCP.
Context Sync gives an agent a persistent memory layer for a codebase:

Context Sync is built for session continuity. Instead of relying on a model to remember earlier conversations, it stores the project context that matters and makes it retrievable through a small MCP tool surface.
The current core tools are:
set_projectrememberrecallread_filesearchstructuregitnotionInstall globally:
npm install -g @context-sync/server
Auto-configuration runs during global install. After install, restart your AI tool.
If you install locally instead of globally, auto-config does not run. Use the manual config guide in docs/CONFIG.md.
Check that context-sync appears in your MCP tool list:
codex mcp listclaude mcp listIf auto-config fails, use docs/TROUBLESHOOTING.md and docs/CONFIG.md.
Run the setup wizard if you want Notion integration:
context-sync-setup
or:
npx context-sync-setup
Notion support is intentionally read-only at the tool surface:
notion({ action: "search", query: "..." })notion({ action: "read", pageId: "..." })Start every new session by setting the project first:
1. set_project({ path: "/absolute/path/to/project" })
2. recall()
3. structure({ depth: 2 })
4. read_file({ path: "src/index.ts" })
5. remember({ type: "decision", content: "Use SQLite for local storage" })
Recommended pattern:
set_project once per project/session startrecall to recover contextstructure and search to exploreread_file for focused inspectionremember when something should survive the current sessionWhen you run set_project inside a git repository, Context Sync can install hooks for automatic context capture.
Installed hooks:
post-commitpre-pushpost-mergepost-checkoutHooks are marked with Context Sync Auto-Hook, and existing hooks are backed up first.
The git tool supports:
statuscontexthotspotscouplingblameanalysisDefault locations:
~/.context-sync/data.db~/.context-sync/config.json~/.context-sync/install-status.jsonCustom database options:
context-sync --db-path /absolute/path/to/dbCONTEXT_SYNC_DB_PATHSee docs/DATA.md for storage details.