Flows

Flows are how Mnema turns a workspace of docs into structured context for an AI agent. Here's what they are, how Claude calls them, and when to reach for one.

1. 1

   What a flow is

   A flow is a named sequence of content steps. Each step has an instruction and references one or more docs in your workspace. Flows are the unit of context that you deliver to Claude — not raw docs, not entire workspaces, but specific ordered sequences with your authorial intent baked in.

2. 2

   How Claude calls a flow

   Claude (or any MCP client) discovers your flows by calling list_flows. It then walks the flow by calling get_flow_step(flow_id, step_number) for each step in order. Each call returns one step's instruction plus the rendered content. The sequence is explicit — Claude doesn't decide order, you do.

3. 3

   When to use a flow vs. a single doc

   Single docs are good when Claude needs a fact or a specific piece of content. Flows are good when Claude needs to be walked through something — a codebase onboarding, a workflow, a structured analysis. If you'd brief a teammate over five minutes with "first read this, then this, then this" — that's a flow.

4. 4

   The flow editor (coming next release)

   The visual flow editor is in active development. Drag docs into a sequence, annotate each step with an instruction, save the flow. It's exposed to Claude automatically through MCP — no extra wiring needed.