Jonybur Oc

io.github.jonybur-ocPublished by GitHub account jonybur-ocv0.6.1Updated Oct 27, 2026

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

Overview

AI-generated overview

Local stdio MCP server that gives an assistant access to stories.yaml, an open specification format for software requirements enforced by CI.

What you can do
  • Works with stories.yaml, an open specification for software requirements that is enforced by CI.
  • Reads a project's stories file, either from an explicit path or through auto-discovery from the project root.
  • Optionally syncs 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
Useful when a project keeps its requirements as stories.yaml and you want an assistant to work with those specs alongside the code, or when a team wants local spec access plus optional cloud sync.
Requirements
Runs as a local process over stdio, installed from the npm package, so Node.js is needed. Optionally set LOCUS_STORIES_PATH to point at a specific stories.yaml; otherwise it auto-discovers from the project root. Cloud team sync needs PROTOTYPER_API_KEY (prefix ptmcp_) and PROTOTYPER_PROJECT_ID. Desktop only.
Before you install
The optional PROTOTYPER_API_KEY is a secret credential for cloud team sync; keep it out of shared config. Cloud sync sends project data to a third-party service. The manifest lists no tools, so review what the server can read or change before installing.

Installation

In SourceWeft

  1. Open Jonybur Oc 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.6.1LatestSep 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.