Skip to content

Releases: macorifice/yeti

Yeti 1.0.3

Choose a tag to compare

@macorifice macorifice released this 23 Oct 23:30
367cedc

Patch release. The npm package now declares its MCP Registry name (mcpName: io.github.macorifice/yeti), so Yeti can be listed in the official MCP Registry. No code changes.

Yeti 1.0.2

Choose a tag to compare

@macorifice macorifice released this 23 Oct 23:24
b9479f0

Patch release.

  • Fix: the yeti-mcp command now runs. npx yeti-mcp and npx yeti-mcp dashboard failed in 1.0.0 and 1.0.1, because the entry file had no node shebang. Configurations that run node dist/index.js directly were not affected.
  • Docs: README with dashboard screenshots, an npx quick start, and tools grouped by area.

Yeti 1.0.1

Choose a tag to compare

@macorifice macorifice released this 23 Oct 23:14
bcf328e

Patch release. The npm package now links to GitHub Sponsors (npm fund), and the README has a Sponsor section. No code changes.

Yeti 1.0.0

Choose a tag to compare

@macorifice macorifice released this 23 Oct 22:59
22a945c

Yeti is an MCP server that guides product design through five phases, from the problem to a verified scope, and hands execution over to Jira.

What is in 1.0.0

Design workflow

  • Projects move through discovery, definition, prioritization, flows and verification. In strict mode a phase advances only when it is complete; in free mode it advances and reports what was skipped.
  • Requirements with MoSCoW priorities, user stories linked to requirements, acceptance criteria you can tick, RICE scoring, Mermaid flows with Yes/No branches, next and ends.
  • Verification requires every must to be done and covered by a user story.

Working with the backlog

  • Edit, delete, search, archive and duplicate projects and items; project summary.
  • Export to Markdown or CSV, optionally saved to a file; import requirements and stories from CSV.

Jira

  • push_to_jira creates a Task per requirement and a Story per user story, with dry-run by default, limit, and no duplicates; update refreshes linked issues.
  • sync_from_jira marks items done when their issue is done and reopens what it completed when the issue goes back.

Dashboard

  • open_dashboard (or npx yeti-mcp dashboard) serves a read-only page on 127.0.0.1: phases, what is missing, musts and their stories, criteria, RICE and flows. It refreshes every 10 seconds.

Storage

  • Data lives in SQLite (data/yeti.sqlite); a data/db.json from earlier versions is imported once.

Requirements

  • Node.js 22.13 or later.
  • Jira credentials only for the Jira tools (JIRA_SITE, JIRA_EMAIL, JIRA_API_TOKEN).

Changes since 0.9.0

  • New live dashboard and open_dashboard tool.
  • The MCP server now reports its real version, read from package.json.

Yeti 0.9.0

Choose a tag to compare

@macorifice macorifice released this 23 Oct 22:40
e06fbd6

What's Changed

Full Changelog: v0.8.0...v0.9.0

Yeti 0.8.0

Choose a tag to compare

@macorifice macorifice released this 23 Oct 22:23
3840151

What's Changed

Full Changelog: v0.7.0...v0.8.0

Yeti 0.7.0

Choose a tag to compare

@macorifice macorifice released this 23 Oct 22:06
b97ad93

What's Changed

Full Changelog: v0.6.1...v0.7.0

Yeti 0.6.1

Choose a tag to compare

@macorifice macorifice released this 23 Oct 19:37
a79e519

Patch release: README now documents the Jira credentials. No code changes.

Yeti 0.6.0

Choose a tag to compare

@macorifice macorifice released this 23 Oct 19:21
379bd20

What's Changed

Full Changelog: v0.5.0...v0.6.0

Yeti 0.5.0

Choose a tag to compare

@macorifice macorifice released this 23 Oct 18:15
e6f45c7

What's Changed

Full Changelog: v0.4.0...v0.5.0