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
Clify
Overview
Description from the maker (original English)
Verified websites as JSON commands for AI agents over plain curl or MCP.
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 checksi0 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 in the cloud
- Transport: Streamable HTTP
- Category: Other
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 0 of 1 passed
- Runs on the maker’s server: what you ask it goes through their server.
- The registry lists no key to fill in.
You need
- Runs in the cloudNothing to install; it connects over the internet
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
- Open Settings → Connectors
- Press Add custom connector
- Paste the address below and press Add
- If it asks you to sign in, sign in with the maker
https://bold-cloud-h4u6s.run.mcp-use.com/mcpRun this in your terminal
claude mcp add --transport http clify https://bold-cloud-h4u6s.run.mcp-use.com/mcpOr copy the settings yourself
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"clify": {
"url": "https://bold-cloud-h4u6s.run.mcp-use.com/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.
Or copy the settings yourself
Paste into .vscode/mcp.json in your project
{
"servers": {
"clify": {
"type": "http",
"url": "https://bold-cloud-h4u6s.run.mcp-use.com/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.
ChatGPT connects only to servers on the internet:
- Open ChatGPT on the web → Settings → Connectors (Apps)
- Press Create or Add (some plans need Developer mode under Advanced first)
- Paste the address below, give it a name and save
- If it asks you to sign in, sign in with the maker
https://bold-cloud-h4u6s.run.mcp-use.com/mcpMenu names can differ slightly by plan and over time.
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
We have not read this server’s tool list yet; we check endpoints in rotation.
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 6, 2026
- ! Caution
Maker matches the repo
The publisher (clify-dev.netlify.app) is not the repo owner (ToukoUrsin); someone else may have listed it
- … 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 checked yet
Endpoint responds
Not checked yet; we check endpoints in rotation
- … Not checked yet
Sign-in with OAuth
Not checked yet; we check endpoints in rotation
- … Not checked yet
No hidden instructions in tool descriptions
Not checked yet; we read the tool list when we check the endpoint
Compared with others in Otheri
- More stars than 0% of the other 32410 servers in this category
- Published to the registry more recently than 68% of the other 32410 servers in this category
- Basic checks equal to or better than 35% of the other 32410 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 Clify safe?
It passed 0 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 in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
Is it still maintained?
The GitHub repo last changed –, and the latest version (0.3.0) reached the registry 17 days ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
What can I use instead?
In the same category: Spec Driven Development, Remote Desktop Commander, debuff
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 yesterday
Install
debuff
by debuffjp
Let coding agents play, test and tune your 2D web game: live state, explained errors, replays, fuzz.
Runs on your computerUpdated 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.
clify: the web, rebuilt for agents
clify turns most websites into a JSON CLI and an MCP server: so far 156 public sites ship with verified commands (open data and government, developer registries, science, maps and weather, culture, news, sports, jobs). An agent explores the site once in a headless browser, records the requests behind what it clicks, writes a typed command for each, and tests every command live before keeping it. After that, agents call the site's own endpoints instead of clicking through pages: same answers, a fraction of the time, tokens and RAM. When a site needs an account, clify signs in with its own identity (email and phone) or with yours. When it hits a CAPTCHA, it stops and asks a human.
Replay of one live run (2026-10-18T09-57-57-642Z), sped up: the GIF starts at 0:17 on the race clock, once the browser has loaded its first page, and plays the 4× video at 4× again (16×). The same model (Claude Opus 5.5) does the same six jobs on five signed-in SaaS dashboards and a forum, once through a browser and once through clify with specs generated by clify add (5 of 6 CLIs generated; svix's robots.txt forbids exploring, so its spec is hand-written). This run: 4.0× faster, 7.3× cheaper. Over all 6 runs: 3.3× faster by mean time (288 s vs 87 s), paired per-run mean 3.5×; 7.3× cheaper by mean cost, paired 7.4×. Details below and in race/.
In numbers: 156 sites ship with 1,802 live-verified read commands in the CLI and hosted MCP, including a new U.S./San Francisco set for events, startup hiring, transit, listings, local news, public data and prediction markets.
Built for YC's *Make Something Agents Want* hackathon (Oct 17–18, 2026).
Use it with curl, nothing to install
The public agent API is at https://clify-dev.netlify.app. It needs no install, key, or account:
curl "https://clify-dev.netlify.app/search?q=SF+tech+events"curl "https://clify-dev.netlify.app/luma/discover-events?city=San%20Francisco" curl "https://clify-dev.netlify.app/bart/get-departures?station=16TH"
Use /sites.json for the catalogue, /llms.txt for the full agent guide, and / .json for commands and verified example URLs. Task-specific entry points start with San Francisco and U.S. agent tasks, Luma events, YC startup jobs, BART departures, Craigslist SF listings, and DataSF. Finnish sites remain in the catalogue; their task pages are still available. Machine-readable discovery manifests are at /agent.json and /.well-known/webmcp.json.
Live demo: 6 browser agents vs 6 clify agents
Twelve Claude Code agents (Claude Opus 5.5) start at the same moment: on each of the six sites above, one works in a browser and one with clify, same prompt, same accounts. Every account was created by the agent itself with its own email. Each tile turns green when an independent check finds the object on the live site. Recorded live run of Oct 18, 08:58 PT: clify all 6 verified at 0:27.6 for $0.64; browser agents all 6 verified at 1:43.8 for $2.06. Run it yourself: race/bin/grid (on the machine with the sessions) or race/bin/mac-demo (from a laptop, over ssh); details in race/.
Try it in 10 seconds (hosted MCP, nothing to install)
claude mcp add --transport http clify https://bold-cloud-h4u6s.run.mcp-use.com/mcpThen ask your agent something like *"latest serde version on crates.io and the NWS forecast for San Francisco"*. The server holds 156 sites and 1,802 live-verified commands behind 3 core tools (clify_sites, clify_help, clify_run) plus 4 direct shortcuts for popular commands; the whole tool list costs about 2.5k tokens instead of 569k (one tool per command), and the 3 core tools alone about 1.4k. Codex: codex mcp add clify --url https://bold-cloud-h4u6s.run.mcp-use.com/mcp. Read-only and public; write commands return a preview and need confirm: true. More in mcp/.
Or email the agent: send clify@fine-vale.primitive.email a question like *"latest tokio version and its downloads"*. The always-on clify agent runs it with clify on its own InstaBox and answers in your thread, usually within a minute (read-only public sites, 5 jobs per sender per day).
Is it alive? https://clify-agent-b3d326.inkboxwire.com/status: the agent's read-only status page (uptime, jobs today, last reply, model), served from its InstaBox at its Inkbox internet address.
Quickstart (local CLI)
Node 22+. clify is not on npm (npm i clify is an unrelated package): clone the repo. clify add and logins need Chromium; using a CLI needs nothing else.
git clone https://github.com/ToukoUrsin/clify && cd clify/clifynpm install npx playwright install chromium # for clify add, repair, login (or set CLIFY_CHROME) export PATH="$PWD/bin:$HOME/.clify/bin:$PATH"
clify list --query "SF events" # find a site: 156 verified site CLIs ship built in clify crates search-crates --q "http client" --sort downloads --limit 3 clify weather get-point --lat 37.77 --lon -122.42
export ANTHROPIC_API_KEY=... # model access, only for clify add / repair clify add https://metacpan.org/ # explore → generate → verify live → install (2–6 min typical, up to ~15 on big sites)
Every command prints one JSON object ({"ok":true,"count":N,"nextPage":...,"data":...}); errors carry next, the exact command to run next. clify mcp serves everything installed as a local MCP server. Agents should start at AGENTS.md, clify/AGENTS.md, llms.txt or clify guide.
Headline numbers
All runs are real, on live sites, with claude-opus-5-5. Ratios are clify vs a browser agent doing the same task with the same model and prompt.
| Test | Result | Evidence |
|---|---|---|
| Race, specs generated by `clify add` (6 jobs on 5 signed-in dashboards + 1 forum; 6 runs, every racer 6/6 verified; 5 of 6 specs generated: svix's robots.txt forbids exploring, so its spec is hand-written and labelled) | 3.3× faster by mean time (288 s vs 87 s); paired per-run mean 3.5×. 7.3× cheaper by mean cost ($2.06 vs $0.28; paired 7.4×), 14.4× fewer tokens incl. cache (paired 14.8×), 9.5× less RAM (paired 9.4×) | race/README.md, generated-r5-runs.txt, specs + generation logs, video accounts-4x.mp4 |
| Race, hand-written specs (same jobs, 7 runs) | 4.5× faster by mean time (314 s vs 69 s); paired per-run mean 4.4×. 6.2× cheaper by mean cost ($1.87 vs $0.30; paired 6.2×), 13.0× fewer tokens incl. cache (paired 12.9×), 10.0× less RAM (paired 10.1×) | accounts-runs.txt, video accounts-4x-handwritten.mp4 |
| Browser with page JavaScript (mode B, the strong baseline), round 5 | B 253 s / $1.74 vs clify 108 s / $0.30 in the same run: clify 2.3× faster, 5.9× cheaper, 10.6× fewer tokens incl. cache. Page JavaScript barely helps on these dashboards (B 253 s vs clicks-only A's 288 s mean); B's means in earlier rounds: 341 s (round 3, n=3), 435 s (round 4, n=2) | race/README.md, generated-r5-runs.txt |
| Benchmark: 20 easy public read-only tasks on 11 sites (10 of the 20 tasks on 4 scraping-practice sites), hand-written specs, 40 runs per mode (the CLIs for these 11 sites were written by hand before the benchmark, not generated; ground truth was recomputed with clify right before each run, and an independent recheck without clify agrees on 20 of 20 tasks: truth-check.txt) | all modes 40/40 correct. clify 9.0 s / 16.5k tokens / $1.28 total vs clicks-only browser 16.1 s / 79.4k / $4.12: 1.8× faster, 4.8× fewer tokens, 3.2× cheaper. vs browser + page JS: 1.4× / 3.1× / 1.8× | bench/README.md, summary, every run's prompt and result in bench/runs/ |
"By mean" divides the browser's mean (clicks-only runs) by clify's mean (all runs); "paired" is the mean of the per-run ratios in the clicks-only runs, where both racers ran at the same moment. With generated specs the clify agent now makes as many model calls as with hand-written ones (16.8 vs 17 per run) and costs about the same ($0.28 vs $0.30): clify add fills the signed-in account's project/org/team ids in by itself and prints compact help (race/README.md, round 5). Both sets are published. Every number in this README is derived from its source files and checked by scripts/counts.mjs.
Versus an agent with curl
Same model, same prompts, the agent given curl, jq, python3, WebFetch and WebSearch instead of clify (no browser):
- Public read-only benchmark: curl wins. curl 40/40, 7.5 s / 10.2k tokens / $1.12 vs clify 40/40, 9.0 s / 16.5k / $1.28 (median time, median tokens, total cost). These sites have documented JSON APIs or are scraping sandboxes the model knows by heart, so curl usually answers in one call; clify reads its help first. bench/README.md
- Signed-in dashboards (race mode D, curl handed the same saved cookies and tokens as files): both 6/6, clify ahead. D 97 s / $0.52 vs clify 66 s / $0.29 in the same 2 runs (D 6/6 and clify 6/6 every run; paired: D 1.5× slower, 1.8× the cost). curl spends its extra calls re-discovering forms, CSRF fields and API paths in every run; on the public forum it beat clify. race/README.md (mode D)
So clify's value is not on sites whose API the model already knows. It is in the signed-in, undocumented parts: requests discovered once and verified by clify add instead of re-discovered every run, sessions kept in a vault (the login, signup and 2FA that produced the sessions D used were clify's), and account ids filled in. Most of the gap to a browser agent is the browser: curl with sessions is also 3× faster and 4× cheaper than clicking.
What's proven
- Most URLs → verified CLI.
clify addon 44 public sites it had never seen: 41 (93%) ended with 3 or more live-verified commands, 514 verified in total, 2–6 minutes each, no human edits. The 3 misses are behind bot walls, which clify reports and does not get around. clify/proofs/sites.md. A second sweep of 116 more sites in Blaxel sandboxes brings it to 133 of 160 sites with 3+ verified commands and 1,634 verified commands (1,628 of them on those 133 sites, listed in wall.json; 6 more on 3 sites that stayed under 3); every miss is listed with its reason. 132 of the 133 ship built into clify (RubyGems' generated spec stays in proofs/sites/). clify/proofs/sites-blaxel.md - Agents use it unaided. Fresh
claude -pagents with Bash limited toclifysolved 6/6 real tasks (handoff.md). Cold start: a fresh agent in an empty directory cloned this public tree, installed clify, ranclify add https://flathub.org/itself (8 of 8 commands verified) and answered corr
Only the beginning is shown; read the rest in the repo