Viberevert MCP server
{
"mcpServers": {
"viberevert": {
"command": "npx",
"args": [
"-y",
"viberevert@latest"
]
}
}
}{
"mcpServers": {
"viberevert": {
"command": "npx",
"args": [
"-y",
"viberevert@latest"
]
}
}
}{
"mcpServers": {
"viberevert": {
"command": "npx",
"args": [
"-y",
"viberevert@latest"
]
}
}
}{
"servers": {
"viberevert": {
"command": "npx",
"args": [
"-y",
"viberevert@latest"
]
}
}
}{
"mcpServers": {
"viberevert": {
"command": "npx",
"args": [
"-y",
"viberevert@latest"
]
}
}
}file .mcp.json (in your project root)file claude_desktop_config.jsonfile ~/.cursor/mcp.jsonfile .vscode/mcp.jsonfile ~/.codeium/windsurf/mcp_config.jsoninstall npx -y viberevertversion 0.7.1-beta.4
What it does
VibeRevert records AI coding sessions, flags risky changes using deterministic rules (not AI judgment), and restores your project files to their pre-session state including uncommitted work. It is for developers using coding agents like Claude Code or Cursor who want a safety layer that can undo changes without losing their own work.
- Undo an AI coding session that touched sensitive code (payments, auth, database migrations) while preserving your uncommitted changes.
- Review what an AI agent changed across your project and identify risky edits before committing.
- Selectively restore only part of a session (e.g., revert the agent's payment changes but keep its test additions).
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.