Skip to content
Agentmart
Submit a tool

Yeti

Product design with Claude: phases, requirements, user stories, RICE, flows, dashboard, Jira.

Connector by macorifice · GitHub account verified by the MCP Registry

IndexedMITLocal (stdio)
Write a review

Install

Works with Claude Code, Codex, VS Code, Cursor, Windsurf, Claude Desktop. Read the repository before you give any tool access to your data.

npx agentmarket install connector/macorifice-yeti

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Product design with Claude: phases, requirements, user stories, RICE, flows, dashboard, Jira.

Reviews

Write a review

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this server can do and what it asks for, from its tool list and install config. Checked Oct 25, 2026.

Tools
8 read · 17 write · 4 delete · 2 not yet classified
Secrets
1 (API keys, tokens or passwords)
Install scripts
Not scanned yet
Runs as
Node.js package

Tools by what they do 31

Read from the source code; the running server may list different tools.

Read 8 · Look things up without changing anything.

  • get_project
  • list_flows
  • list_projects
  • list_requirements
  • list_stories
  • prioritize_rice
  • project_summary
  • search_items

Write 17 · Create, change, send or run things.

  • add_requirement
  • add_user_story
  • advance_phase
  • archive_project
  • create_project
  • duplicate_project
  • export_dashboard
  • import_requirements
  • open_dashboard
  • push_to_jira
  • set_criterion_status
  • set_project_mode
Show 5 more tools
  • set_requirement_status
  • sync_from_jira
  • update_project
  • update_requirement
  • update_user_story

Delete 4 · Delete, drop, revoke or wipe things.

  • delete_flow
  • delete_project
  • delete_requirement
  • delete_user_story

Not yet classified 2 · We could not tell from the name and description.

  • export_backlog
  • map_user_flow

Secrets and settings it asks for

Secrets: values you paste in that let it act as you.

  • JIRA_API_TOKEN

Other settings (environment variables or headers).

  • JIRA_EMAIL
  • JIRA_SITE
  • PRODUCT_DESIGN_DB

Tools (31)

Read from the source code; the running server may differ. Descriptions are the server’s own words; hidden characters are shown as [U+…].

  • add_requirement

    Record a product requirement with a MoSCoW priority (must, should, could, wont).

  • add_user_story

    Create a user story in the format 'As a <persona> I want <goal> so that <benefit>', with acceptance criteria.

  • advance_phase

    Move to the next phase. In 'strict' mode, it lists what is missing and does not advance. In 'free' mode, it advances and reports what was skipped. After 'verification' it closes the project.

  • archive_project

    Archive or unarchive a project. Archived projects are hidden from list_projects by default. Nothing is deleted.

  • create_project

    Create a design project. It starts in the 'discovery' phase: problem, users and goal are required. Mode 'strict' (default) blocks advancing until each phase is complete; 'free' allows advancing and reports what was skipped.

  • delete_flow

    Delete one saved flow diagram from a project, by the index shown by list_flows.

  • delete_project

    Permanently delete a project with its requirements and user stories. Requires confirm: true. This cannot be undone; issues already created in Jira are not touched.

  • delete_requirement

    Delete a requirement. It is also removed from the requirementIds of any user story that covered it.

  • delete_user_story

    Delete a user story.

  • duplicate_project

    Create a new project from an existing one, copying its requirements and user stories as open items. Useful as a template for a new client or product. Statuses and RICE scores are not copied.

  • export_backlog

    Export a project backlog as Markdown or CSV: requirements (most important first) and user stories.

  • export_dashboard

    Write a read-only HTML dashboard to data/exports/dashboard.html: phases, what is missing, musts covered by stories, RICE scores and flow diagrams. Open the file in a browser.

  • get_project

    Show a project's status: current phase, what is missing to advance, and linked items.

  • import_requirements

    Import requirements and user stories from CSV text, in the format produced by export_backlog. Requirement rows need type and title; story rows need persona, goal, benefit and criteria (separated by ' | '). Story-to-requirement links are not restored.

  • list_flows

    List the flow diagrams saved in a project, with their index. Use the index to refer to a diagram.

Show 16 more tools
  • list_projects

    List projects with their id, name, phase and status. Use it to find a projectId.

  • list_requirements

    List requirements, optionally filtered by priority, status and project. Most important first.

  • list_stories

    List user stories, optionally for one project, with their ids, criteria state and Jira key. Use it to find a storyId.

  • map_user_flow

    Generate a Mermaid flowchart from a list of steps. Steps are linked in order; a decision (diamond) gets a 'Yes' edge to the next step, or to 'yes' if set, and a 'No' edge to 'no' if set. With projectId, saves the diagram to the project.

  • open_dashboard

    Start the local, read-only Yeti dashboard and return its address (http://127.0.0.1:...). It shows phases, what is missing, musts and their stories, RICE and flows, and refreshes by itself. It runs on this computer only, while Yeti runs.

  • prioritize_rice

    Compute RICE scores (Reach × Impact × Confidence ÷ Effort) for a list of ideas and sort them. With projectId, saves the result to the project.

  • project_summary

    Summarise a project's progress: requirements by priority and status, story coverage of musts, acceptance criteria done, RICE leader, Jira links and what is missing to close.

  • push_to_jira

    Create Jira issues for a project: one Task per requirement and one Story per user story. Items already sent are skipped. With update: true, also refreshes the issues already linked. dryRun (default true) only lists what would be sent.

  • search_items

    Search requirements and user stories by text (case-insensitive). Optionally limit to one project.

  • set_criterion_status

    Mark one acceptance criterion of a user story as done or not done. The index is 0-based, in the order of the criteria.

  • set_project_mode

    Change a project's mode: 'strict' or 'free'. Applies from the next phase change.

  • set_requirement_status

    Mark a requirement as open or done.

  • sync_from_jira

    Read the status of linked Jira issues and mark items done in Yeti when their Jira issue is done. Requirements become done; stories get all their criteria ticked. Read-only on Jira.

  • update_project

    Change a project's name, problem, users or goal. Only the fields you pass are changed.

  • update_requirement

    Change a requirement's title, description or priority. Only the fields you pass are changed.

  • update_user_story

    Change a user story's persona, goal, benefit, linked requirements or acceptance criteria. Only the fields you pass change. Changing the criteria resets their done state.

Compare and alternatives

    Featured in

    Signals

    Stars
    0
    Forks
    0
    Open issues
    0
    Last commit
    Oct 23, 2026 (5 days ago)
    Last release
    Oct 23, 2026 (5 days ago)

    From GitHub (fetched Oct 24, 2026).

    Details

    Registry name
    io.github.macorifice/yeti
    Version
    1.0.3
    Auth
    API key
    Packages
    npm yeti-mcp
    License
    MIT
    Repository
    github.com/macorifice/yeti
    Website
    github.com/macorifice/yeti
    First seen
    Oct 24, 2026
    Last checked
    Oct 24, 2026
    Source
    Official MCP Registrygithub-graphql
    Cite this page

    Yeti MCP server. Agent Mart. https://agentmart.dev/connectors/macorifice-yeti (last updated 2026-10-24)