Mcp Server
Expose repo-local stories.yaml requirements to your agent with optional Locus cloud sync via the Locus monorepo mcp-server package.
Overview
io.github.jonybur/mcp-server is a Validate-phase MCP server that lets agents work with CI-enforced stories.yaml requirements and optional Locus cloud sync.
What is this MCP server?
- MCP access to stories.yaml requirements spec with CI enforcement
- Same @locus-dev/mcp-server npm entry (v0.5.0) from github.com/jonybur/locus packages/mcp-server
- Local-first: no API key required when working only with discovered stories.yaml
- Optional cloud sync with PROTOTYPER_API_KEY (ptmcp_) and PROTOTYPER_PROJECT_ID
- LOCUS_STORIES_PATH for monorepos or non-default spec locations
- Version 0.5.0 published as npm identifier @locus-dev/mcp-server
- Repository subfolder packages/mcp-server on github.com/jonybur/locus
- Optional env configuration: PROTOTYPER_API_KEY, PROTOTYPER_PROJECT_ID, LOCUS_STORIES_PATH
What problem does it solve?
Requirements in stories.yaml are invisible to your agent unless you copy-paste, so implementations silently exceed scoped stories.
Who is it for?
Developers on the jonybur/locus ecosystem who standardize on stories.yaml and want MCP-native requirement access in the IDE.
Skip if: Projects without stories.yaml or CI enforcement, or buyers seeking only GitHub Issues/Jira MCP with no spec-in-repo workflow.
What do I get? / Deliverables
Registering the server lets agents ground edits in stories.yaml your CI already enforces, keeping validate-to-build work traceable to named stories.
- MCP bridge from agent sessions to enforced stories.yaml content
- Clearer traceability from scoped stories to agent-generated implementation work
Recommended MCP Servers
Journey fit
Validate centers on proving what you will build; CI-backed stories.yaml keeps agent-assisted coding inside declared scope. Scope holds the canonical requirement file and story breakdown agents should consult before generating implementation plans or code.
How it compares
Locus stories.yaml requirements MCP (v0.5.0 monorepo package)—not an autonomous PM agent skill marketplace entry.
Common Questions / FAQ
Who is io.github.jonybur/mcp-server for?
It is for builders using Locus and stories.yaml who want coding agents to interact with enforced requirement files from the official locus repo mcp-server package.
When should I use io.github.jonybur/mcp-server?
Use it while defining and tightening scope in Validate and when implementing features that must map to stories.yaml during Build.
How do I add io.github.jonybur/mcp-server to my agent?
Install @locus-dev/mcp-server (0.5.0) as an stdio MCP server in your agent config; set LOCUS_STORIES_PATH if needed; add Prototyper/Locus env vars only for cloud sync.