Jonybur MCP Server

What the code does

We have not read this server's code yet

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

пакет @locus-dev/mcp-server ссылается на jonybur-oc/locus

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add mcp-server -- npx -y @locus-dev/mcp-server

{
  "mcpServers": {
    "mcp-server": {
      "args": [
        "-y",
        "@locus-dev/mcp-server"
      ],
      "command": "npx"
    }
  }
}

[mcp_servers.mcp-server]
command = "npx"
args = ["-y", "@locus-dev/mcp-server"]

{
  "mcpServers": {
    "mcp-server": {
      "args": [
        "-y",
        "@locus-dev/mcp-server"
      ],
      "command": "npx"
    }
  }
}

{
  "mcpServers": {
    "mcp-server": {
      "args": [
        "-y",
        "@locus-dev/mcp-server"
      ],
      "command": "npx"
    }
  }
}

This one needs environment variables set before it will start: PROTOTYPER_API_KEY (Optional: Locus API key for cloud team sync. Prefix ptmcp_. Not required for local stories.yaml mode.), PROTOTYPER_PROJECT_ID (Optional: Locus project UUID for cloud team sync.), LOCUS_STORIES_PATH (Optional: Explicit path to stories.yaml. Defaults to auto-discovery from project root.). The author declared them in the registry entry; get the values from the project itself.