Mcp Server
Keep software requirements in stories.yaml aligned with CI and let agents read or update the spec through Locus MCP.
Overview
io.github.jonybur-oc/mcp-server is a Validate-phase MCP server that exposes stories.yaml software requirements—CI-enforced and optionally Locus-synced—to AI coding agents.
What is this MCP server?
- Bridges agents to stories.yaml—the open software-requirements spec enforced in CI
- Works locally with auto-discovered stories.yaml; optional Locus cloud sync via PROTOTYPER_API_KEY
- Optional LOCUS_STORIES_PATH override when the spec lives outside default discovery
- Published as @locus-dev/mcp-server npm package (v0.6.1) with stdio transport
- Optional PROTOTYPER_PROJECT_ID for team project UUID when using cloud sync
- Package @locus-dev/mcp-server version 0.6.1 on npm with stdio transport
- Core artifact: stories.yaml open specification enforced by CI
- Three optional env vars: PROTOTYPER_API_KEY, PROTOTYPER_PROJECT_ID, LOCUS_STORIES_PATH
What problem does it solve?
Your agent ships code that drifts from agreed requirements because stories live in docs the agent cannot read or update consistently with CI.
Who is it for?
Solo builders and small teams adopting stories.yaml or Locus who want agent edits grounded in enforceable requirement files.
Skip if: Codebases with no stories.yaml discipline, or teams that only want generic issue-tracker MCP without a spec-in-repo model.
What do I get? / Deliverables
After install, agents work against the same stories.yaml your CI enforces, tightening scope discipline from validation through implementation.
- Agent-readable and agent-updatable stories.yaml requirements aligned with CI gates
- Optional cloud-synced requirement state when Locus/Prototyper credentials are configured
Recommended MCP Servers
Journey fit
Validate is where you lock scope before full build; stories.yaml is an enforceable requirements contract, not ad-hoc notes. Scope subphase is the canonical home for requirement definitions, acceptance criteria, and story files that gate what you commit to build.
How it compares
Requirements-spec MCP (stories.yaml + optional Locus)—not a code review skill or a deployment integration.
Common Questions / FAQ
Who is io.github.jonybur-oc/mcp-server for?
Builders using stories.yaml or Locus who want Claude Code, Cursor, or Codex to read and maintain requirements that CI can enforce.
When should I use io.github.jonybur-oc/mcp-server?
Use it when scoping and refining features in Validate, and while implementing against stories.yaml during Build and Ship prep.
How do I add io.github.jonybur-oc/mcp-server to my agent?
Add the @locus-dev/mcp-server npm MCP via stdio in your agent; for local mode place or point to stories.yaml (LOCUS_STORIES_PATH optional). Add PROTOTYPER_API_KEY and PROTOTYPER_PROJECT_ID only for cloud sync.