Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Typed noul / choice / score judgments from a local Laya model, with token-budget preflight.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"laya": {
"command": "npx",
"args": [
"-y",
"laya-mcp"
]
}
}
}Run this in your terminal
claude mcp add laya -- npx -y laya-mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"laya": {
"command": "npx",
"args": [
"-y",
"laya-mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"laya": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"laya-mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified with the GitHub account PerryLink, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.1.5) reached the registry last month.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, Tools MCP
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Web production tools for AI agents: contrast, JP text, WebP, JSON-LD, slugs, dates and 40+ more
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
MCP server for Laya typed decisions — noul (yes/no), choice, score — wrapped so it survives contact with a server.
English · 简体中文 · Español · Português · हिन्दी
npx -y laya-mcp --help
Registered as io.github.PerryLink/laya-mcp in the official MCP Registry.
This npm package is a launcher, not an implementation. Laya is a PyTorch
model, so the server itself is Python. Installing this package gets you the
Node entry point and nothing else; you also need the Python side:
`bash
pip install "laya-mcp[mcp]"
`
npx laya-mcpfinds that interpreter, hands stdio to it, and passes the MCP
stream through untouched. It does not install anything for you — fetching torch
(~2 GB) and a checkpoint (~650 MB) as a side effect of running a command is not
something a launcher should do.
On Windows, python on PATH is often the Microsoft Store execution alias, which is a stub: it cannot import anything, and it sits ahead of your real interpreter. The launcher therefore reports what it tried rather than claiming the package is missing. Point it at the right interpreter either way:
# name it outright
set LAYA_MCP_PYTHON=C:\path\to\python.exe # Windows export LAYA_MCP_PYTHON=/path/to/python # macOS, Linux
LAYACORE_PYTHONis still read. 0.1.0 and 0.1.1 printed that name in the error
message, and a launcher that stopped honouring the variable its own previous
version told you to set would be worse than one carrying the alias.
Status: 0.1.5, work in progress. The Python core is implemented and covered
by CI. The launcher itself is covered by ten checks over interpreter discovery,
which is where it has been wrong before. Interfaces may move before 1.0.
Laya truncates things silently and reports none of it:
This package adds a preflight that reports what would be cut, structured errors that name the offending question, an honest confidence contract, and a health surface that admits a demotion.
laya-mcp serve # warm HTTP sidecar on 127.0.0.1:8787 (loads the model once)
laya-mcp mcp # MCP over stdio laya-mcp doctor # what is installed, and whether the GPU really works laya-mcp install # register with whichever agent harness you have
install handles the fact that there is no portable way to register an MCP server: Claude Code (mcpServers), Codex ([mcp_servers. ]), opencode (mcp, with an array command), OpenClaw (mcp.servers) and Hermes (mcp_servers) each get the right shape written to the right file, merged and backed up rather than overwritten. pi has no native MCP support and is reported as unsupported.
Prefer serve plus --sidecar over hosting the model in each stdio process: a harness spawns one server per session, and loading a 650 MB checkpoint per session is the main reason a Python-backed MCP server feels slow.
Upstream's own numbers, repeated because an integration that implies otherwise is lying to you: the base checkpoints are near chance zero-shot on typed decisions (0.362 against a 0.461 majority-class baseline); score is the weakest primitive (35% vs 70% in independent measurement); raw calibration error is 0.466 before temperature fitting; and one fixture run answered "A" on 46 of 50 multiple-choice items.
Calibration makes a probability honest; it cannot make a model right.
Apache-2.0. Laya is Apache-2.0 by Convai Innovations. This is an independent integration, not affiliated with or endorsed by that project.