Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Point at visible targets in an agent-built interface, and deliver grounded Annotations.
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": {
"visual-intent-layer": {
"command": "npx",
"args": [
"-y",
"visual-intent-layer"
]
}
}
}Run this in your terminal
claude mcp add visual-intent-layer -- npx -y visual-intent-layerPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"visual-intent-layer": {
"command": "npx",
"args": [
"-y",
"visual-intent-layer"
]
}
}
}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": {
"visual-intent-layer": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"visual-intent-layer"
]
}
}
}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 willa-code, 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.4.0) reached the registry 2 months ago.
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, FlyDocs
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.
Spec-driven development workflow: your agent works issues, sessions and the status lifecycle.
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.
Point at a browser-rendered interface, describe what should change, and let an agent work from that precise visual context. Visual Intent Layer is a local MCP server and Review Surface for saved HTML documents and local web apps.
hello world! this project is a testbed for me to experience new/random/trending stuff! fyi on what i was testing:
Mobile builds, native windows, design files, and PDFs are outside the supported surface.
No hosted account or Rust toolchain is required.
Register the local stdio server with your agent, then restart the agent:
{
"mcpServers": { "visual-intent-layer": { "command": "npx", "args": ["-y", "--package", "visual-intent-layer@latest", "visual-intent-mcp"] } } }
The server must run on the machine where you look at the screen. It launches a browser there and binds a loopback port. A server in a container, on a remote host, or inside a cloud agent cannot display that machine's Review Surface.
Registry-aware clients can also find the server as io.github.willa-code/visual-intent-layer in the official MCP Registry, which lists where to get it rather than hosting it.
Claude Code
claude mcp add visual-intent-layer -- npx -y --package visual-intent-layer@latest visual-intent-mcp
Codex
codex mcp add visual-intent-layer -- npx -y --package visual-intent-layer@latest visual-intent-mcp
opencode
Run opencode mcp add visual-intent-layer, then provide npx and the package arguments when prompted:
-y --package visual-intent-layer@latest visual-intent-mcp
pi
pi does not ship an MCP client. With pi-mcp-adapter installed, add this to the project's .mcp.json (merge it into an existing mcpServers object):
{
"mcpServers": { "visual-intent-layer": { "command": "npx", "args": ["-y", "--package", "visual-intent-layer@latest", "visual-intent-mcp"] } } }
The same entry can be placed in .pi/mcp.json for a project-only Pi override, or ~/.config/mcp/mcp.json for all projects. The adapter's /mcp setup panel can also create the entry.
Other MCP clients
Use the JSON configuration above, or launch a local stdio server with command npx and arguments -y --package visual-intent-layer@latest visual-intent-mcp.
The package also provides a local CLI:
npx -y --package visual-intent-layer@latest visual-intent open --html ./checkout.html
npx -y --package visual-intent-layer@latest visual-intent open --app http://localhost:5173
Each command opens the default browser and prints the review URL. Add --no-open for headless or scripted use. To run only the local service:
npx -y --package visual-intent-layer@latest visual-intent serve --port 3742
The visual-intent command is also available after npm install -g visual-intent-layer.
The server writes review data to ~/.visual-intent-layer/data by default. It does not write agent configuration. Uninstalling the package does not delete reviews; remove that data directory only when you want to remove them.
Set VISUAL_INTENT_DATA_DIR to choose another data directory. Set VISUAL_INTENT_NO_OPEN=1 to suppress automatic browser opening.
@latest is resolved when npx fetches the package, so there is usually nothing to update by hand. pi-mcp-adapter caches the resolved command for 24 hours; delete ~/.pi/agent/mcp-npx-cache.json to force a fresh fetch. Replace @latest with an exact version in the entry to hold a version still, and update a global install with npm install -g visual-intent-layer@latest.
To uninstall, remove the entry with the mechanism you added it with — claude mcp remove visual-intent-layer, codex mcp remove visual-intent-layer, or by editing your client's configuration. docs/guide.md names the file for each client. Uninstalling deletes none of your reviews: they stay in the data directory until you remove it.
docs/guide.md — product manual, Review Surface, Annotation model, MCP tools, data, schema, development, and layout.design.md — normative Review Surface design contract.docs/design-references.md — component references and verification notes.docs/reference-foundations.md — comparison of candidate reference foundations.SECURITY.md — threat model, supported versions, and disclosure process.docs/adr/ — architectural decisions.docs/pi-validation.md — live Pi validation checklist.Apache-2.0.