Use after Code Mining has completed one or more modules to turn versioned code facts and its durable analysis artifacts into evidence-linked business scope, domain, concept, context, and candidate bizmapping records. Do not use it to discover physical nodes or edges, alter module boundaries, approve candidates, or…
An operations control tool for a code-context knowledge base. It handles registered tools for one repository and one Git commit, while identifying management requests and filling in required details.
Use when a local repository needs an initial full code-analysis inventory for a branch or commit, or needs to discover AI-executable Node Definition Rules before Code Mining. It fixes the Git revision, discovers modules and source files with scripts, creates two-level manifests, and can produce confirmed Node…
Use when an existing Bootstrap run has a valid module Manifest and AI-executable Node Definition Rules, and one-file-at-a-time AI analysis must produce code facts, relationships, and candidate node semantics with auditable decision coverage. Do not use it to discover node rules, approve semantics, or write semantic…
Use after Bootstrap produces a valid immutable handoff to orchestrate Code Mining before Business Mining across selected modules. Do not use it to extract code facts, infer business mappings, or change upstream artifacts.
MCP server "code-context-storage-mcp" as configured in Jrains-ux/code-context-storage-mcp. Runs locally from the code-context-storage-mcp Python package.