GraphMind turns a codebase into a knowledge graph that Claude Code can query and navigate, and gives it persistent memory across registered projects. It runs as a skill and an MCP server.
Claude Code
$ npx -y skills add aouicher/graphmind --agent claude-code
Codex
$ npx skills add aouicher/graphmind -a codex
Cursor
$ npx skills add aouicher/graphmind -a cursor
Gemini CLI
$ npx skills add aouicher/graphmind -a gemini-cli
GitHub Copilot
$ npx skills add aouicher/graphmind -a github-copilot
OpenCode
$ npx skills add aouicher/graphmind -a opencode
Windsurf
$ npx skills add aouicher/graphmind -a windsurf
Your codebase has a shape. Now your AI can see it. And remember it.
GraphMind turns your codebase into a knowledge graph your AI can query, navigate, and remember. Ask about dead code, dependencies, or blast radius — and get answers grounded in your actual architecture.
Up to 5,700× fewer tokens than raw search (~10M tokens saved per session). Works with Claude Code, Cursor, Windsurf, Cline, Zed, Continue, and any MCP-compatible AI assistant.
Every new AI session starts from zero. Your assistant re-reads the entire codebase, re-discovers architecture, and forgets every decision you explained last time. Across multiple projects, there's zero visibility into shared dependencies.
graphmind fixes this with four layers:
Everything runs locally. No cloud. No open ports by default. No telemetry.
Comparison of token usage: grep -r (raw file search) vs graphmind search for the same query on a ~100k LOC codebase. graphmind returns ranked, structured results in under 300 tokens vs 1.5M+ for raw grep output.
Download the .dmg from Releases. The app installs the CLI for you and runs a guided onboarding that configures MCP, hooks, skill, and embeddings — no terminal needed.
| Platform | Asset |
|---|---|
| macOS (Apple Silicon) | GraphMind-macos-arm64.dmg |
| macOS (Intel) | GraphMind-macos-x64.dmg |
Linux / Windows: CLI only — use the shell script or direct download below.
curl -fsSL https://raw.githubusercontent.com/aouicher/graphmind/main/scripts/install.sh | bash
Then run graphmind setup once to configure Claude Code, hooks, and skill.
brew install aouicher/graphmind/graphmind # CLI
brew install --cask aouicher/graphmind/graphmind # Desktop app (macOS only)
curl -fsSL https://github.com/aouicher/graphmind/releases/latest/download/graphmind-cli-linux-x64 -o ~/.local/bin/graphmind
chmod +x ~/.local/bin/graphmind
git clone https://github.com/aouicher/graphmind
cd graphmind
cargo build --release -p graphmind-cli
cp target/release/graphmind ~/.local/bin/
graphmind setup # once — configures Claude Code, Claude Desktop, hooks, skill
cd ~/projects/myapp
graphmind init # per project — registers, installs git hooks, builds graph
That's it. Claude Code, Claude Desktop, Cursor, and VS Code will use graphmind automatically.
graphmind setup (once, global)Configures your machine so all AI tools can use graphmind:
~/.zshenv for zsh, ~/.bashrc for bash, ~/.profile otherwise), after a backup of that profile. On Windows, ~/.graphmind/bin goes on the user PATH and into your PowerShell profile instead. A profile that can't be read as text is left unchanged, and setup prints the folder to add to PATH yourself~/.claude/settings.json; a settings.json that can't be read or parsed is left unchanged/gm + 19 sub-skills)claude_desktop_config.json; the location per OS is under Manual setup)projects.<path>.mcpServers.graphmind in ~/.claude.json, or $CLAUDE_CONFIG_DIR/.claude.json when that is set, under the path Claude Code reads for the repository, usually its main checkout; see MCP server for Claude Code): rewrites an entry that points at a moved binary or carries an env block, moves an entry earlier versions wrote under a worktree's or a subfolder's own path (which Claude Code never reads) to the repository's, and replaces a user-scope graphmind entry that runs graphmind with entries for the registered projects, in one write. Entries are added when a project is registered (graphmind init, graphmind register, the desktop app); a .claude.json that doesn't parse is left as is, and setup runs again later~/.config/opencode/opencode.jsonc)~/.cursor/mcp.json) — available in all Cursor projects.vscode/mcp.json of registered projects that already have one~/.claude/CLAUDE.md); a block you edited is left as you set itsetup re-runs automatically after the binary is updated, when its configuration changed.
graphmind init (per project)Registers and indexes a project:
projects.<path>.mcpServers.graphmind in ~/.claude.json, through claude mcp add -s local when the claude CLI is on PATH), and VS Code's (<project>/.vscode/mcp.json), only in projects that already have a .vscode/ foldercd ~/projects/api && graphmind init
cd ~/projects/web && graphmind init
cd ~/projects/lib && graphmind init
Both commands are idempotent — safe to re-run.
/gm outside a projectClaude Code's MCP entries are per repository (see MCP server for Claude Code), so a session opened outside every registered project has no graphmind MCP tools. /gm runs the graphmind CLI and works there too: in a session opened outside any indexed project (graphmind which prints nothing and exits 1), it still answers questions about a registered project. It runs graphmind list, picks the project the question is about (asking you only when several could match), and passes it to every command with --slug <project>, for example graphmind fn dispatch_tool --slug myapp. Every query command takes --slug, except list and cross query, which span all projects. A slug that isn't registered is an error. Questions about an unregistered folder go to the agent's normal tools.
Click to expand
Claude Code gets graphmind per project, with one entry per repository, under the path Claude Code reads for it when started anywhere in the repository:
a repository's main checkout, for the checkout, its linked worktrees and their subfolders;
the bare repository (repo.git), for the worktrees of a bare repository;
the submodule's root, for a submodule and its subfolders, and <superproject>/.git/modules/<name> for a worktree of a submodule;
the work tree's root, for a repository created with --separate-git-dir;
the folder itself, outside git.
Registering a project (graphmind init, graphmind register, or adding it in the desktop app) writes or confirms that entry. From a worktree or a subfolder, it says which path it used.
Unregistering a project removes the entry, unless another registered project uses it. For a project whose folder was deleted, the entry is the graphmind entry under its path or a parent that no registered project uses; when more than one could be, all are left and graphmind says so.
A graphmind entry you set up by hand (its command isn't a graphmind binary) is left alone.
A .claude.json that doesn't parse is left as is and the reason shown; the project is registered anyway.
By hand, in that path (the main checkout, for most repositories):
claude mcp remove -s local graphmind # only to replace an existing entry: `claude mcp add` refuses a name that exists
claude mcp add -s local graphmind -- "$(command -v graphmind)" mcp
which writes this to ~/.claude.json ($CLAUDE_CONFIG_DIR/.claude.json when that is set), under that path:
{
"projects": {
"/home/user/projects/myapp": {
"mcpServers": {
"graphmind": {
"type": "stdio",
"command": "/home/user/.local/bin/graphmind",
"args": ["mcp"],
"env": {}
}
}
}
}
}
The command is the absolute path of your binary. command -v graphmind finds it on PATH (~/.local/bin/graphmind for the install script, $(brew --prefix)/bin/graphmind for Homebrew). graphmind setup uses ~/.graphmind/bin/graphmind instead whenever that file exists (older installs), even when another graphmind is first on PATH: pass that path to match it. The empty env is fine, but an env.PATH there replaces the environment the server inherits, so don't add one.
Claude Desktop does not inherit your shell PATH, so use the full path:
{
"mcpServers": {
"graphmind": {
"command": "/home/user/.local/bin/graphmind",
"args": ["mcp"]
}
}
}
Config file location:
~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.json~/.config/claude/claude_desktop_config.jsonTip: Run
command -v graphmindto find the correct path on your system.
graphmind setup writes this automatically to ~/.cursor/mcp.json:
{
"mcpServers": {
"graphmind": {
"command": "/home/user/.local/bin/graphmind",
"args": ["mcp"]
}
}
}
graphmind init writes this automatically to <project>/.vscode/mcp.json, in projects that already have a .vscode/ folder:
{
"servers": {
"graphmind": {
"type": "stdio",
"command": "/home/user/.local/bin/graphmind",
"args": ["mcp"]
}
}
}
graphmind install hook-claude
Registers hooks in ~/.claude/settings.json for:
Stars on GitHub
A development methodology for coding agents that makes the agent brainstorm before building, follow plans, run parallel work and finish branches in a disciplined way. You get fewer skipped steps and more consistent results from your coding assistant.
@obraHelps you take a change from a rough idea or bug report through to a tested, reviewed result, with each step handled by a focused skill. Its skills cover pinning down domain terms, designing module interfaces, diagnosing hard bugs, and reviewing changes against your repo's coding standards.
@mattpocockGives your coding agent a planning, testing and review routine to follow on every task. It plans before building, checks changes with tests, has a fresh reviewer look for regressions, and saves repeated wins as reusable skills.
@affaan-mDeveloper tools for working on the React codebase itself. Provides skills for extracting error messages, managing and debugging feature flags across release channels, running Flow type checks, and fixing lint and formatting issues before committing.
@facebookInstall it with the command on its page. It includes graphmind. Its skills do not fire on their own yet. Free and open source.
Is this plugin yours?
Claim it with GitHubSubmit a pluginPromote it