MindSwap
mindswap
Keep project context and personal AI memory local so tools can continue work without re-explaining the same context.
Why it exists
AI sessions reset too often. mindswap saves the current task, decisions, blockers, and handoff context so the next tool can pick up cleanly.
Related MCP server: LLM Memory MCP Server
Install
npm install mindswap --save-devQuick start
npx mindswap init
npx mindswap
npx mindswap doctor
npx mindswap resume
npx mindswap ask "Why did we choose JWT?"What it gives you
initto set up a repo and import existing AI contextsaveto capture the current task, git state, and decisionsdoctorto check setup health and stale contextresumeto start with a clean briefingaskto search project memory with citationsmemoryto manage blockers, assumptions, questions, and resolutions--globalmemory and ask scope for personal cross-tool memory under~/.mindswap/reindexto rebuild the local SQLite search index from your file-based memorysyncto share continuity state across machinesmcpandmcp-httpto expose the same context to AI clients
Global personal memory
MindSwap now supports two local memory scopes:
repo memory in
<repo>/.mindswap/personal memory in
~/.mindswap/
Use global memory when a preference or learning should follow you across projects and tools.
npx mindswap log "Prefer concise explanations" --type assumption --global
npx mindswap memory list --scope all
npx mindswap ask "What explanation style should we use?" --scope all
npx mindswap reindex --scope allMCP and AI tools
mindswap generates context for tools like Claude Code, Cursor, Copilot, Codex, Windsurf, Cline, Roo, Aider, Amp, Gemini CLI, and AGENTS.md-based workflows.
npx mindswap mcp-install
npx mindswap mcp-httpProject state
The main repo data lives in .mindswap/:
.mindswap/
├── HANDOFF.md
├── state.json
├── decisions.log
├── memory.json
├── config.json
├── branches/
└── history/npm package
Use it
If mindswap helps your workflow, star the repo and keep improving the handoff loop.
This server cannot be deployed
Maintenance
Related MCP Connectors
Local-first, governed memory and session continuity for AI coding agents. No cloud, no telemetry.
1Shared memory for coding agents. Stop re-explaining your codebase every session.
Private-by-default, local-first memory/context/task orchestrator for MCP apps and agents.
shared AI-context layer for teams — persistent memory your agents search and update over MCP
Related MCP Servers
- AlicenseAqualityBmaintenanceA local-first MCP server for shared memory across AI tools, enabling context capture and resume across sessions.2627 npm4Apache 2.0
- FlicenseNot gradedqualityFmaintenanceA local-first, team-ready MCP server providing durable memory for LLM-based coding workflows with multiple storage backends and fast search.4-
- AlicenseAqualityCmaintenanceA lightweight, local-first MCP server and CLI that helps developers and AI coding agents store and retrieve lessons learned during development, using SQLite and context-aware filtering.6MIT
- AlicenseNot gradedqualityBmaintenanceLocal-first MCP server that persists AI coding agent memory and session context, enabling seamless resume across sessions with searchable memories and checkpoints.4 npm1MIT