- All Collections
- MCP Server Test (Beta)
- StoriesOnBoard Model Context Protocol (MCP) Server Overview
Written by Tamás Párványik
Updated today
Table of contents
Contents:
What is the StoriesOnBoard MCP server?
The StoriesOnBoard Model Context Protocol (MCP) server is a powerful integration bridge that connects your story maps directly to AI agents and LLMs (like Claude, Cursor, Visual Studio Code or ChatGPT). The MCP allows an AI to not just "chat" about your project, but to interact with it as an active collaborator.
Traditionally, AI could only help you by generating text that you then had to manually copy and paste into your story map. With the MCP server, the AI gains a "hands-on" connection to your workspace.
The MCP server allows agents to perform both comprehensive read and atomic write operations across the entire story map structure, unlocking powerful automation workflows:
Available tools for StoriesOnBoard MCP server
The StoriesOnBoard MCP server offers seven specialized tools, covering discovery, read, and write capabilities:
Discovery and Read Tools
Tool Name | Capability |
ListStoryMaps | Discovers all story maps in the workspace, returning key data like ID, slug, title, and the user's role (Admin/Editor/Viewer). |
GetStoryMapCards | Retrieves the hierarchical card structure of a story map (activities → tasks → subtasks). It now returns a contiguous, zero-based |
GetStoryMapCardDetails | Fetches the full details of a specific card, including the description, comments, attachments, and weblinks. |
GetStoryMapData | Provides story map-level reference data necessary for valid write calls, such as collaborator lists, canonical color labels, subtask statuses, active priority framework (e.g., Basic, Moscow, Kano), 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. It also provides a status report showing subtask statistics and any metadata if the release is linked to an external integration tool (like Jira or Azure DevOps). |
Write and Action Tools
Standardization Feature
The MCP Position Semantics is a key standardization feature. It dictates that all relevant MCP tools use a unified, zero-based position field to describe a card's location. This standardization ensures that agents can reliably read a card's position from GetStoryMapCards and use that value directly in CreateStoryMapCard or MoveStoryMapCard for advanced positional commands.
Benefits of using StoriesOnBoard MCP server
The StoriesOnBoard Model Context Protocol (MCP) server represents a paradigm shift in product management. Instead of the AI being a separate chatbot where you copy-paste text, the MCP server turns the AI into an active collaborator with a "hands-on" connection to your actual story map.
By using an MCP-compatible host (like Claude Desktop, Cursor, or IDEs), your AI agent can see, understand, and edit your product's DNA in real-time.
Here are the primary benefits of this integration:
Elimination of Manual Data Entry (Agentic Mapping)
The most immediate benefit is the transition from static documents to visual maps without the "manual labor."
Intelligent Backlog Grooming & Quality Control
Backlog grooming is often the "chore" of product management. An AI agent can now perform this autonomously.
Strategic "Slice" Planning (MVP Development)
Deciding what goes into an MVP vs. a later release is a complex logic puzzle.
Real-Time Gap Analysis
Because the AI can "see" the entire horizontal journey, it can spot architectural holes that humans might miss in a flat list.
Bridging the "Context Gap" for Developers
When developers use AI-powered IDEs (like Cursor or Windsurf) connected to StoriesOnBoard via MCP, the AI understands the "Why" behind the code.
Learn more about: