Storybloq local project

Use the current task's working directory. Each task has its own board MCP process; do not select a project from an earlier chat, a demo path or an inherited project-root variable. Storybloq's .story/ files remain canonical. No API key, tunnel, cloud account or Mac app is required.

Open Storybloq

Call this plugin's storybloq_board tool. Discover the exact tool by name if necessary, checking that it belongs to the Storybloq plugin. Its local server discovers the nearest ledger within the current Git worktree, or only the task directory when there is no Git repository. It refuses incomplete or unreadable ledgers.

If the result says ready: true, call storybloq_board again: the previous call activated tools after setup. Use its project summary to explain current progress and blockers. The returned UI resource contains the board, phases, ticket and issue editors, notes, timeline, sessions and federation views. Use the host's supported app display action when available. A resource retrieval alone does not prove the host rendered it. Never say the board opened unless there is evidence it is visible. Do not promise automatic opening from hook support.

If native app rendering is unavailable and the board response supplies structuredContent.localBrowser.url, provide its Open Storybloq link. Use the host’s supported browser action to open that exact link when requested. It is a local page owned by this task’s running plugin process, with no tunnel. It expires when the task connection stops; reopen from the current task after restart. Keep the capability link in this task and never forward it to another project or external service. A link returned by the tool does not itself prove a visible board.