#!/bin/bash . _env.sh export SESSION_ID=3e636737-4db0-472a-8337-50941fb07f35 export session_id__StoryBeatMCPMaker_2512010103 export session_id__StoryBeatMCPMaker_2512010103__MCP_CONFIG export session_id__StoryBeatMCPMaker_2512010103__ADD_DIR claude "file @prototypes/artefacts/storybeats-reference.md contains references about what I would want us to have an MCP that agents can use when it is time to turn a session into story beats. I guess to design this narrative-mcp-convertion (or something like it) you would have to think carefully about the protocol and schema, probably the reference you have comes from what is in /src/holisticagnostic-narrative-context-protocol/ - At the end, I will want to have, for example, a folder where all the story points (we will want not just to work on story beats with that new tool) to become part of a series, a show where the story of what happens in a session (example of sessions can be found in : /src/_sessiondata) into parts of the series arc and episode arc (like the technological and contextual settings , goals, values,...) are transformed into all elements of the NCP by this MCP." --mcp-config $session_id__StoryBeatMCPMaker_2512010103__MCP_CONFIG --add-dir $session_id__StoryBeatMCPMaker_2512010103__ADD_DIR --session-id $session_id__StoryBeatMCPMaker_2512010103 --permission-mode plan