MindSwap MCP

MindSwap exposes local project context and personal memory to assistants so tasks, decisions and handoffs can carry across sessions.

Local + remotestdioJavaScriptMIT

What is the MindSwap MCP Server?

MindSwap exposes local project context and personal memory to assistants so tasks, decisions and handoffs can carry across sessions.

Continue work with stored context

MindSwap records project state, decisions, blockers and handoff information in a local .mindswap directory. A separate personal scope lives under the user's home directory. MCP exposes this context to a compatible assistant, while the CLI provides setup, saving, search and health checks.

Select the memory scope

Repository memory and personal memory serve different purposes. Keep a project-specific decision with the repository; use the global scope for a preference that should follow you across projects. Search results should be checked against their cited memory rather than treated as a complete history of the codebase.

Connect from the project

The npm package supplies a local MCP mode and a separate HTTP mode. Initialize the intended repository, run the documented setup check and register the local stdio configuration. Save one test decision and ask for it from a new session. If the search index is stale, inspect the stored files and rebuild the index using the project's reindex workflow.

Project documentation

Repository and setup guide

How to install the MindSwap MCP Server

{
  "mcpServers": {
    "mindswap": {
      "command": "npx",
      "args": [
        "mindswap",
        "mcp"
      ]
    }
  }
}

Configuration

Node.js, an initialized MindSwap project and access to its local state files.

Frequently asked questions

Project state is stored under the repository’s .mindswap directory. Personal memory uses a separate global directory.