Vibelens MCP server
io.github.klewicki7/vibelens-mcp·v0.1.0VibeLens MCP tool for AI to visualize code changes with inline annotations in VS Code/Cursor
0 stars83 downloads/wk
Reviews
Write oneNobody has reviewed Vibelens yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Vibelens tools (1)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
show_diff_explanationShows a git diff with annotations in the VibeLens extension panel. Use this tool after analyzing code changes to present the diff visually with your explanations. The tool will: 1. Save the diff and annotations to the local SQLite database 2. Return a structured envelope with a reviewId for tracking
Public scan report
scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it
- Code scan17 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitystatic API keys via environment variables6/15
- Maintenancelast push 112 days ago8/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How Vibelens compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 72/100
- higher than 38% of 48,255 servers
- Tools
- 1
- the typical server has 7
- Tools that change things
- 0%
- typical: 0%. Fewer write tools means less an agent can break
- Downloads a week
- 83
- more than 58% of 12,191 servers with a package
What its tools let an agent do: 1 read
Install Vibelens in Claude Code, Cursor or VS Code
Runs npx -y vibelens-mcp on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add vibelens-mcp -- npx -y vibelens-mcp
What the publisher says
From the Vibelens repository's README, as published. We do not edit it. Read it on GitHub
VibeLens
AI peer review for your code changes.
Just like humans review each other's PRs, your AI reviews its own changes with inline annotations that appear directly in a VS Code/Cursor panel.
Why AI Peer Review?
When humans write code, we do peer review. When AI writes code, we often scroll through chat hoping we understood what changed.
VibeLens gives AI the same workflow humans use: review the diff, annotate the changes, and explain the reasoning next to the code.
How It Works
AI makes changes -> AI reviews its own diff -> VibeLens opens an annotated panelThe AI calls the showdiffexplanation MCP tool after completing a task. The MCP server stores the review locally, and the VS Code/Cursor extension renders the diff with inline annotations.
Action buttons let you send improvement suggestions directly to Cursor chat.
Features
- Visual diff: Side-by-side or unified view powered by diff2html.
- Inline annotations: Review comments appear directly after relevant code lines.
- Action buttons: Click to send prompts to Cursor chat, such as refactors or test suggestions.
- Click to open: File names link directly to the source.
- Workspace-aware: Only shows in the window matching your project.
- Auto-configured MCP: The extension configures vibelens-mcp for supported AI tools.
Installation
VS Code
Install kevcode.vibelens-extension from the Visual Studio Marketplace once published.
Cursor
Install kevcode.vibelens-extension from Cursor's extension marketplace once the Open VSX listing syncs.
VSIX
Download the .vsix from GitHub Releases and install it from the Extensions view with "Install from VSIX...".
The extension automatically configures the MCP server on first activation where supported.
Manual MCP Configuration
If auto-configuration does not work, add vibelens-mcp manually to your MCP client.
Cursor
Add to ~/.cursor/mcp.json:
{
"mcpServers": {
"vibelens": {
"command": "npx",
"args": ["-y", "vibelens-mcp"]
}
}
}Claude Desktop
Add to claudedesktopconfig.json:
{
"mcpServers": {
"vibelens": {
"command": "npx",
"args": ["-y", "vibelens-mcp"]
}
}
}Windsurf
Add to ~/.codeium/windsurf/mcp_config.json:
{
"mcpServers": {
"vibelens": {
"command": "npx",
"args": ["-y", "vibelens-mcp"]
}
}
}Packages
Architecture
MCP Server VS Code/Cursor Extension
| |
| writes review data | watches
| ~/.vibelens/ | ~/.vibelens/
| |
+----------------------------->|
|
v
Webview Panel
(diff + annotations)Development
# Install dependencies
pnpm install
# Build all packages
pnpm run build
# Build extension only
pnpm run build:extension
# Build MCP only
pnpm run build:mcp
# Package extension as .vsix
pnpm --filter vibelens-extension packagePublishing
- Extension: Published as kevcode.vibelens-extension to VS Code Marketplace and Open VSX.
- MCP package: Published to npm as vibelens-mcp.
- MCP Registry: Registered as io.github.klewicki7/vibelens-mcp.
License
MIT
Nothing above is checked by us. What we check is on the safety report.
Vibelens: common questions
- Is Vibelens MCP server safe?
- Mostly: it is graded B (72/100). Read the Vibelens safety report
- How do I install Vibelens?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Vibelens need an API key?
- Yes. The registry entry asks for
YOUR_API_KEY. - Is Vibelens maintained?
- The last commit was 149 days ago (2026-06-07). The latest release is v0.1.0.
- How does Vibelens compare with other MCP servers?
- safety score 72/100 (higher than 38% of 48,255 servers); tools 1 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.