haft_entity

MCP tool from Haft by m0n0x41d

Proactively establish one minimum non-binding EntityOfConcern when current Work supplies a concrete operator-named or agent-inferred durable receiving use; known absence alone is insufficient

How to use it

haft_entity is exposed by the Haft MCP server. Add the server to your MCP client (Claude Desktop, Cursor, Windsurf and others), and the haft_entity tool becomes available to the model automatically. See the full listing for setup details and every tool this server provides.

FULL HAFT LISTING

Other tools in Haft (11)

haft_commission

Runner-neutral WorkCommission authority and lifecycle records

haft_decision

Decision contracts: invariants, claims, evidence, baseline lifecycle

haft_memory

Expert raw MemoryChangeSet validation/admission through a nested request envelope; ordinary agents use haftentity, and validation never admits automatically

haft_method

Task-local SWE MethodRun cards: pull gates before non-trivial work, close with evidence or waivers

haft_note

Non-binding facts, observations, caveats, and rationale with typed anchors, validation, and optional freshness

haft_onboard

Read setup status, prepare a non-binding initial profile review, or prepare an explicitly requested predecessor-pinned scope relation change; a missing relation never gates TargetSystemSpec lifecycle; haft init automatically admits only a complete supported singleton as origin=detectordefault and in

haft_problem

Frame problems, declare comparison dimensions with indicator roles

haft_query

Project search/status, code graph, source-native FPF query/lookup/inspect, and typed-memory resolve/neighborhood/recall

haft_refresh

Lifecycle management for every artifact kind

haft_solution

Explore variants with diversity check, compare under parity

haft_spec_section

Typed SpecSection lifecycle projection over project SQL editions; FPF source compatibility is assessed separately; manual CLI gates approve, rebaseline, or reopen baselines