Product design with Claude: phases, requirements, user stories, RICE, flows, dashboard, Jira.
MCPpedia last refreshed this data
io.github.macorifice/yeti is an MCP server that product design with Claude: phases, requirements, user stories, RICE, flows, dashboard, Jira. Its tool list has not been published yet over stdio and sse, requires no API key, and scores 83/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients - only the file and path differ.
{
"mcpServers": {
"yeti": {
"env": {
"PRODUCT_DESIGN_DB": "/Users/you/yeti/yeti.sqlite"
},
"args": [
"-y",
"yeti-mcp"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Product design with Claude: phases, requirements, user stories, RICE, flows, dashboard, Jira.
This server supports HTTP transport. Be the first to test it - help the community know if it works.
Five weighted categories - click any category to see the underlying evidence.
No known CVEs.
Checked yeti-mcp against OSV.dev.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience - it helps other developers decide.
Sign in to write a review.
Others in developer-tools / ai-ml
XcodeBuildMCP provides tools for Xcode project management, simulator management, and app utilities.
MCP server for using the GitLab API
2,700+ scientific tools for AI scientists: life science, research, literature, and more.
MCP server for mobile app automation: verify, control, and debug iOS, Android, TV, and desktop apps
MCP Security Weekly
Get CVE alerts and security updates for io.github.macorifice/yeti and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
An MCP server for product design with Claude. It takes a project from the problem to a verified scope: requirements, user stories, RICE priorities and flow diagrams. Then it sends the work to Jira.

Add Yeti to Claude Desktop, in claude_desktop_config.json, then restart Claude Desktop:
{
"mcpServers": {
"yeti": {
"command": "npx",
"args": ["-y", "yeti-mcp"],
"env": { "PRODUCT_DESIGN_DB": "/Users/you/yeti/yeti.sqlite" }
}
}
}
Set PRODUCT_DESIGN_DB to a file in a folder you keep. With npx the package lives in a cache that can be cleared, and a database stored there would go with it. Yeti needs Node.js 22.13 or later.
Then ask Claude:
Create a project "Quotes for craftsmen" with Yeti. Problem: writing quotes takes hours. Users: plumbers and painters. Goal: a quote in five minutes.
Open the Yeti dashboard.
A project goes through five phases, in order:
must requirement completed and covered by a user story, then the project closesProjects have a mode, chosen at creation:
strict (default): a phase advances only when its requirements are met. advance_phase tells you what is missing.free: phases advance regardless, and the response lists what was skipped.Projects
| Tool | What it does |
|---|---|
create_project | Start a project in the discovery phase, in strict or free mode |
list_projects | List projects with id, name, phase and mode; archived ones are hidden unless includeArchived is set |
get_project | Show phase, what is missing, and linked items |
project_summary | Progress overview: requirements by priority and status, musts covered by stories, criteria done, RICE leader, Jira links, and what is missing to close |
update_project | Change a project's name, problem, users or goal |
advance_phase | Move to the next phase, or list what is missing |
set_project_mode | Switch a project between strict and free |
duplicate_project | Copy a project's requirements and stories into a new project, as open items (a template) |
archive_project | Hide a project from list_projects without deleting it |
delete_project | Permanently delete a project and its items. Requires confirm: true; Jira issues are not touched |
Requirements and user stories
| Tool | What it does |
|---|---|
add_requirement | Add a requirement with a MoSCoW priority |
list_requirements | List requirements, filtered by priority, status or project |
update_requirement | Change a requirement's title, description or priority |
set_requirement_status | Mark a requirement open or done |
delete_requirement | Delete a requirement and unlink it from stories |
add_user_story | Create a user story with acceptance criteria, optionally linked to requirements (requirementIds) |
list_stories | List user stories with their ids, links, criteria state and Jira key |
update_user_story | Change a story's persona, goal, benefit, linked requirements or criteria. Changing criteria resets their done state |
set_criterion_status | Mark one acceptance criterion of a user story as done or not done |
delete_user_story | Delete a user story |
| `searc |