Jonybur

io.github.jonyburPublished by GitHub account jonyburv0.5.0Updated Oct 24, 2026

stories.yaml — an open specification for software requirements, enforced by CI.

VerifiedSTDIODesktop onlyDeveloper Tools

Overview

AI-generated overview

A local MCP server for stories.yaml, an open specification for software requirements, letting an assistant work with requirement stories in a project.

What you can do
Works with stories.yaml, an open specification for software requirements that is enforced by CI, so an assistant can help manage requirement stories in a project. It can use an explicitly configured stories file path or auto-discover the file from the project root. It can optionally sync with a Locus cloud team workspace when an API key and project ID are supplied. No individual tools are listed in the manifest, so the exact operations are not documented here.
When to use it
Worth adding when a project keeps its software requirements as stories.yaml and you want an assistant to help read or maintain those stories, especially in a team that enforces the specification in CI.
Requirements
Runs as a local process over stdio, installed from the npm package @locus-dev/mcp-server, so Node.js is needed. Optionally set LOCUS_STORIES_PATH to point at a stories.yaml file; otherwise it auto-discovers from the project root. Cloud team sync needs PROTOTYPER_API_KEY and PROTOTYPER_PROJECT_ID.
Before you install
The optional PROTOTYPER_API_KEY is a secret used for cloud team sync; keep it out of shared files. With cloud sync enabled, project requirement data may be sent to the Locus service. The manifest lists no tools, so confirm what the server can read or change before pointing it at real project files.

Installation

In SourceWeft

  1. Open Jonybur in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.5.0LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.