Overview

The StoriesOnBoard Model Context Protocol (MCP) provides the mechanism for development-focused AI agents, such as Claude Desktop (which functions as an AI coding agent), to directly integrate with and interact with your story maps.

💡 Tip : StoriesOnBoard Model Context Protocol (MCP) Server Overview

List of available tools

Read tools:

ListStoryMaps: Allows the AI to discover and list all available story maps in your workspace, including titles, descriptions, and URLs.
GetStoryMapPersonaDetails: Allows to gain access to user personas and understand how they interact with the solution you build.
GetStoryMapCards: Enables the AI to pull the entire hierarchical structure from Activities → Tasks → Subtasks along with all associated releases. Your AI now understands exactly where a task fits within the user journey.
GetStoryMapCardDetails: Provides full access to a specific card’s details, including descriptions, comments, attachments, and linked web resources.
GetStoryMapData: Provides story map-level reference data necessary for valid write calls, such as collaborator lists, canonical color labels, subtask statuses, active priority framework, and persona/annotation names.
GetStoryMapReleaseDetails: Access the complete data sheet for a specific release on your story map. You can use it to view the release's goal, dates, and whether it has been officially released.

Write tools:

CreateStoryMapPersona: Creates a new persona scoped to a specific story map. Accepts a name and optional fields including a markdown description, group, custom field values, and personality slider values.
CreateStoryMapCard: Allows the creation of activity, task, or subtask cards in a single MCP call, including all common fields.
UpdateStoryMapPersona: Partially updates an existing storymap-scoped persona. Any combination of name, description, group, custom fields, and personality values can be updated.
UpdateStoryMapCard: Facilitates the updating of any field combination on an existing card in a single MCP call.
MoveStoryMapCard: Enables agents to perform structural changes: reorder activities, relocate a task under a different activity (reparent), and move a subtask between releases (schedule/unschedule) or different tasks. It uses the zero-based position parameter for precise placement.
CreateStoryMapRelease: Allows to create a new release on the story map in a single call, setting its name, goal, start/release dates, and specific position on the board.
UpdateStoryMapRelease: Allows for a partial update of an existing release, enabling you to modify the name, goal, dates, and the status in a single call. If a field's new value is an empty string, the field is cleared; if a field is omitted, it remains unchanged.