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
VibeRevert
Overview
Description from the maker (original English)
Local MCP server for AI coding safety: risk checks, sessions, checkpoints, and fix prompts.
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": {
"viberevert": {
"command": "npx",
"args": [
"-y",
"viberevert",
"mcp",
"serve"
]
}
}
}Run this in your terminal
claude mcp add viberevert -- npx -y viberevert mcp serveOr copy the settings yourself
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"viberevert": {
"command": "npx",
"args": [
"-y",
"viberevert",
"mcp",
"serve"
]
}
}
}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": {
"viberevert": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"viberevert",
"mcp",
"serve"
]
}
}
}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 6, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified against the domain viberevert.com (the registry checks domain ownership)
- … 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 32455 servers in this category
- Published to the registry more recently than 26% of the other 32455 servers in this category
- Basic checks equal to or better than 100% of the other 32455 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 VibeRevert 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.7.1-beta.4) reached the registry 3 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, SSTracker free youth training
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
SSTracker free youth training
by sstracker.app
Free youth sports drills, practice plans and age-group answers for parents and coaches.
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.
VibeRevert
Protect the project you're actually working on.
Record · Check · Fix · Restore.
VibeRevert is the project-integrity layer for AI coding. It records the real working state before an agent starts, flags risky changes with deterministic rules, and lets you remove the agent work you don't want without giving up the rest.
An agent changed 80 files. 75 are useful. Remove the 5 you don't.
No AI judges the AI: risk findings are reproducible, explainable, and based on rules you can inspect.
The working state you already had is part of the project. Staged work, unstaged edits and pre-existing untracked files are recorded before the session starts and preserved through recovery. You don't have to package your work into commits before letting an agent help with it.
Keep using your coding agent. VibeRevert works alongside Claude Code, Cursor, and other coding-agent workflows. Git worktrees give an agent an isolated checkout; VibeRevert protects and selectively recovers the working state an agent actually changes. They solve different problems and can be used together.
*AI broke your project? Undo the session, not your week.* Whole-session rollback is still one command.
See it work
The actual CLI, condensed from a real beta payment run — check flags it, and rollback previews what it will change before you --apply:
$ viberevert checkrisk: CRITICAL · payments app/api/checkout/route.ts payments (critical) app/api/webhooks/stripe/route.ts payments (critical)
$ viberevert rollback # preview — nothing changed yet package.json tracked_restored app/page.tsx tracked_restored app/api/checkout/route.ts untracked_deleted app/api/webhooks/stripe/route.ts untracked_deleted lib/stripe.ts untracked_deleted .gitignore README.md (your uncommitted work) skipped_unchanged
Proof, not promises
3 real AI coding sessions. 3 exact project-file restorations. Payments, database migrations, and deployment infrastructure — all with pre-existing uncommitted work preserved. Read the beta report →
Quickstart
Works inside a Git repository and requires Node.js 22+. VibeRevert keeps its records on your machine and requires no VibeRevert account or hosted service.
npm install -g viberevert@betaviberevert init # one-time setup in your projectviberevert run # records the session and saves your files' starting state viberevert check # see what changed and what looks risky viberevert rollback # preview putting your files back; add --apply to restore
Restoring only part of a session works the same way, with a selector:
viberevert rollback <session> --only 'app/api/**' # preview just that partviberevert rollback --only 'app/api/**' --apply # restore just that part
What it protects you from
You let an AI agent work across your project, and it touched more than you expected — maybe payment code, a database migration, a deploy file — while your own half-finished work was sitting right there uncommitted. VibeRevert captures your project's starting file state first, so a session you don't like doesn't cost you your afternoon.
What VibeRevert does
Around each AI coding session, VibeRevert:
- Checkpoints your project first — working tree, staged changes, and untracked files, including work you haven't committed.
- Records the session and the project files that changed while it ran.
- Flags risky edits — changes touching auth, payments, databases, secrets, dependencies, or infrastructure (risk taxonomy).
- Writes an agent-ready fix prompt from those findings, to paste into your next iteration.
- Restores your files to the checkpoint when you need it.
It warns you; it does not silently block your work. An optional pre-commit hook can reject a commit above your configured risk threshold — opt-in, tunable, and bypassable like any local Git hook.
Rules decide. Agents fix.
VibeRevert does not ask another language model whether your agent's changes look risky. Its checks are deterministic: the same inputs and configuration produce the same findings, with an inspectable reason for every flag.
When something needs attention, VibeRevert can turn those findings into an agent-ready fix prompt. The rules decide what to flag; you decide what happens next.
Roll back all of it, or only the part that went wrong
viberevert rollback restores your local project files — tracked, staged, and untracked, including uncommitted work — to how they were when the session started. It previews by default; --apply writes the change, and every apply first saves an emergency checkpoint you can recover from.
Since 0.8.0 you can also restore part of a session. Say the agent's payments change was wrong but its test additions were fine: put back only the payments work and keep everything else.
$ viberevert rollback <session> --only 'app/api/**' # preview — nothing changed yet[RESTORED] app/api/checkout/route.ts [RESTORED] app/api/webhooks/stripe/route.ts Eligibility: eligible
$ viberevert rollback --only 'app/api/**' --apply
Four ways to choose, and any one of them switches rollback into selective mode:
| Selector | Picks |
|---|---|
--only | changes matching a path pattern |
--except | everything but those, subtracted last |
--risk | changes a finding rated at or above that level touches |
--finding | the changes one specific finding applies to |
Positive selectors combine by intersection, so --only 'payments/**' --risk critical means critical changes inside payments/, not payments plus every unrelated critical file. Path selectors follow a renamed file, so a file moved out of payments/ still matches. Nothing is restored unless everything you selected can be: if any selected path drifted since the session ended, the whole operation refuses rather than half-applying, and --force does not override that. If a selective apply is interrupted, the next one fails closed and points you at the emergency checkpoint rather than layering a second partial restore on top.
Two current limitations worth knowing before you rely on it:
- Sessions ended before 0.8.0 cannot be selectively rolled back. They have no record of what they contributed and it cannot be reconstructed. Whole-session rollback still works on them, unchanged. See MIGRATIONS.md.
- `--finding` needs the full finding id, as printed by
viberevert check --since --json. Short prefixes are not accepted yet.
It does not reverse effects outside your project files. Deployments, database writes, third-party API calls, payments, and sent emails need their own recovery. Rollback is state-based rather than atomic, and it's a safety net around AI sessions, not a replacement for tests or review. Read what rollback can and can't restore before you rely on it.
One recovery layer across your coding agents
Keep using the coding tools you prefer. VibeRevert can wrap command-line agent sessions (viberevert run ) and integrates with tools such as Claude Code and Cursor through its installers.
Built-in checkpoints live inside the agent's workflow. VibeRevert stays with the project.
It captures your project's starting state — including uncommitted work — then records the session, flags risky changes, previews the rollback, and keeps that recovery path outside the agent itself.
Use Claude Code today, Cursor tomorrow, or wrap another terminal agent: the safety layer stays with your project.
Wire it into your tools
VibeRevert installs non-destructively and can be removed cleanly. It integrates with Claude Code and Cursor (MCP server and hooks); every install previews its changes and keeps a recovery journal. See getting started.
An experimental terminal bridge (--pty) can intercept commands inside an interactive agent shell; it's best-effort and documented as such in the PTY contract.
Platforms
Linux, macOS, and Windows, on Node.js 22+. CI runs the suite across all three on Node 22 and 24; see compatibility for exactly what each platform is tested to do.
Learn more
- Getting started · Commands · Configuration
- What rollback can and can't restore · Risk taxonomy
- Security policy · Threat model · Contributing
Support VibeRevert
VibeRevert is Apache-2.0 open source. Sponsoring funds continued cross-platform testing, security work, rollback and recovery testing, and helping pay for independent review. Sponsorship does not influence risk findings or release decisions. → [Sponsor VibeRevert](https://github.com/sponsors/madeinplutofabio?metadata_campaign=viberevert) · what your support funds
License
Apache-2.0. See NOTICE and the license audit.