maxkle1nz/m1nd

**m1nd is a local code graph and evidence-linked memory for MCP coding agents.** Find connected code, inspect the impact of a change, and carry verified findings into the next session. Answers include trust signals and explicit gaps so your agent knows what still needs checking.
Built for developers working across unfamiliar repositories, multi-file changes, or repeated agent sessions. Use your existing MCP host; the runtime is Rust and the license is MIT.
Get started · Workflows · Limits · Documentation
Why add it to your agent?
- **Start with the repo's structure.** north combines task context, bounded source excerpts, binding trust, prior memory, and a suggested next move. seek finds candidates; impact helps inspect their neighbors before editing.
- **Keep findings attached to code.** memorize stores claims with evidence paths and provenance. The next session can recall them and check whether they still apply.
- **Share context across agents.** A served local owner can share one graph with attached clients. Presence and overlap warnings help agents coordinate; they are advisory, not locks.
- **See uncertainty.** reverify, abstain, and insufficient_evidence are useful results. A graph connection is a reason to inspect code, not proof that a change is safe.
The graph and memory live on your machine. m1nd does not require an LLM API key for graph queries. Installation, updates, optional model downloads, and network-backed document providers can use the network or transmit documents to a configured endpoint; your MCP host has its own data policy.
Get started
**Version matters:** GitHub/native 1.6.5, crates.io packages, and npm 1.6.5 are published from immutable commit 363bc97f2336c73e90802916804dccd2109c5746; npm latest is 1.6.5 as of 2026-10-12. The learning-event separation merged after that release in PR580 is **Unreleased**, even though source package versions still say 1.6.5.
Published 1.6.5: get a first result
You need **Node.js 18+** and a repository you can read. Install the signed native 1.6.5 artifact, then run this POSIX-shell recipe from your repository:
first-minute discovers a covering served owner first. Otherwise, the matching wrapper/native runtime prepares only the exact launcher-granted repository in an external private cache. Source files remain inputs. Only when reusing the automatic isolated cache does the CLI refresh the declared root before retrieval. Attached-owner freshness follows the owner's own semantics; inspect that owner's version, repository binding, and freshness rather than inferring them from the selected client binary. Check runtime.boot, returned source locations, and gaps. This is not authority to create a shared brain, move a binding, or call generic ingest.
To connect an MCP host, follow the 1.6.5 quick start. Direct stdio needs an explicit workspace grant and an existing external private runtime; a shared owner has separate preparation and authority requirements. See agent autonomy.
Historical pinned 1.6.3: install, prepare, connect
You need **Node.js 18+**, an MCP host, and a repository. First install the signed native 1.6.3 artifact; that guide uses cosign and an exact release URL. The prebuilt 1.6.3 release covers Linux x86_64 and macOS x86_64/ARM64. Run this POSIX-shell recipe from the repository you want to use; it deliberately pins the wrapper:
Replace claude with your host, such as codex or cursor. Follow the printed instructions: some host-managed configuration and hooks are **printed for you to install**, not written automatically. Restart or reconnect the host after configuration changes. See the host integration matrix for host-specific behavior.
Before reconnecting, add M1ND_RUNTIME_DIR to the generated MCP server environment with the **same absolute path** printed by echo "$M1ND_RUNTIME_DIR". Keep the generated M1ND_WORKSPACE_ROOT. hosts apply does not add the runtime selector for you; without it, a host launched elsewhere can open a different graph.