Laminar MCP

Overview

Laminar is the product behind this MCP. Server tools/list (or equivalent) wins on names and args over this file. No assumption of a local Laminar checkout. Prefer signals from load_source_context; stop loading when the next step is clear.

For the developer (human)

• Attach @laminar-mcp when starting demand work so the agent reads this playbook.
• Give demand id (TAL-* or Convex id) and client/product if scope must not be guessed; say if you want anchored handoff at session end.
• If MCP fails: confirm Laminar MCP enabled + auth; retry or paste tools/list for the agent.

Agent: session scope

get_current_context → if needed list_clients / list_products → set_context (clientId, then productId). Lists need client; story map and releases need product. clear_context only to drop product on purpose.

Agent: demand context (order)

Demand record → anchored ADR → evidence → map → peers.