开源MCP工具

(re-)indexed on a full `basemind scan` only (not live-watched). Requires the operator to set

Installation

Three ways to run basemind, easiest first. All three share the same local index and are safe to run side by side.

The plugin downloads the basemind program for you on first use. The MCP-server and CLI paths need it installed yourself — see Install the program.

Install the program

The MCP and CLI paths need basemind available on your system. (The plugin does this for you.)

The Homebrew / npm / pip / GitHub downloads include the full feature set — documents, OCR, search, web crawl, shared memory, agent comms, and agent shells — so the first run downloads the models it needs. The plain cargo install builds the code-map and git tools only.

`exclude` is ADDED ON TOP of an always-on floor (node_modules, target, dist, build, out, .venv,

Demos

<p align="center"><img src="docs/media/demo.gif" alt="basemind CLI: scan, then symbol / reference / call-graph / blame queries" width="760"></p> <p align="center"><em>The same engine from the CLI — <code>scan</code>, then symbol / reference / call-graph / blame queries.</em></p>

<p align="center"><img src="docs/media/semantic-demo.gif" alt="Semantic search over the documents store" width="820"></p> <p align="center"><em>Searching documents by meaning, not keywords, across 90+ formats.</em></p>

<p align="center"><img src="docs/demos/code-review-panel.gif" alt="Three named reviewer agents posting findings to a shared repo-scoped thread, replying to each other, and an orchestrator synthesizing a verdict over the comms CLI" width="820"></p> <p align="center"><em>Multi-agent code-review panel: named reviewers coordinate in a repo-scoped thread (post, reply, synthesize) — entirely over <code>basemind agents</code>.</em></p>

---

Configuration

<details> <summary><strong>Config file &amp; overrides</strong></summary>

The config lives at the repo root as basemind.toml (committed). The cache it drives is derived state — held in the global cache under the XDG data directory, wiped and rebuilt on schema bumps — so config never belongs there and nothing basemind-owned is written into your repo. Run basemind init to drop a fully-commented scaffold (documenting every option) at the root. The legacy in-cache path (.basemind/basemind.toml, from before the global-cache move) is still read as a fallback for older checkouts. The full schema is at schema/basemind-config-v1.schema.json:

```toml

venv, __pycache__, *.pyc, .pytest_cache/.mypy_cache/.ruff_cache/.tox, .next/.nuxt/.svelte-kit,

BASEMIND_ALLOW_EXTRA_ROOTS=1 in the environment: this file lives inside the repository, so

symbols resolve in search / references / outlines. External files are keyed by absolute path;

CLI reference

<details> <summary><strong>Full command list</strong> — code · graph · git · memory · admin · cache · web · agents · workspace · shell</summary>

CLI commands mirror the MCP tools 1:1 (enforced by tests/cli_parity.rs). Add --json for machine-readable output.

Code (basemind code)

Graph (basemind graph)

Git (basemind git)

Memory (basemind memory)

Admin (basemind admin)

Cache (basemind cache)

Web (basemind web)

Agents (basemind agents, --features comms)

Every command takes --as-agent <ID> to act as a named sub-identity.

Comms daemon (basemind comms, --features comms)

Shell (basemind shell, --features shells)

Other commands (scan, serve, watch, …)

</details>

---

1. As a plugin (recommended)

The plugin sets up everything for you — the server, the helper skills, the agent-comms features, and the slash commands. Pick your coding tool.

<details> <summary><strong>Claude Code</strong></summary>

In the session (not your shell), run in order:

/plugin marketplace add Goldziher/basemind
/plugin install basemind@basemind

Restart, then run /bm-statusline once to turn on the live statusline (a one-time step — see Statusline). Turn on auto-update for the basemind marketplace (Claude Code's plugin manager): the plugin then tracks each new release automatically, and the launcher resolves the latest published release, so you always get the current index format and tool set and startup stays reliable even during a release. Prefer to control timing? Update the marketplace regularly by hand instead.

</details>

<details> <summary><strong>Codex</strong></summary>

codex plugin marketplace add Goldziher/basemind
codex plugin add basemind@basemind

In the app: open the Plugins sidebar and add basemind. The CLI and IDE share one config file. The plugin starts the latest published GitHub release from the project workspace; it never runs from the installed plugin cache or races a shared npx install.

</details>

<details> <summary><strong>Cursor</strong></summary>

In Agent chat: /add-plugin basemind (once listed), or go to Dashboard → Settings → Plugins → Team Marketplaces → Import from Repo and point it at https://github.com/Goldziher/basemind.

</details>

<details> <summary><strong>Gemini CLI</strong></summary>

gemini extensions install https://github.com/Goldziher/basemind

Update later with gemini extensions update basemind.

</details>

<details> <summary><strong>Factory Droid</strong></summary>

droid plugin marketplace add https://github.com/Goldziher/basemind
droid plugin install basemind@basemind

</details>

<details> <summary><strong>GitHub Copilot CLI</strong></summary>

copilot plugin marketplace add Goldziher/basemind
copilot plugin install basemind@basemind

</details>

<details> <summary><strong>OpenCode</strong></summary>

Add to opencode.json (project) or ~/.config/opencode/opencode.json (global):

{ "plugin": ["basemind-opencode@latest"] }

</details>

<details> <summary><strong>Kimi Code</strong></summary>

/plugins install https://github.com/Goldziher/basemind

Kimi doesn't support the comms auto-notifications, but the chat tools still work.

</details>

<details> <summary><strong>Hermes</strong></summary>

Hermes exposes MCP servers through config, so basemind's tools are wired there. Two steps — the binary + MCP wiring gives you the tools; a small standalone plugin package adds the helper skills, slash commands, and comms notifications.

First install the program (Homebrew / npm / cargo / release — not pip), then add the server to ~/.hermes/config.yaml (this is what gives you the nine domain tools):

mcp_servers:
  basemind:
    command: basemind
    args: [serve]

For the helper skills, slash commands, and agent-comms notifications, install the standalone plugin into the same Python environment Hermes runs in, then enable it (general plugins are opt-in):

pip install basemind-hermes-plugin
hermes plugins enable basemind

The plugin is pure-Python and ships no binary — it shells out to the basemind you installed above. Comms auto-notifications are best-effort; the chat tools work regardless.

</details>

<details> <summary><strong>Antigravity &amp; pi</strong></summary>

Antigravity uses a shared MCP config — install the program, then add the generic MCP block. If you already use the Gemini extension, agy plugin import gemini brings it across.

pi: pi install git:github.com/Goldziher/basemind. pi has no MCP support, so basemind runs through its CLI here.

</details>