mindswap_get_contextLABSCO SUMMARY
Plain files first, index second.
Everything is readable Markdown, JSON and a log — the SQLite index is derived and can be rebuilt with one command, so nothing important is trapped in a database. The two scopes are the design choice that matters: a decision about this repository and a preference about how you like explanations are different things and get stored separately.
What it is
A local-first continuity tool for AI coding sessions. It captures what you were doing — task, git state, decisions — into files under .mindswap/, and serves that same context to AI clients over MCP so the next tool picks up cleanly instead of starting cold.
What you get
- A repository set up and existing AI context imported —
init; the current task, git state and decisions captured —save - Setup health and stale context checked —
doctor; a clean briefing to start from —resume - Project memory searched with citations —
ask; blockers, assumptions, questions and resolutions managed —memory - Two memory scopes: repo memory in
<repo>/.mindswap/and personal memory in~/.mindswap/, with--globalfor preferences that should follow you across projects - The local SQLite search index rebuilt from the file-based memory —
reindex; continuity state shared across machines —sync - The same context exposed to AI clients —
mcpandmcp-http, withmcp-installto wire up a client - Generated context for Claude Code, Cursor, Copilot, Codex, Windsurf, Cline, Roo, Aider, Amp, Gemini CLI and AGENTS.md-based workflows
Requirements
No account and no key — memory lives in plain files on your machine. Install with npm install mindswap --save-dev, then npx mindswap init. The MCP entry runs the mindswap package with the positional argument mcp over stdio; version 3.3.0, MIT licensed. Repository state sits in .mindswap/ as HANDOFF.md, state.json, decisions.log, memory.json, config.json, plus branches/ and history/.
Setup effort
One command — npm install mindswap --save-dev
USE CASES
01
Restarting a project after a week away
Ask for a briefing and start from the recorded task, decisions and blockers instead of re-reading your own commits.
02
Answering "why did we do it this way"
Search the project memory and get the answer with citations back to where it was recorded.
03
Carrying a preference between projects
Log it to the personal scope so it follows you across repositories and tools rather than living in one project.
04
Handing a session to a different AI tool
Save the state, then let the next client read the same context over MCP.
3 tools
Listed in project docs. Your client may show a different list.
mindswap_save_contextmindswap_searchBEFORE YOU INSTALL
What to know first
Tools you get
3 tools named in the project's documentation.
Requires
npx on PATH
INSTALLATION
Connect your client
Add the block to your client, or run the command directly.
Server setup
Configuration file
JSON
{
"mcpServers": {
"mindswap": {
"command": "npx",
"args": [
"mindswap"
]
}
}
}npm
TERMINAL
npm install mindswap --save-dev
