io.github.klewicki7/vibelens-mcp
VibeLens MCP tool for AI to visualize code changes with inline annotations in VS Code/Cursor
What can you do with io.github.klewicki7/vibelens-mcp?
- 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-mcpfor supported AI tools.
Install
Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).
vibelens-mcpclaude mcp add vibelens-mcp -e 'YOUR_API_KEY=<your your_api_key>' -- npx -y vibelens-mcp@0.1.0
{
"mcpServers": {
"vibelens-mcp": {
"command": "npx",
"args": [
"-y",
"vibelens-mcp@0.1.0"
],
"env": {
"YOUR_API_KEY": "<your your_api_key>"
}
}
}
}
Environment variables
YOUR_API_KEYrequired secret Your API key for the service
Documentation
From the project's README on GitHub, refreshed weekly. Links open on GitHub.
Contents
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 panel
The AI calls the show_diff_explanation 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-mcpfor 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 claude_desktop_config.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
| Package | Description |
|---|---|
| packages/extension | VS Code/Cursor extension that displays diff explanations |
| packages/mcp | MCP server with the show_diff_explanation tool |
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 package
Publishing
- Extension: Published as
kevcode.vibelens-extensionto 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
Frequently asked questions
What is io.github.klewicki7/vibelens-mcp?
VibeLens MCP tool for AI to visualize code changes with inline annotations in VS Code/Cursor
How do I install io.github.klewicki7/vibelens-mcp?
It runs on your machine. In Claude Code: claude mcp add vibelens-mcp -e 'YOUR_API_KEY=<your your_api_key>' -- npx -y vibelens-mcp@0.1.0. For other clients, paste the JSON configuration from this page into their MCP settings.
Does io.github.klewicki7/vibelens-mcp need an API key?
Yes. It expects YOUR_API_KEY, which you set in its configuration.
Is io.github.klewicki7/vibelens-mcp open source?
Its code is public on GitHub, but the repository does not declare a standard license.
Who maintains io.github.klewicki7/vibelens-mcp?
It is published by klewicki7. AI.tn lists it but does not maintain or endorse it.
From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.