MCP server for Taskweft.

Start with mix taskweft.mcp (stdio) or mix taskweft.mcp --http.

The planner model is RECTGTN — Relationship-Enabled Capability-Temporal Goal-Task-Network. A domain's tasks hold three task kinds: TwCall call arrays ('E'/'T'), TwGoal goal bindings ('G', the top-level goals key), and TwMultiGoal {"multigoal": …} entries ('N'). Two more layers apply on top of any task kind: capability guards ('R'/'C', top-level capabilities) and per-action temporal duration ('T', an action's duration field). The plan tool's domain_json description documents all five with golden shapes (and rejected shapes for goals/multigoal — capabilities/duration are plan-time, not load-time, so nothing there is structurally validated).

Tools

check_temporal is not exposed as its own tool; every plan response already includes a "temporal" block computed from action duration fields. ReBAC, bridge, and cache NIF entrypoints are not exposed.

Prompts

plan_problem (solve a problem/domain pair), plan_goal (build a TwGoal or TwMultiGoal problem), plan_capability_temporal (build a domain using capability guards and/or action durations), replan_after_failure, and work_queue.

Resources

Every .jsonld under priv/plans/{domains,problems} is exposed as taskweft://domains/<file> and taskweft://problems/<file>; new files require mix compile to register.