io.github.klewicki7/vibelens-mcp

Registre officiel Outils de développement

VibeLens MCP tool for AI to visualize code changes with inline annotations in VS Code/Cursor

Que pouvez-vous faire avec 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-mcp for supported AI tools.

Installation

Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).

NPM package vibelens-mcp
Claude Code
claude mcp add vibelens-mcp -e 'YOUR_API_KEY=<your your_api_key>' -- npx -y vibelens-mcp@0.1.0
Configuration JSON (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "vibelens-mcp": {
            "command": "npx",
            "args": [
                "-y",
                "vibelens-mcp@0.1.0"
            ],
            "env": {
                "YOUR_API_KEY": "<your your_api_key>"
            }
        }
    }
}

Variables d'environnement

  • YOUR_API_KEY obligatoire secret Your API key for the service

Documentation

Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.

Sommaire
  1. VibeLens
  2. Why AI Peer Review?
  3. How It Works
  4. Features
  5. Installation
  6. Manual MCP Configuration
  7. Packages
  8. Architecture
  9. Development
  10. Publishing
  11. License

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-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 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

PackageDescription
packages/extensionVS Code/Cursor extension that displays diff explanations
packages/mcpMCP 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-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

Questions fréquentes

Qu'est-ce que io.github.klewicki7/vibelens-mcp ?

VibeLens MCP tool for AI to visualize code changes with inline annotations in VS Code/Cursor

Comment installer io.github.klewicki7/vibelens-mcp ?

Il s'exécute sur votre machine. Dans Claude Code : claude mcp add vibelens-mcp -e 'YOUR_API_KEY=<your your_api_key>' -- npx -y vibelens-mcp@0.1.0. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.

Faut-il une clé API pour io.github.klewicki7/vibelens-mcp ?

Oui. Il attend YOUR_API_KEY, à renseigner dans sa configuration.

io.github.klewicki7/vibelens-mcp est-il open source ?

Son code est public sur GitHub, mais le dépôt ne déclare pas de licence standard.

Qui maintient io.github.klewicki7/vibelens-mcp ?

Il est publié par klewicki7. AI.tn le référence sans le maintenir ni le recommander.

Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.