cbm-tool: a cross-platform CLI helper for indexing and editor setup

[fxjs]

Hi — sharing a small community helper I built around codebase-memory-mcp.

What it is

cbm-tool (cbm) is a lightweight cross-platform wrapper (Bash + PowerShell) that makes day-to-day use of codebase-memory-mcp a bit smoother:

1. Friendlier indexing CLI around index_repository — modes, persistence, cross-repo targets, list projects, open the local graph UI
2. cbm setup — auto-detect and configure local AI editors (Claude Code, Cursor, Codex CLI, Cline, Windsurf) with rules that prefer the knowledge graph when exploring code
3. cbm update — update cbm itself or call through to codebase-memory-mcp's own updater

It does not replace the official installer or MCP server. You still need codebase-memory-mcp installed; cbm just wraps common workflows.

Quick examples

# Index current repo (default mode: full)
cbm .

# Fast index + persist artifact
cbm -m fast -p /path/to/repo

# Configure detected editors to prefer the graph
cbm setup

# Open local MCP UI
cbm -o

Windows:

.\bin\cbm.ps1 .
.\bin\cbm.ps1 setup -Editor cursor

Links

• Repo: https://github.com/fxjs/cbm-tool
• Release v1.0.0 (includes cbm / cbm.ps1 assets): https://github.com/fxjs/cbm-tool/releases/tag/v1.0.0
• Docs: https://github.com/fxjs/cbm-tool/blob/main/docs/USAGE.md

MIT licensed. Feedback welcome — happy to adjust naming/docs if anything conflicts with upstream conventions.

[DeusData]

Thanks for sharing this and for clearly presenting it as a community wrapper rather than an official installer. The local workflow focus is useful, and we appreciate the effort across Bash and PowerShell.

Because cbm-tool writes editor configuration and carries its own installation and self-update path, it remains an independent, unofficial project outside the upstream codebase-memory-mcp security and support boundary. Please keep “unofficial community tool” prominent in its README and releases, document preview and backup behavior before configuration changes, publish checksums for release assets, and keep its updater clearly separated from the official codebase-memory-mcp updater. That will help users understand which project owns each operation.

Thanks as well for offering to align the naming and documentation with upstream conventions.