Solumbe

What Solumbe MCP server does

Solumbe MCP server adds repository-analysis tools to an AI development workflow. Its local core reads the repository and Git state to build task-aware context, rank the files a request is likely to affect, compare intended work with the resulting change, and assess whether the staged tree is ready for review. The analysis is deterministic and model-agnostic: the core does not call a model, open a socket, or read outside the repository.

The project is intended to run beside an agent harness rather than replace one. An agent can use the resulting context before editing, then use convergence and review checks after editing. The local gate reports PASS, WARN, or FAIL and explains the evidence behind that result.

How it works

A typical workflow has four stages:

• context identifies files, tests, and commands relevant to a request.
• converge compares the request with the files changed by a diff and creates a receipt.
• gate evaluates the exact staged tree, including changed-file scope, secret safety, risk review, and convergence.
• attest records what shipped, the verdict, and the merge commit in a hash-chained record.

Impact analysis can rank likely blast radius from the request alone. Scope contracts provide another control: declare records expected files before editing, while later amendments attach a reason when the scope expands. The gate can then identify undeclared files, including risk-sensitive paths.

Evidence is tied to repository state. Examples in the documentation include a staged-tree identity, a base commit, and a receipt handle, so reviewers can see which tree was assessed. A local passing gate is not described as an automatic merge approval; hosted CI, GitHub review, CODEOWNERS, and the human release decision remain separate authorities.

Setup and configuration

Install the package globally with npm, then run the diagnostic command and connect the server to detected agent hosts:

npm install -g @bashbop/solumbe
solumbe doctor
solumbe install --host all

Use --dry-run to inspect the installation plan first, or provide a comma-separated host list such as --host claude-code,cursor. Restart each host after installation. The documentation also supports running the diagnostic without a global install through npx -y @bashbop/solumbe.

The MCP process can be started directly with solumbe mcp. Every command accepts --json, and solumbe help or solumbe help --all lists available commands and flags. The documented runtime requirement is Node.js 18.18 or newer.

Tools and capabilities

The Solumbe MCP server ships a stdio MCP server with 14 tools. The provided material names change_impact and review_gate; change_impact supports declaration through declare: true, while review_gate accepts an intent. The command-line surface also includes repository inspection, mapping, indexing and search, workspace gates, calibration, route recommendations, harness generation, and dashboard-related commands.

Useful command examples include impact for ranking affected files, declare for recording expected scope, converge for intent-versus-diff scoring, gate for staged-tree checks, and attest for post-merge records. Context can be sharpened with an optional online model read, but the local core itself does not require hosted services.

Limitations and notes

The local gate is evidence for review, not a complete merge authority. It does not replace hosted CI, GitHub review, CODEOWNERS, or a human release decision. Optional hosted features exist, but the supplied documentation states that the local core requires no hosted service and that hosted components cannot change a local verdict.

Solumbe MCP server is local-first: its core does not send code over the network. The project was formerly named Òtítọ́ and the npm package was formerly @bashbop/otito; version 4.0.0 introduced the current name. The stated license is MIT.