Vibelens Mcp

io.github.klewicki7Published by GitHub account klewicki7v0.1.0Updated Oct 25, 2026

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

VerifiedSTDIODesktop onlyDeveloper ToolsMedia & Design

Overview

AI-generated overview

A local MCP server that lets an assistant render annotated git diffs in a VibeLens panel inside VS Code or Cursor.

What you can do
Show a git diff with a title, summary and per-file or per-line annotations in the VibeLens extension panel, targeting Cursor or VS Code and optionally a workspace path for filtering. Attach action buttons with labels and prompts to individual annotations so a reviewer can send follow-up requests to chat. Provide a reusable prompt that guides the assistant to obtain a diff, prepare annotations and call the display tool.
When to use it
Useful when you want AI explanations of code changes shown visually next to the diff in your editor instead of as plain chat text, for example when reviewing a branch or a working-tree change before committing.
Requirements
Runs locally over stdio, typically started with npx or a global npm install, so Node.js is needed. Requires the companion VibeLens extension in VS Code or Cursor to display results. The manifest declares a required API key environment variable named YOUR_API_KEY.
Before you install
The server writes to a pending file and a local database under the user's home directory, and the extension reads that data, so diff content and annotations are stored on disk. It asks for an API key via YOUR_API_KEY; check what that key is for before supplying it. Annotations and action prompts are passed to the editor extension and may be sent to chat when a button is used.

Installation

In SourceWeft

  1. Open Vibelens Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

VibeLens MCP Server

MCP server that provides the show_diff_explanation tool for visualizing code changes with AI annotations.

Installation

bash
npx -y vibelens-mcp

Or install globally:

bash
npm install -g vibelens-mcp

MCP Configuration

Add to your MCP client configuration:

json
{  "mcpServers": {    "vibelens": {      "command": "npx",      "args": ["-y", "vibelens-mcp"]    }  }}

Tool: show_diff_explanation

Displays a git diff with AI-generated annotations in the VibeLens extension panel.

Parameters

ParameterTypeRequiredDescription
titlestringYesTitle for the explanation
diffstringYesRaw git diff output (unified format)
summarystringNoHigh-level overview of changes
annotationsarrayNoExplanations for specific parts of the diff
workspacePathstringNoAbsolute path to project folder (for workspace filtering)
editorstringNo"cursor" or "vscode" (default: "cursor")

Annotation Object

FieldTypeRequiredDescription
filestringYesFile path the annotation refers to
linenumberNoLine number in the new file
explanationstringYesYour explanation of this change
actionsarrayNoAction buttons with prompts

Action Object

FieldTypeRequiredDescription
labelstringYesButton label (e.g., "Add tests")
promptstringYesFull prompt to send to chat

Example

json
{  "title": "Add user authentication",  "summary": "Added JWT middleware and protected API routes.",  "diff": "diff --git a/src/auth.ts b/src/auth.ts\n...",  "workspacePath": "/Users/me/myproject",  "annotations": [    {      "file": "src/auth.ts",      "line": 15,      "explanation": "Extracts and validates JWT token from Authorization header",      "actions": [        {          "label": "Add refresh token",          "prompt": "Add refresh token support to this auth middleware"        }      ]    }  ]}

Prompt: vibelens

The MCP server also provides a prompt with instructions for explaining code changes. Reference it with @vibelens in your chat.

The prompt guides the AI to:

  1. Get the diff from conversation context (or run git diff if needed)
  2. Analyze and prepare annotations
  3. Call show_diff_explanation with appropriate parameters
  4. Generate specific, actionable suggestions for each annotation

How It Works

The MCP server writes to ~/.vibelens/pending.json and stores reviews in ~/.vibelens/vibelens.db. The companion VS Code/Cursor extension watches this data and displays the diff in a webview panel.

MCP Server                    Extension     │                            │     │ writes to                  │ watches     │ ~/.vibelens/               │ ~/.vibelens/     │ pending.json               │ pending.json     └────────────────────────────┘

Development

bash
# Buildnpm run build
# The server runs via stdionode dist/index.js

License

MIT

Source: packages/mcp/README.md at commit 67b82b4

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.