VibeLens MCP tool for AI to visualize code changes with inline annotations in VS Code/Cursor
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.
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.
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.
vibelens-mcp for supported AI tools.Install kevcode.vibelens-extension from the Visual Studio Marketplace once published.
Install kevcode.vibelens-extension from Cursor's extension marketplace once the Open VSX listing syncs.
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.
If auto-configuration does not work, add vibelens-mcp manually to your MCP client.
Add to ~/.cursor/mcp.json:
{
"mcpServers": {
"vibelens": {
"command": "npx",
"args": ["-y", "vibelens-mcp"]
}
}
}
Add to claude_desktop_config.json:
{
"mcpServers": {
"vibelens": {
"command": "npx",
"args": ["-y", "vibelens-mcp"]
}
}
}
Add to ~/.codeium/windsurf/mcp_config.json:
{
"mcpServers": {
"vibelens": {
"command": "npx",
"args": ["-y", "vibelens-mcp"]
}
}
}
| Package | Description |
|---|---|
| packages/extension | VS Code/Cursor extension that displays diff explanations |
| packages/mcp | MCP server with the show_diff_explanation tool |
MCP Server VS Code/Cursor Extension
| |
| writes review data | watches
| ~/.vibelens/ | ~/.vibelens/
| |
+----------------------------->|
|
v
Webview Panel
(diff + annotations)
# 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
kevcode.vibelens-extension to VS Code Marketplace and Open VSX.vibelens-mcp.io.github.klewicki7/vibelens-mcp.MIT
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y vibelens-mcpMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"io-github-klewicki7-vibelens-mcp": {
"command": "npx",
"args": [
"-y",
"vibelens-mcp"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup referencevibelens-mcpnpmio.github.klewicki7/vibelens-mcp works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.