Contents:
Overview
Taking advantage of agentic workflows using the MCP, it allows you to efficiently add a new release to your story map in a single action. Instead of manually entering details after creation, you can simultaneously define the release's name, goal, scheduled dates, and precise position on the board. This ensures that every new release is immediately complete and visible to your team with all the necessary details.
How to connect StoriesOnBoard MCP Server with Claude Code
Before you connect make sure that StoriesOnBoard Model Context Protocol (MCP) is enabled on your workspace. During the Beta Program, you may contact to our team via email support@storiesonboard.com or text in the built-in chat for clarification.
💡 Follow this guide:
Ask your agent to create a new release
Before you move forward make sure you let your agent know which story map you want to work with. You can refer story maps by their names as well.
Then return to your story map to access the new release.
Create a new release with scheduling cards in it
You can also create a new release and based on your criteria you can ask your agent to create the new release and schedule backlog items in it.
In this case not only the new release will be created but backlog items will be moved into the release according to your needs.
Prompt examples for creating new releases
To create a standard release with a goal and full dates
Create a new release named 'Q3 Feature Polish' with the goal 'Refine the new user onboarding flow by fixing all reported usability bugs.' Set the start date to 2026-07-01 and the release date to 2026-09-30.
To create a release with a name and goal
Add a new release called 'Beta Launch Prep' and set its goal to 'Finalize all documentation and marketing assets for the upcoming beta program.
To create a time-bound release without a goal
Create a release scheduled to start on 2026-05-15 and finish on 2026-06-15, and name it 'May-June Mini Release.
Learn more about: