Mindswap

io.github.ShipOrBleedPublished by GitHub account ShipOrBleedv3.3.0Updated Oct 24, 2026

Local-first AI context and memory server for cross-tool coding continuity.

VerifiedSTDIODesktop onlyKnowledge & MemoryDeveloper Tools

Overview

AI-generated overview

Local-first memory server that saves coding task context, decisions and blockers so AI tools can resume work without re-explaining.

What you can do
  • Save and resume project context: capture the current task, git state and decisions, then start a session with a clean briefing
  • Search project memory with citations and ask questions about past decisions
  • Manage blockers, assumptions, questions and resolutions in repo or global personal memory
  • Set up a repo, import existing AI context, check setup health and stale context, and rebuild the local SQLite search index
  • Share continuity state across machines and expose the same context to AI clients over MCP
When to use it
Useful when you switch between several AI coding tools or sessions and keep losing context, or want decisions and handoff notes stored locally in the repository and reused across projects.
Requirements
Runs as a local process installed from the npm package mindswap (Node.js). No accounts, API keys or environment variables are declared. Memory is stored in files under the repo's .mindswap directory and, for global scope, under the user's home directory.
Before you install
It writes context files into the repository and into a personal home-directory store, and the sync command shares continuity state across machines, so review what is captured before syncing. Saved context may include task details, decisions and git state.

Installation

In SourceWeft

  1. Open Mindswap in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

mindswap

[npm version] [License: MIT]

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.

Install

bash
npm install mindswap --save-dev

Quick start

bash
npx mindswap initnpx mindswapnpx mindswap doctornpx mindswap resumenpx mindswap ask "Why did we choose JWT?"

What it gives you

  • init to set up a repo and import existing AI context
  • save to capture the current task, git state, and decisions
  • doctor to check setup health and stale context
  • resume to start with a clean briefing
  • ask to search project memory with citations
  • memory to manage blockers, assumptions, questions, and resolutions
  • --global memory and ask scope for personal cross-tool memory under ~/.mindswap/
  • reindex to rebuild the local SQLite search index from your file-based memory
  • sync to share continuity state across machines
  • mcp and mcp-http to 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.

bash
npx mindswap log "Prefer concise explanations" --type assumption --globalnpx mindswap memory list --scope allnpx mindswap ask "What explanation style should we use?" --scope allnpx mindswap reindex --scope all

MCP 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.

bash
npx mindswap mcp-installnpx mindswap mcp-http

Project state

The main repo data lives in .mindswap/:

text
.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.

Source: README.md at commit 83bedef

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v3.3.0LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts