mcp-usagelisted

# MCP Usage Procedures that used to live inline in every project's `CLAUDE.local.md`. They are needed occasionally, not on every turn, so they load on demand. `CLAUDE.local.md` keeps only what binds every turn: which servers are registered, the git/GitHub MCP-only requirement, Open Brain, trust/verification, and failure handling. ## Ollama availability & warm-up Before `local_first_pass` or `extract_json`: 1. `ollama_health` — is the server up? 2. `ollama_list_models` — are the required models present? 3. `warm_models` (optional) — pre-load for faster first inference. If Ollama is unavailable: say so, proceed without local preprocessing when the task is small, and do **not** retry indefinitely or fail silently. ## Large inputs / context digestion For any input over ~200 lines, or complex regardless of length (requirements, logs, architecture, policy): 1. `local_first_pass` to compress or plan. 2. **Verify important details against the original** — the summary is assistive, not authoritative. 3. Only then implement or answer. ## Structured information extraction When the task needs structured data — errors, TODOs, requirements, entities, acceptance criteria, cause/effect: 1. `extract_json` with an explicit schema. 2. Treat the returned JSON as the authoritative structure. 3. Act on it (prioritize, implement, fix). Do not hand-infer structure when extraction is available. If `extract_json` returns invalid JSON, retry through the tool — never continue on a guessed s