Spec Driven Development
by formulahendry
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Runs on your computer★ 440MITUpdated 14 months ago
Install
Jev Use
Overview
Description from the maker (original English)
Typed yes/no, pick-one and score judgments from Jev in one batched call; typed escalation back.
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
- UsageiNot measured yet★ –
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Runs on your computer
- Transport: stdio
- Category: Other
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 1 of 1 passed
- Runs on your computer with your user’s permissions (files, network, apps).
- The registry lists no key to fill in.
You need
- npmNode.js installed (for the npx command)
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": {
"jev-use": {
"command": "npx",
"args": [
"-y",
"jev-use"
]
}
}
}Run this in your terminal
claude mcp add jev-use -- npx -y jev-useOr copy the settings yourself
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"jev-use": {
"command": "npx",
"args": [
"-y",
"jev-use"
]
}
}
}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.
Or copy the settings yourself
Paste into .vscode/mcp.json in your project
{
"servers": {
"jev-use": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"jev-use"
]
}
}
}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.
What it can do
Runs on your computer; the tool list appears in your AI app after you install it.
Basic checksi
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
- ✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account shitianfang, which owns the repo
- … Not checked yet
Still maintained
We have not read this repo from GitHub yet
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- – Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
- – Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
- … Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints
Compared with others in Otheri
- More stars than 0% of the other 18334 servers in this category
- Published to the registry more recently than 51% of the other 18334 servers in this category
- Basic checks equal to or better than 100% of the other 18334 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is Jev Use safe?
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.
What keys or codes does it need?
The registry does not list a required key, though some servers ask you to sign in on first use.
Does it run on my computer or in the cloud?
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).
Is it still maintained?
The GitHub repo last changed –, and the latest version (0.8.0) reached the registry 2 months ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
What can I use instead?
In the same category: Spec Driven Development, Remote Desktop Commander, ProAgentStore
Alternatives
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
Remote Desktop Commander
by desktop-commander
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Runs in the cloud★ 211Updated 2 days ago
Install
ProAgentStore
by ProAgentStore
MCP-first control plane for ProAgentStore agents and private instances.
Runs in the cloudUpdated today
Install
README from the maker
Open the README
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.
jev-use
English | 简体中文
The best way for Claude Code, Codex, and pi to work with Jev: hand the tasks that need no text output to Jev — faster steps, fewer tokens, tasks done sooner and better.
It makes the LLM and Jev true collaborators: when content needs to be written, the LLM takes over; when a step just needs a fast decision, Jev executes it.
Demos — real runs, 1× speed
Directions task: Jev clicks, the LLM types — 10 decisions (p50 274 ms) · 4 writes; Jev rejects a wrong route, the LLM rewrites
Context compaction — 200 messages judged in 7 calls, one LLM paragraph replaces the dropped pile; recall 3/3
Pong: ball speed = decision latency — 86 Jev decisions in 20 s vs 6 (haiku) and 3 (gemini) called the usual way; enum-constrain both and the gap is 3×
Gate every shell command — dangerous ones denied in ~230 ms with a reason, zero LLM tokens
Every demo is a rerunnable script in bench/examples/; all numbers, methodology, variance and caveats: bench/RESULTS.md · third-party measurements: docs/evidence.md.
Install
npx -y jev-use install # wires Claude Code, Codex, and pi — whichever it findsSet one key in the environment your agent runs in (JEV_BACKEND=mock for a keyless dry run):
| Provider | Env var |
|---|---|
| TypeSafe direct | TYPESAFE_API_KEY |
| OpenRouter | OPENROUTER_API_KEY |
| Vercel AI Gateway | AI_GATEWAY_API_KEY |
npx -y jev-use doctor checks the wiring. Judged state goes to the provider you configure; JEV_BACKEND=mock stays local. Plugin form with the routing skill and the PreToolUse gate: harness/claude-code · harness/codex.
Use as a library
npm i jev-use — zero runtime dependencies on the judgment path:
import { Jev, check, pick, rate } from "jev-use";const jev = new Jev();
const { answers } = await jev.judge(state, { next: pick("Next action?", { merge: "all green", rerun: "looks flaky", hold: "needs attention" }), risk: rate("How risky?", ["routine", "worth a look", "incident"]), passed: check("Did the run fully succeed?"), }); // answers.next → { answer: "merge", confidence: 0.93, confidenceFrom: "reported", escalate: false }
Anything Jev can't or shouldn't decide comes back with escalate: true and a typed reason. Tools, verdict shape, escalation contract, CLI: docs/reference.md.
Small enough to read
| File | Job |
|---|---|
| src/protocol.ts | Questions (check/pick/rate), verdicts, escalation reasons |
| src/dispatch.ts | Pre-call routing: what never reaches Jev |
| src/judge.ts | screen → backend → hand back what is unsure; gate |
| src/jev.ts | The Jev client over that engine |
| src/redact.ts | Credentials stripped from a gated action before it is sent |
| src/backends/ | TypeSafe, OpenRouter, Vercel, mock adapters |
| src/server.ts | The two MCP tools |
| src/cli.ts | install, serve, hook gate, doctor |
| skills/jev-use/SKILL.md | The routing rules the agent follows |
Development
$ npm run typecheck && npm test # unit tests incl. per-provider wire fixtures$ npm run smoke # real MCP client ↔ built CLI over stdio $ node bench/run.mjs # micro-benchmarks, your key and region
Substantially written with Claude Code (AI-assisted).
MIT © shitianfang