mcpField
J
jonybur

jonybur

Local
github.com/jonyburDeveloper Tools

About jonybur

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

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"jonybur": {
"command": "npx",
"args": [
"-y",
"@locus-dev/mcp-server"
],
"env": {
"PROTOTYPER_API_KEY": "<PROTOTYPER_API_KEY>",
"PROTOTYPER_PROJECT_ID": "<PROTOTYPER_PROJECT_ID>",
"LOCUS_STORIES_PATH": "<LOCUS_STORIES_PATH>"
}
}
}
}
Run commandnpx -y @locus-dev/mcp-server
Environment variables to set
PROTOTYPER_API_KEYSecretOptional: Locus API key for cloud team sync. Prefix ptmcp_. Not required for local stories.yaml mode.
PROTOTYPER_PROJECT_IDOptional: Locus project UUID for cloud team sync.
LOCUS_STORIES_PATHOptional: Explicit path to stories.yaml. Defaults to auto-discovery from project root.

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npm@locus-dev/mcp-server0.5.0

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

The maintainer has not added details yet. Check the README in the repository.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.