Use the existing @getmarrow/mcp tools directly. Do not invent wrappers, aliases, or local substitutes.
Treat Marrow logging as mandatory. The point is simple: every logged action improves future decisions, and every skipped action throws away usable failure prevention.
marrow_orient({ autoWarn: true }) before any other tool. If shouldPause=true, stop and review the warnings before acting.marrow_auto({ action: "what you are about to do" }). Meaningful actions include file writes, edits, deploys, config changes, API calls, security changes, installs, deletes, and external sends.marrow_auto({ action: "what you did", outcome: "result", success: true|false }). If the action already happened, one combined marrow_auto call is fine.marrow_think before acting and marrow_commit after acting so you get pattern intelligence, loop detection, and explicit outcomes.marrow_run is acceptable when you want orient, think, and commit handled in one call.marrow_ask("plain English question") for prior failures, working patterns, or recommended next steps.marrow_orient, marrow_auto, marrow_think, marrow_commit, marrow_run, marrow_ask, or any marrow_* tool is infrastructure — not a loggable action.references/marrow-api.md when you need the tool quick reference.共 1 个版本